Apologies, just noticed I copied and pasted wrong. It should have been:

BEFORE
[root@PacketFence-ZEN ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0

AFTER
[root@PacketFence-ZEN ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.51.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0.51

Logical name      IP Address           Netmask              Type
eth0       192.168.50.132                255.255.255.0    Management      ADD 
VLAN
default network: 192.168.50.0
eth0 vlan 51       192.168.51.2     255.255.255.0    Registration        DELETE
default network: 192.168.51.0


From: Jessica Cohen
Sent: Friday, November 02, 2018 11:14 AM
To: 'Durand fabrice' <[email protected]>; 
[email protected]
Subject: RE: [PacketFence-users] getting started - interface questions

Default route looks right after adding a vlan. 192.168.50.1 is the ip on the 
vlan 50 interface on the switch. 192.168.51.1 is the ip on the vlan 51 
interface on the switch. IP routing is enabled and intervlan routing works fine 
except for this server after "add vlan"

BEFORE
[root@PacketFence-ZEN ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0

AFTER
[root@PacketFence-ZEN ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.51.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0.66

Logical name      IP Address           Netmask              Type
eth0       192.168.50.132                255.255.255.0    Management      ADD 
VLAN
default network: 192.168.50.0
eth0 vlan 51       192.168.51.2     255.255.255.0    Registration        DELETE
default network: 192.168.51.0

From: Durand fabrice <[email protected]<mailto:[email protected]>>
Sent: Thursday, November 01, 2018 8:50 PM
To: Jessica Cohen <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: Re: [PacketFence-users] getting started - interface questions


Ok so in this case if you lost the access then it mean that the default route 
is changed.

check the default route before and after you play with the interfaces/vlan.


Le 18-11-01 à 19 h 45, Jessica Cohen a écrit :
Hi Fabrice,

It's a single ethernet interface with all vlans tagged except vlan 50 which is 
untagged. I'm a network engineer so server stuff, especially VMware is a bit 
new to me. I appreciate the assistance.

Jessica

From: Durand fabrice via PacketFence-users 
<[email protected]><mailto:[email protected]>
Sent: Thursday, November 01, 2018 6:40 PM
To: 
[email protected]<mailto:[email protected]>
Cc: Durand fabrice <[email protected]><mailto:[email protected]>
Subject: Re: [PacketFence-users] getting started - interface questions


Hello Jessica,

it depend how you configure the esx, do you have a interface with all the vlan 
tagged (only eth0 in the virtual machine) or a virtual interface for each vlan 
(it appear eth0, eth1, eth2, ethx... on the vm).

Based on that, then you will need to create a vlan on the eth0 interface or 
assign the correct interface as the management/registration/isolation.

Regards

Fabrice


Le 18-10-30 à 14 h 42, Jessica Cohen via PacketFence-users a écrit :
Can someone please explain how the interfaces work or provide a link that 
adequately describes them? After importing the OVA and starting the server, it 
gets an IP address from our dhcp server that's in vlan 50. All of our network 
devices management IPs are in vlan 49. When I add a new interface, assign an IP 
and vlan, I suddenly lose all connectivity to the server unless I access it 
from a machine that's on the 50 vlan. Why can't I access the server from other 
vlans? I noticed that it adds a subinterface on eth0 (i.e. eth0.49) but that 
shouldn't affect intervlan routing as long as a default gateway is provided 
right? Can someone help me get past this step?




_______________________________________________

PacketFence-users mailing list

[email protected]<mailto:[email protected]>

https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to