Posted: Mon Feb 13, 2012 22:03 Post subject: [ SOLVED ] network errors with client bridge
I just found the solution to a problem I've been having for a long time, with firmwares reaching back for a year i think (i cant remember it ever working since i bought my routers), and thought I'd post my solution here for me to find again at a later time or for any one else experiencing the same problems.
I have two wzr-hp-g300nh and right now one of them serves the internet connection, and that router is running OpenWRT Backfire 10.03.1-rc5 (this router has ip: 192.168.1.2)
the second router is configured as a client bridge with dd-wrt v18024 (this router has ip: 192.168.1.100)
on this client bridge i have my NAS, media center, BluRay-player, dreambox and PS3 and on the wireless network, which is served out by the first router, i have a laptop.
before i found my "fix" i had serious problems with DUP pings and unreachable hosts/nets, if i from my media center pc tried to ping different locations i got:
(DUP!)'s when pinging either the client bridge or the gateway, every 2:nd ping would give me a DUP.
"destination net unreachable" when pinging google ~every 2:nd ping would give me that
"destination host unreachable" when pinging a host not connected via switch (my laptop) ~every 4:th ping would end in a message like that
and then depending on moon phases or something, i could have most of them mixed in the same ping...
anyways, what i found was that if i logged on via ssh to the client bridge and killed relayd and then restarted relayd again, without the "-B" that it was started with originally, my ping's would work without any problems
of course it wasn't only my pings that suffered from the broken networking, i could hardly reach the internet at all
the "-B" option appears to be undocumented, does anyone know what it's supposed to do?
------edit-----------
hmmm, i must have been blind.. "-B" is "Enable broadcast forwarding"
Posted: Wed Feb 15, 2012 3:13 Post subject: Re: [ SOLVED ] network errors with client bridge
pigge wrote:
I just found the solution to a problem I've been having for a long time, with firmwares reaching back for a year i think (i cant remember it ever working since i bought my routers), and thought I'd post my solution here for me to find again at a later time or for any one else experiencing the same problems.
I have two wzr-hp-g300nh and right now one of them serves the internet connection, and that router is running OpenWRT Backfire 10.03.1-rc5 (this router has ip: 192.168.1.2)
the second router is configured as a client bridge with dd-wrt v18024 (this router has ip: 192.168.1.100)
on this client bridge i have my NAS, media center, BluRay-player, dreambox and PS3 and on the wireless network, which is served out by the first router, i have a laptop.
before i found my "fix" i had serious problems with DUP pings and unreachable hosts/nets, if i from my media center pc tried to ping different locations i got:
(DUP!)'s when pinging either the client bridge or the gateway, every 2:nd ping would give me a DUP.
"destination net unreachable" when pinging google ~every 2:nd ping would give me that
"destination host unreachable" when pinging a host not connected via switch (my laptop) ~every 4:th ping would end in a message like that
and then depending on moon phases or something, i could have most of them mixed in the same ping...
anyways, what i found was that if i logged on via ssh to the client bridge and killed relayd and then restarted relayd again, without the "-B" that it was started with originally, my ping's would work without any problems
of course it wasn't only my pings that suffered from the broken networking, i could hardly reach the internet at all
the "-B" option appears to be undocumented, does anyone know what it's supposed to do?
------edit-----------
hmmm, i must have been blind.. "-B" is "Enable broadcast forwarding"
the strange thing is that it works in windows on the same media pc.
But the ping reply times are longer when -B is used as an option to relayd on the bridge
there must be some differences in Windows vs Linux ping, when i set the MTU in Linux ping to >=1473 i won't get any unreachable messages when i ping hosts on the lan, a ping to google though still gives me "Destination Net Unreachable" on both Windows and Linux
Posted: Wed Mar 14, 2012 14:08 Post subject: great trick
Man, your trick made my day!
I was just preparing an email to send this f***ing router back, but I gave it one more chance ... what the hack?! ... and your post came out of nowhere and saved this little bastard.
Initially, I thought this might be related to the wireless bridge and I tried to tweak the wireless bridge channel, but with no luck.
BTW, how come did you get to this obscure setting? -B. I would have need ages to figure this out.
actually it took me ages, but mostly since no FW before 17461 had wireless that were stable enough to test things over the link, after that it was a combination of frustration, stubbornness and luck i guess ;)