Date: Wed, 12 Mar 2008 22:52:47 +0100 (CET) From: Ingo Flaschberger <if@xip.at> To: Giulio Ferro <auryn@zirakzigil.org> Cc: freebsd-net@freebsd.org, Sean Chittenden <sean@chittenden.org> Subject: Re: VLAN trunking and fragmentation Message-ID: <alpine.LFD.1.00.0803122241140.21544@filebunker.xip.at> In-Reply-To: <47D84B52.5020607@zirakzigil.org> References: <47D7C34E.8060805@zirakzigil.org> <D8BE14C3-9897-4F19-A5AC-6770995423E5@chittenden.org> <47D84B52.5020607@zirakzigil.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Giuilio, > Sean Chittenden wrote: >>> interface ethernet 1/g1 >>> switchport mode trunk >>> switchport trunk allowed vlan add 10 >>> exit >> >> I think this is an issue with default VLAN membership. > > I don't think it's where the problem lies, otherwise even a simple ping > wouldn't work. The problem here explicitly arises when packets are > fragmented... fragmentation? I think, you use ethernet links, all have 1500byte max packet size, you have 1500byte packet size also comfigured at the vlan interface, so.. why do you think anything should start fragmenting? (and tagged vlan frames are bigger than 1500byte at the "raw" ethernet link). check for maximum mtu that can travel over the link. (ping -s 1472 for 1500byte packet) >> switchport trunk encapsulation dot1q >> > There's no such option, I believe it's implicit in the trunk mode... and put the server back to back and remove the switch, just to be shure the switch is not the problem. Kind regards, Ingo Flaschberger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LFD.1.00.0803122241140.21544>