Re: linux bridge dies after time

(to all long and the short is my wireless card stops responding on a
bridge setup after some time.

i still havent figured out how much to write when i have these problems.
here's the rest of the details. thanks for bearing with me. i swear
i'm reasonably competent with linux.

i'm running a 2.4.24 kernel on a NoName Alpha architecture, namely a
Multia box with two onboard pcmcia's (i82365.o) and a 21064 processor I
believe. The card itself is a Cisco Aironet 350 by airo_cs.o and
airo.o. and bridge.o

its debian testing with a make-kpkg'd kernel (Debian's little package to
turn a kernel build and its associate modules into a handy package...
pretty transparent wrapper really).

everything is static ips. the bridge runs 10.20.30.142. the laptop
with wireless is 10.20.30.166. the server is 10.20.30.1

iptables is blank, but proxy_arp and ip_forward are set to 1 in
/proc/sys/ipv4/conf/(eth*|br0) and /proc/sys/ipv4/ip_forward. i've
tried having proxy_arp on and off, and ip_forward on and off. it doesnt
seem to hcange anything.

i dont have any firewall rules. everything flushed. i presume this is
why i can ping the bridge from both sides, but no packets actually pass
across the bridge... i cannot ping the server from the laptop or hte
laptop from the server. i kind of thought bridge was supposed to auto
forward unless table rules prevented it, which makes me dubious about
how well the bridge is truly functioning.

i just tried with a different Cisco Aironet 350 card (reputed to be very
good, thats why i bought them), and it has the same results.
# ping 10.20.30.4
(many results...)
64 bytes from 10.20.30.142: icmp_seq=53 ttl=64 time=2.6 ms
64 bytes from 10.20.30.142: icmp_seq=53 ttl=64 time=2.2 ms
64 bytes from 10.20.30.142: icmp_seq=53 ttl=64 time=10.8 ms
64 bytes from 10.20.30.142: icmp_seq=54 ttl=64 time=2.1 ms
64 bytes from 10.20.30.142: icmp_seq=55 ttl=64 time=188.5 ms
average times are around 3.2 ms.

i took everything down, ejected the card (taking the wireless down is
not enough, like i said, it refuses to connect even after being taken
down and brought back up, even if i completely remove the br0 interface
entirely and manually specify stuff like ifconfig eth1 -promisc (which
it usually handles for me anyways)). anyways, the second results got to
icmp_seq=847 and died without the ending ping abnormalities, just
quietly fading away.

i always ping with ip addresses, not hostnames.

