**** BEGIN LOGGING AT Thu Sep 22 02:59:57 2011 Sep 22 16:17:29 Mathjis, I tried a couple those trouble shooting steps you suggested Sep 22 16:17:49 ran tcpdump on the br-lan interface with a host value for my laptop's IP address 192.168.10.151 Sep 22 16:18:05 It picks up my SSH connections to Internet hosts as well as my fonera. Sep 22 16:18:24 But when I try to SSH to a host on the local LAN subnet, nothing even show up on tcpdump. Sep 22 16:18:26 Weird. Sep 22 16:18:42 Here's the command that I'm running: tcpdump -ni br-lan host 192.168.10.151 and port 22 Sep 22 16:19:50 Same behavior for ping packets: tcpdump -ni br-lan host 192.168.10.151 and icmp Sep 22 16:20:11 cleaning the iptables rules did not make any differnce. Sep 22 16:20:23 It seems like there is a problem with the bridging function. Sep 22 17:42:10 srf21c: Do you see the packets when you dump the actual LAN and Myplace interfaces (eth0.0 and ath1 IIRC) ? Sep 22 17:59:17 let me check Sep 22 18:02:10 "tcpdump -ni eth0.0 host 192.168.10.151 and icmp" catches nothing. Sep 22 18:03:25 "tcpdump -ni ath1 host 192.168.10.151 and icmp" catches pings to the router LAN IP 192.168.10.1 and Internet hosts such as google DNS 8.8.8.8 Sep 22 18:03:59 that would be consistent with my problem as no traffic seems to be getting bridged from LAN to WiFI interfaces Sep 22 18:04:35 "tcpdump -ni ath1 host 192.168.10.151 and icmp" does not catch ping to any wired LAN hosts on the local subnet Sep 22 18:08:40 Hmm, that seems weird Sep 22 18:09:11 though it might be an artifact of the way bridging is implemented, packets might take a shortcut (around tcpdump) in some cases I think Sep 22 18:09:13 Tell me about it. Here's a sample: http://pastebin.ca/2082220 Sep 22 18:09:44 if I ping other hosts on the Wireless side of the local subnet, those are not picked up by tcpdump either. Sep 22 18:09:58 wireless to wireless ping goes undetected, that is. Sep 22 18:11:22 I'm running SVN 2012 on the device right now. Doesn't seem to matter what build I'm running though, the problem comes and goes with the same build in firmware. Sep 22 18:11:32 as I saw yesterday. Sep 22 18:12:04 I'm almost getting paranoid like someone is hacking into it, changing it and breaking it after I get it working. Sep 22 18:12:30 Maybe I should go back to a stock firmware to see if that resolves it. Sep 22 18:13:13 Might be useful, for debugging at least Sep 22 18:13:31 which version do you suggest? Sep 22 18:13:37 however, I think I've seen the issue as well, but it disappeared when I looked more closely Sep 22 18:13:58 that does seem consistent with your observations, so I should probably have a closer look at the problem Sep 22 18:14:30 Perhaps just the latest stable, which is Flipper IIRC? Sep 22 18:15:27 yes, flipper. Sep 22 18:16:04 Can I downgrade to a previous version though the GUI or should I use the command line method mtd? Sep 22 18:16:53 I'll just use the mtd command via SSH Sep 22 18:19:00 flashing now, be back in a bit. Sep 22 18:30:39 ok, I'm back Sep 22 18:32:48 Alright, wired to wifi is working now. Sep 22 18:32:59 Definitely a software bug. Sep 22 18:45:32 Alright, now what? Sep 22 18:46:40 Do I build a revision just before 1929 to see where the bug comes back? Sep 22 18:52:55 srf21c: Are you sure the bug is gone now? Sep 22 18:53:12 srf21c: Before, it would go away after a firmware flash as well, I think you said? Sep 22 18:55:23 Positive. Sep 22 18:55:58 It only went away on approx 2 out of 8 firmware flashes. Sep 22 18:56:18 And even then it didn't stick. Sep 22 18:56:26 It would eventually break and stay broken. Sep 22 18:58:16 I don't have any more time to mess with it today. Sep 22 18:58:39 Feel free to email me if you want any help investigating this bug later on though. **** ENDING LOGGING AT Fri Sep 23 02:59:56 2011