Hi List!
I have a strange behavior on a packetfence 4.1 running on debian7:
The network configuration is as follow:
eth0: management
eth1.4: data network
eth1.5: registration
eth1.6: isolation
eth0.2: not used
eth2: not used
When I reboot the server, the network doesn't come up, because of the following
/etc/network/interfaces file:
auto eth0
iface eth0 inet static
address 192.168.3.30
netmask 255.255.255.0
gateway 192.168.3.25
auto eth0.2
iface eth0.2 inet static
address 192.168.2.30
netmask 255.255.255.0
auto eth1
iface eth1 inet static
address
netmask
auto eth1.4
iface eth1.4 inet static
address 192.168.4.1
netmask 255.255.255.0
auto eth1.5
iface eth1.5 inet static
address 192.168.5.1
netmask 255.255.255.0
auto eth1.6
iface eth1.6 inet static
address 192.168.6.1
netmask 255.255.255.0
If I remove the wrong 'eth1' block, then the server start correctly.
If I change something in packetfence "interfaces" configuration, however, then
the wrong eth1 configuration reappears.
Of course, the workaround is to configure eth1 with some dummy, unused IP
address, but it seems that there is an issue here : it should be possible to
have VLAN interfaces (eth1.X), without having to configure the physical
interface.
And in a production environnement, it's quite disturbing to have to check the
interfaces before rebooting the server!
Regards,
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
