SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-18-2008, 07:16 AM
| ||||
| ||||
 Re: Vlan em weirdness if_em works fine with vlan for me are you sure you aren't simply misconfiguring your vlan device (Switch?) ??? you don't appear to be testing the same networks between your bge and em vlans Gabe E. Nydick [Gabe.Nydick@transacttools.net] wrote: > I have mutliple vlans setup on my em0 interface. I am experiencing a > problem where all of the inbound packets are being received on em0 and > outbound packest destined for hosts on the vlan are being sent on vlan100. > This breaks arp and probably other protocols. If I add static arp entries, > layer 3 seems to work fine. As you can see, the arp-requests leave vlan100 > and arp-replies arrive on em0. My bge interfaces have all traffic leave & > arrive on vlan3 as shown below. > > BROKEN ? packest leave via vlan100 and arrive via em0 > > # netstat -I em0 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Colls > em0 1522 <Link> 00:04:23:09:9b:7c 8606 0 7790 0 > 0 > em0 1522 fe80::%em0/ fe80::204:23ff:fe 8606 0 7790 0 > 0 > > # netstat -I vlan100 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Colls > vlan100 1500 <Link> 00:04:23:09:9b:7c 0 0 1632 0 > 0 > vlan100 1500 fe80::%vlan fe80::204:23ff:fe 0 0 1632 0 > 0 > vlan100 1500 172.16.1/24 172.16.1.103 0 0 1632 0 > 0 > > BROKEN ? arp-replies only arrive on em0 > > # tcpdump -evn -i em0 arp > tcpdump: WARNING: em0: no IPv4 address assigned > tcpdump: listening on em0 > 11:20:21.475925 0:5:5e:2a:f5:e0 0:4:23:9:9b:7c 0806 60: arp reply 172.16.1.1 > is-at 0:5:5e:2a:f5:e0 > 11:20:22.481104 0:5:5e:2a:f5:e0 0:4:23:9:9b:7c 0806 60: arp reply 172.16.1.1 > is-at 0:5:5e:2a:f5:e0 > 11:20:23.491032 0:5:5e:2a:f5:e0 0:4:23:9:9b:7c 0806 60: arp reply 172.16.1.1 > is-at 0:5:5e:2a:f5:e0 > 11:20:24.500959 0:5:5e:2a:f5:e0 0:4:23:9:9b:7c 0806 60: arp reply 172.16.1.1 > is-at 0:5:5e:2a:f5:e0 > 11:20:25.511012 0:5:5e:2a:f5:e0 0:4:23:9:9b:7c 0806 60: arp reply 172.16.1.1 > is-at 0:5:5e:2a:f5:e0 > > # tcpdump -evn -i vlan100 arp > tcpdump: listening on vlan100 > 11:20:45.691950 0:4:23:9:9b:7c ff:ff:ff:ff:ff:ff 0806 42: arp who-has > 172.16.1.1 tell 172.16.1.103 > 11:20:46.700052 0:4:23:9:9b:7c ff:ff:ff:ff:ff:ff 0806 42: arp who-has > 172.16.1.1 tell 172.16.1.103 > 11:20:47.710030 0:4:23:9:9b:7c ff:ff:ff:ff:ff:ff 0806 42: arp who-has > 172.16.1.1 tell 172.16.1.103 > 11:20:48.720040 0:4:23:9:9b:7c ff:ff:ff:ff:ff:ff 0806 42: arp who-has > 172.16.1.1 tell 172.16.1.103 > 11:20:49.730032 0:4:23:9:9b:7c ff:ff:ff:ff:ff:ff 0806 42: arp who-has > 172.16.1.1 tell 172.16.1.103 > > ---------------------------------------------------------------------------- > ------------------------------ > > NOT BROKEN ? packets leave and arrive via vlan3 and bge1 > > # netstat -I bge1 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Colls > bge1 1522 <Link> 00:0f:1f:6a:51:67 5147 0 2208 0 > 0 > bge1 1522 fe80::%bge1 fe80::20f:1fff:fe 5147 0 2208 0 > 0 > > # netstat -I vlan3 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Colls > vlan3 1500 <Link> 00:0f:1f:6a:51:67 426 0 2184 0 > 0 > vlan3 1500 fe80::%vlan fe80::20f:1fff:fe 426 0 2184 0 > 0 > vlan3 1500 216.223.10/ obsdfw02-internal 426 0 2184 0 > 0 > > NOT BROKEN ? arp-replies arrive on vlan3 and bge1 > > # tcpdump -evn -i bge1 arp > tcpdump: WARNING: bge1: no IPv4 address assigned > tcpdump: listening on bge1 > 11:22:13.566419 0:d:56:fe:a2:11 0:f:1f:6a:51:67 0806 60: arp reply > 216.223.10.11 is-at 0:d:56:fe:a2:11 > > # tcpdump -evn -i vlan3 arp > tcpdump: listening on vlan3 > 11:22:33.129887 0:f:1f:6a:51:67 ff:ff:ff:ff:ff:ff 0806 42: arp who-has > 216.223.10.11 tell 216.223.10.253 > 11:22:33.130064 0:d:56:fe:a2:11 0:f:1f:6a:51:67 0806 60: arp reply > 216.223.10.11 is-at 0:d:56:fe:a2:11 -- The past cannot be changed. The future cannot be guaranteed.      |
Linear Mode
