Date: Tue, 26 Feb 2002 16:28:21 +0100 (CET) From: "Bjoern A. Zeeb" <bzeeb@zabbadoz.net> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-stable@FreeBSD.ORG, "Bjoern A. Zeeb" <bzeeb@zabbadoz.net> Subject: Re: VLAN init prob ? [was: Strangeness on 4.5-STABLE] Message-ID: <Pine.BSF.4.44.0202261359270.441-100000@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <5.1.0.14.0.20020226010232.04e51a38@192.168.0.12>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Feb 2002, Mike Tancsa wrote:
> Details please.... How about some more info,
Here we go ... (stripping the 64 IPs bound to lo0 ;-)
> ifconfig -a
--- snip ---
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::202:b3ff:fe60:7db6%fxp0 prefixlen 64 scopeid 0x1
ether 00:02:b3:60:7d:b6
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
...
vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.111.66.194 netmask 0xffffffe0 broadcast 10.111.66.223
inet6 fe80::202:b3ff:fe60:7db6%vlan2 prefixlen 64 scopeid 0x5
ether 00:02:b3:60:7d:b6
vlan: 2 parent interface: fxp0
...
--- snip ---
> netstat -ni
--- snip ---
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
fxp0 1500 <Link#1> 00:02:b3:60:7d:b6 163365 0 110734 0 0
fxp0 1500 fe80:1::202 fe80:1::202:b3ff: 0 - 0 - -
...
vlan2 1500 <Link#5> 00:02:b3:60:7d:b6 163450 0 110733 0 0
vlan2 1500 10.111.66.192 10.111.66.194 163223 - 110714 - -
vlan2 1500 fe80:5::202 fe80:5::202:b3ff: 0 - 0 - -
--- snip ---
> You said you have the fxp installed now and a 3com before... Are you
> setting the MTU explicitly ?
Did this for the 3Com but it is not needed for the fxp.
> How are you setting up your 802.1q vlan interface. The problems you are
In /etc/rc.conf:
# on 3Com (xl) mtu needs to be fixed (see man 4 vlan); mtu was 1496 before
#ifconfig_xl0="up"
#ifconfig_vlan2="inet 10.111.66.194 netmask 255.255.255.224 vlan 2 vlandev xl0 mtu 1500"
# fxp informs vlan driver that it supports long frames; no mtu correction needed
ifconfig_fxp0="up"
ifconfig_vlan2="inet 10.111.66.194 netmask 255.255.255.224 vlan 2 vlandev fxp0"
> describing would be consistent if your VLAN was messed up in the sense that
> one interface, be that your nic or switch port, does not have a consistent
> size for your ethernet frames (1500+the vlan info)
The other side is a linux machine with another eepro100 (in between
there is an unmanagable switch):
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:b3:60:81:0b brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1351151175 1535814 0 0 0 0
TX: bytes packets errors dropped carrier collsns
1353519274 1525204 0 0 0 0
3: vlan2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 00:02:b3:60:81:0b brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
364846469 724669 0 0 0 1130
TX: bytes packets errors dropped carrier collsns
980460610 811599 0 0 0 0
But I can see the problem clearer now !
I am only having trouble in one direction (from FreeBSD->linux-gw) but not
in the other direction after booting. F***. Never try to debug problems
if you're already running half in suspend mode in the eve ;-( I should
have ssen this last eve too ...
Now did a
ifconfig fxp0 mtu 1400
ifconfig vlan2 mtu 1400
after booting and
-> other direction ok
so I thought back to the old values:
ifconfig fxp0 mtu 1500
ifconfig vlan2 mtu 1500
-> both directions ~6Mbit/s to and from my laptop (not in that vlan)
with ftp. That's ok. No stalls, ...
NO more hangs have been found since then on any new connection for
more than two hours now.
This may also explain the fact that it worked through the weekend
because last time I must have set the mtu from 1496 to mtu by hand
and after that placed the command extention in /etc/rc.conf what seems
to fail gloriously :(
Output from above once again:
--- snip ---
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::202:b3ff:fe60:7db6%fxp0 prefixlen 64 scopeid 0x1
ether 00:02:b3:60:7d:b6
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
...
vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.111.66.194 netmask 0xffffffe0 broadcast 10.111.66.223
inet6 fe80::202:b3ff:fe60:7db6%vlan2 prefixlen 64 scopeid 0x5
ether 00:02:b3:60:7d:b6
vlan: 2 parent interface: fxp0
...
--- snip ---
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
fxp0 1500 <Link#1> 00:02:b3:60:7d:b6 476369 0 492736 0 0
fxp0 1500 fe80:1::202 fe80:1::202:b3ff: 0 - 0 - -
...
vlan2 1500 <Link#5> 00:02:b3:60:7d:b6 476472 0 492741 0 0
vlan2 1500 10.111.66.192 10.111.66.194 474272 - 493109 - -
vlan2 1500 fe80:5::202 fe80:5::202:b3ff: 0 - 0 - -
...
--- snip ---
So I suspect this to be a problem when initializing the vlan ? Or did
I miss s.th. ? Found not much docs about this apart from vlan(4) and
some postings/articles not beeing too precise.
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.44.0202261359270.441-100000>