The connection isn't working with the wired setup, yet it functions via Wi-Fi.
The connection isn't working with the wired setup, yet it functions via Wi-Fi.
Hello everyone, I'm really puzzled about where I stand right now. In an attempt to resolve my issues, I reached out to someone who seems more experienced in networking. I tried using the Huawei HG8546M as an access point and connected my second Huawei HG8245H as a secondary one to extend Wi-Fi coverage inside a closed space. Initially, everything worked perfectly—I had successfully enabled Wi-Fi in my room. Recently, when trying to connect my Nintendo Switch via the second router, I encountered problems. After spending a long time without issues, I thought I might have hit a limit and needed to increase it. However, things took a turn for the worse. I removed the first router from consideration and focused only on the second one. Unfortunately, I realized I couldn't access the admin page using 10.0.0.1, which was supposed to be the default address. Despite setting a static IP earlier, that didn’t help. I tried resetting the device and reusing 10.0.0.1 as the default, but it still wouldn’t connect. Now I’m left wondering about my wired network setup—it feels strange. After checking Windows, I got an error message, but when I tried Wi-Fi again, I saw my original router name and managed to log in and access the admin panel. I changed the password (it’s labeled 'claro-010'). So far, I can still reach the Wi-Fi interface via Wi-Fi, but Ethernet seems completely unresponsive. I’m stuck and need guidance on what to do next. Please help!
Setting a fixed IP on your PC in the 10.x.x.x/8 network won’t automatically connect you to the second router over Ethernet. You’ll need proper routing or NAT to reach it. Over WiFi works differently, and the second router is typically connected via a LAN port—not WAN. The first router should share the same subnet as the second for seamless communication.
It's linked via LAN, but the primary router is offline now—only the second router and your laptop remain online. Earlier, when I configured it, I assigned an IP of xxx.xx.x.1 to the second router with a range of xxx.xx.x.255. I chose .210 as the static IP for my PC, which should help establish connectivity and allow access afterward.
Would help to know the full IPs, it's what determines the subnet mask that gets entered by default. If they're in different subnets, they won't be able to communicate without proper routing set up. As they're local IPs, there's no need to censor them, there's nothing we can do with them. If you put everything starting with 10.x.x.x and have the subnet mask as 255.0.0.0 then everything's on the same subnet. As the first router is disconnected from the second at the moment, you'll find that you won't get an IP address on your laptop when connected to the 2nd router. The steps for getting it to work as a second access point will involve disabling the DHCP server on the 2nd router to avoid conflicts. The way I'd recommend doing it is setting the 1st router to 10.0.0.1 and set the 2nd router to 10.0.0.2. Disable NAT and DHCP on the 2nd router. On the 1st router, set the DHCP range to start at 10.0.0.3 or later (to avoid 10.0.0.2 being assigned) and end it wherever you want (could be 10.255.255.254 with an /8 subnet mask as the last three octets are all host bits in that case.)
If they aren't linked, it doesn't affect the initial router when you restart the second one. The configuration should be straightforward. Most of the time the first router stays on its default configuration. Turn off DHCP and NAT on the second router, ensure its default gateway is the IP of the first router (if available). Assign a unique IP to the second router from the first but within the same subnet. Link them using a cable through LAN ports and it should work. Remember, since DHCP is disabled on the second router and it's not connected to the first, you can't reach its web interface unless you manually assign a static IP on your PC that matches the second router's subnet.
While reviewing your message, it appears you attempted to reach the second router through the default gateway, which is typically the first router in the setup. The correct path would involve using the static IP assigned to that second router.
I also attempted this before. Now that I performed a factory reset, its IP is back to 10.0.0.1 and I can connect via Wi-Fi. When I run /release it shows "an address has not yet been associated with the network endpoint."