Posted: Thu Jun 09, 2022 2:30 Post subject: DIR-878 client bridge problem
I flashed the 878 with the latest June 7 firmware. I followed the client bridge setup below, doesn't work, the 878 did connected to my router but no internet and the main router will not see my computer which is connected to the 878.
I am using the 878 to replace my Netgear R6300 which worked fine as a client bridge but it died two days ago.
Anyone know if the 878 actually will not work as a client bridge router? Thanks.
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Thu Jun 09, 2022 3:09 Post subject:
These fake bridge modes do not support ARP or multicast. It would be helpful to see the screenshots rather than make folks grasp at straws, but my first thought is whether or not the upstream router IP has been entered into the gateway config in the Setup -> Basic Setup tab as well as on the applicable Wireless -> Basic Wireless Settings tab (if it's like Atheros). _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
These fake bridge modes do not support ARP or multicast. It would be helpful to see the screenshots rather than make folks grasp at straws, but my first thought is whether or not the upstream router IP has been entered into the gateway config in the Setup -> Basic Setup tab as well as on the applicable Wireless -> Basic Wireless Settings tab (if it's like Atheros).
Basically, the setting was the same like the dead Netgear R6300, the 878 is 192.168.1.5 and my main router is 192.168.1.1, my computer is set to 192.168.1.9, if I do not change my computer ip back to automatic ip and dns, I was able to see the content of the NAS that was connected to my main router but no internet. If I switch my computer back to auto IP and DNS, can not see anything and ipconfig show that its ip number is not even 192.xxx.xxx.xxx, I think it was 168.xxx.xxx.xxx
When my computer was set 192.168.1.9, under ipconfig, the gateway is 192.168.1.1 but no subnet mask number.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Thu Jun 09, 2022 9:16 Post subject:
Too many words and not enough setup screenshots.
I think you just have a bad setup your described IPs are in the same subnet, so they all should be able to talk to each other by default. If you have different routers, they all should have different subnets and not the same subnets as each other and their connected clients. (im guessing because there is nothing to look at but words salads).
No need to go messing around with bridges for any of this, what you need is setting up static leases and proper subnetting, if you have more routers/subnets on network consider using proper routing instead of bridges (Setup tab -> Advanced routing tab and you have routing tables and routing policies)
Too many people use bridges when they should be setting up routing between subnets.
Finally found out what is wrong, I used to connect wireless bridge to a Linksys router which is also ddwrt without problem.
Upgraded to an Asus router with Asus stock firmware and now the wireless bridge will connect but no internet, I can ping all network devices without problem but just no internet access.
Recent development changes may have introduced a needed change in procedure from the wikis. I also vote for screenshots, but it may be as simple as switching back to gateway mode on the Setup -> Advanced Routing tab. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Not surprising, stock firmware is not magic either and will now lock you to prevent you from flashing DD-WRT or any other 3rd party Firmware.
And stock firmware generally speaking is filled to the brim and back with unpatched known exploits.
I suggest you post your setup screenshots from your DD-WRT setup, we dont support 3rd party/stock firmware here so you know. They have their own places of support, and in case of stock FW they have very well paid support staff, while we are all unpaid volunteers (just dd-wrt users like you).
Thank you very much again, I can solve the problem now, all I have to do is to flash the Asus with DDWRT.
Recent development changes may have introduced a needed change in procedure from the wikis. I also vote for screenshots, but it may be as simple as switching back to gateway mode on the Setup -> Advanced Routing tab.
Thank you very much, I will try that when I have time to flash the Asus back to stock firmware to see if just switching to gateway will work.
