I put a WDS link on my network, replacing a previously working perfectly hard-wired link.
The WDS link is composed of a D-Link DIR-825 rev. B1 running 10.03.1-RC5, r27015 and a Linksys WRT54G/GS/GL running 10.03.1-RC5, r27015 also. The link seems to work just fine but for one problem. The symptom of the problem I am having is that the routing table on the machine across the WDS link is losing it's OSPF (quagga) supplied routes for a period of time, after which they will restore and then disappear again, rinse repeat. A.k.a. flapping. When I look at the OSPF traffic across the link it's quite clear that some traffic is being dropped. For example, the originator of the OSPF routing data (the DIR-825) sends the following traffic out to it's br-lan: 01:49:19.119032 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 52 01:49:29.119909 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 52 01:49:39.120775 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 52 01:49:49.121616 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 52 01:49:49.156963 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:49:49.163503 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:49:49.176246 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 672 01:49:49.383876 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Ack, length 144 01:49:54.141959 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:49:54.386636 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Ack, length 64 01:49:59.122387 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 56 01:49:59.141458 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:04.391427 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Ack, length 44 01:50:09.123166 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 56 01:50:10.273924 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:12.877861 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 100 01:50:12.883817 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 392 01:50:15.261924 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:15.859647 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:17.853734 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:19.123934 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 56 However the receiver, a machine on the other side of the WDS link (i.e. plugged into the WRT54GS) only receives on it's br-lan: 01:49:49.165441 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 52 01:49:49.201450 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:49:49.209237 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:49:49.227617 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 672 01:49:49.427871 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Ack, length 144 01:50:04.435092 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Ack, length 44 01:50:09.166864 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 56 01:50:10.318296 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:12.922271 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 100 01:50:12.929242 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 392 01:50:15.305692 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:15.903668 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:17.897930 IP 10.75.22.196 > 224.0.0.5: OSPFv2, LS-Update, length 64 01:50:19.167041 IP 10.75.22.196 > 224.0.0.5: OSPFv2, Hello, length 56 Clearly some of the sender's traffic did not make it to the receiving WDS router's br-lan. Any thoughts on why this is happening? Any tips on how to further debug or a mailing list to take the issue to if it's not OpenWRT specific? Would the the netdev list be reasonable, or is there a wireless specific netdev list somewhere that would be more appropriate? Cheers, b.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