heres the results you asked for, all 10.0.65's are actually my static ip
addresses, modified to be private to protect the identifies. `
ifconfig -a:
br0 Link encap:Ethernet HWaddr 00:07:0E:B9:8C:7A
inet addr:10.20.30.142 Bcast:10.20.30.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6946 errors:0 dropped:0 overruns:0 frame:0
TX packets:223 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:532150 (519.6 KiB) TX bytes:20699 (20.2 KiB)

eth0 Link encap:Ethernet HWaddr 08:00:2B:E5:27:9D
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6689 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603826 (589.6 KiB) TX bytes:6312 (6.1 KiB)
Interrupt:10 Base address:0x8400

eth1 Link encap:Ethernet HWaddr 00:07:0E:B9:8C:7A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:255 errors:542 dropped:0 overruns:0 frame:542
TX packets:279 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:1000
RX bytes:21543 (21.0 KiB) TX bytes:25795 (25.1 KiB)
Interrupt:5 Base address:0x100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:672 (672.0 b) TX bytes:672 (672.0 b)

wifi0 Link encap:UNSPEC HWaddr
00-07-0E-B9-8C-7A-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:2312 Metric:1
RX packets:255 errors:542 dropped:0 overruns:0 frame:542
TX packets:279 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:100
RX bytes:21543 (21.0 KiB) TX bytes:25795 (25.1 KiB)
Interrupt:5 Base address:0x100

route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.20.30.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
0.0.0.0 10.20.30.1 0.0.0.0 UG 0 0 0 br0

arp -a
prometheus.intranet.domain.com (10.20.30.1) at 00:50A:8D:AC:A5 [ether]
on br0
? (10.20.30.166) at 00:08:E3:9B:E6:33 [ether] on br0
01:52:09.771188 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:09.772517 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:10.784245 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:10.785552 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:11.786314 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:11.787481 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:12.793736 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:12.794757 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:13.793108 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:13.793781 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:14.794479 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:14.795316 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:15.795065 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:15.795988 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:16.797672 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:16.798588 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:17.796692 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:17.798104 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:18.797405 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:18.798802 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:19.798312 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:19.799069 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:20.800131 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:20.800957 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:21.488101 10.20.30.142 > 10.20.30.166: icmp: echo request (DF)
01:52:21.490674 10.20.30.166 > 10.20.30.142: icmp: echo reply
01:52:21.800419 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:21.801335 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:22.232369 arp who-has 10.0.1.1 tell 10.0.1.5
01:52:22.493190 10.20.30.142 > 10.20.30.166: icmp: echo request (DF)
01:52:22.496680 10.20.30.166 > 10.20.30.142: icmp: echo reply
01:52:22.802220 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:22.802988 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:23.494558 10.20.30.142 > 10.20.30.166: icmp: echo request (DF)
01:52:23.496248 10.20.30.166 > 10.20.30.142: icmp: echo reply
01:52:23.803031 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:23.803942 10.20.30.142 > 10.20.30.166: icmp: echo reply
01:52:24.803664 10.20.30.166 > 10.20.30.142: icmp: echo request (DF)
01:52:24.804377 10.20.30.142 > 10.20.30.166: icmp: echo reply




as for the wireless system, its: ==================
eth0 Link encap:Ethernet HWaddr 00:0B:5D:1F:73:A2
inet addr:69.17.65.163 Bcast:69.17.65.255 Mask:255.255.255.0
inet6 addr: fe80::20b:5dff:fe1f:73a2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:808188 errors:0 dropped:0 overruns:0 frame:0
TX packets:653464 errors:0 dropped:0 overruns:1 carrier:0
collisions:10537 txqueuelen:1000
RX bytes:99178566 (94.5 MiB) TX bytes:78136462 (74.5 MiB)
Interrupt:10

eth1 Link encap:Ethernet HWaddr 00:E0:001:9D:16
inet addr:10.20.30.4 Bcast:10.20.30.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1047 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:11 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62973 (61.4 KiB) TX bytes:504 (504.0 b)
Interrupt:10 Base address:0x6000 Memory:e8013000-e8013fff

eth2 Link encap:Ethernet HWaddr 00:08:E3:9B:E6:33
inet addr:10.20.30.166 Bcast:10.20.30.255 Mask:255.255.255.0
inet6 addr: fe80::208:e3ff:fe9b:e633/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1496 errors:1032 dropped:0 overruns:0 frame:1032
TX packets:1891 errors:194 dropped:0 overruns:0 carrier:194
collisions:2089 txqueuelen:1000
RX bytes:140091 (136.8 KiB) TX bytes:145120 (141.7 KiB)
Interrupt:3 Base address:0x100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11704 errors:0 dropped:0 overruns:0 frame:0
TX packets:11704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1306835 (1.2 MiB) TX bytes:1306835 (1.2 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:UNSPEC HWaddr
00-08-E3-9B-E6-33-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:2312 Metric:1
RX packets:1496 errors:1032 dropped:0 overruns:0 frame:1032
TX packets:1891 errors:194 dropped:0 overruns:0 carrier:194
collisions:2089 txqueuelen:100
RX bytes:140091 (136.8 KiB) TX bytes:145120 (141.7 KiB)
Interrupt:3 Base address:0x100


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.65.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.20.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
0.0.0.0 10.0.65.1 0.0.0.0 UG 0 0 0 eth0
kato.domain.com (10.0.65.162) at 00:04:61:47:A2:9B [ether] on eth0
prometheus.domain.com (10.0.65.164) at 00:50A:8D:AC:A5 [ether] on eth0
? (10.50.50.4) at 00:04:61:47:A2:9B [ether] on eth0
? (10.20.30.142) at 00:07:0E:B9:8C:7A [ether] on eth2
dsl017-065-001.wdc1.dsl.speakeasy.net (69.17.65.1) at 00:02:3B:00:B1:5F
[ether] on eth0



thanks much for the reply.

(E-Mail Removed) wrote:
> Hi,
>
> On Fri, 23 Apr 2004 19:23:32 -0400, you posted to alt.internet.wirelessnnnn:
>
>
>>i have a linux box acting as a wireless bridge.
>
>
> Would have been nice to know a few minor details - what distribution, what
> release, what kernel, what hardware, is anything using DHCP (if so, where
> is the DHCP server) or is everything on Static IPs, what addresses (if
> public, replace the first two octets with 10.0. if posting), what firewall
> rules... just minor stuff - my crystal ball doesn't work this far away.
>
>
>>i can ping the bridge from both 802.11b and twisted-pair. but after ~3-7
>>minutes the wireless stops responding.
>
>
> 1. /sbin/ifconfig -a
> 2. /sbin/route -n
> 3. /sbin/arp -a
> 4. /usr/sbin/tcpdump -ni NAME_OF_INTERFACE
>
> where NAME_OF_INTERFACE is the name of the interface as noted in step 1.
> Does pinging IP addresses rather than names change anything? NOTE: Some of
> those commands could be in other directories, or the application may not
> installed. The first three commands should work as a user, but tcpdump
> probably wants you to be root. Do steps 1 to 3 before AND after the link
> fails. What is the difference?
>
> Assuming the box on the wireless side is also running Linux, repeat steps 1
> - 4 on that. If you are running windoze over there, the command "ipconfig
> /all" (NT, w2k, or XP - use winipcfg and the more button in win9x or ME)
> might provide clues.
>
> (E-Mail Removed)
>
>
>> i have a linux box acting as a wireless bridge. i can ping the bridge
>> from th 802.11b and twisted-pair. but after ~3-7 minutes the
>> wireless stops responding.


matt f