Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Mon Jul 13, 2020 3:12 Post subject:
Ok, so. Is your existing router going to be your dhcp server for the entire network, or are you going to double NAT with the WRT54*?
If you are setting wan to auto-dhcp in gateway mode, your WRT54* should be in a different subnet, i.e. 192.168.2.x; If you are configuring in router mode, wan disabled and assigned to switch and dhcp turned off on the WRT54*, then the router should have a static IP assigned in the same subnet as the main router, outside of the dhcp server's served IP range.
Thanks for your response.
I am aware that I would need to configure the router on a different subnet.
Aside of configuring the router to work on my existing network, my only concern is getting the LAN ports to work.
I need to be able to access the router through the LAN ports before I can do anything else. From the first time I flashed the firmware I have only been able to access the router through a WIFI connection. I just need your help in getting access to the router through the LAN ports.
Thanks.
Thanks for your response.
I am aware that I would need to configure the router on a different subnet.
Aside of configuring the router to work on my existing network, my only concern is getting the LAN ports to work.
I need to be able to access the router through the LAN ports before I can do anything else. From the first time I flashed the firmware I have only been able to access the router through a WIFI connection. I just need your help in getting access to the router through the LAN ports.
Thanks.
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Thu Jul 08, 2021 15:10 Post subject:
On what build? It seems nobody ever followed up and I didn't see any advice to do an nvram erase && reboot via telnet or ssh at any point in this thread. If you have tried every suggestion in this thread to correct it and it is still broken, then we can try to figure this out by doing the things below.
If you can connect via wifi, check "Setup -> Networking" tab in webUI to see if the proper interfaces are assigned to br0 as well as "Setup -> Switch Config" (or VLANs) tab to see if that is all correct. If everything looks correct and syslog and klog are enabled, please provide output of 'cat /var/log/messages', 'dmesg', 'nvram show' (see earlier posts in this thread or swtiched ports wiki), and 'ifconfig' at the very least in a text file attached to your post. At that point, I can contact the developer about this. _________________ "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
On what build? It seems nobody ever followed up and I didn't see any advice to do an nvram erase && reboot via telnet or ssh at any point in this thread. If you have tried every suggestion in this thread to correct it and it is still broken, then we can try to figure this out by doing the things below.
If you can connect via wifi, check "Setup -> Networking" tab in webUI to see if the proper interfaces are assigned to br0 as well as "Setup -> Switch Config" (or VLANs) tab to see if that is all correct. If everything looks correct and syslog and klog are enabled, please provide output of 'cat /var/log/messages', 'dmesg', 'nvram show' (see earlier posts in this thread or swtiched ports wiki), and 'ifconfig' at the very least in a text file attached to your post. At that point, I can contact the developer about this.
