wds bridged router doesn't appear to have internet access via the host router
see attached screen shots for the bridged router showing "wds run" and the dhcp disabled
to test the bridged router I thought it should have internet access from the host router, so I tried to ping yahoo from the command prompt of the pc attached to the c7, but that failed, with "no reply"
the bridged router is supposed to service a device, ZOSI, that has 6 cameras wired to it, and then transmit those pics via the zosi app for remote access.
see zositech.c**/pages/app
the bridged router needs the wds bridging due to it being wired to host router is not practical
so actually I'm not sure if I'm 'bridged' or if I am, how to test access the internet via the host router
I can ping the host router gate way, 192.168.0.1 and the host router pc's ip4 address
any suggestions how to test? possibly to test, do I need to plug the zosi box into 1 of the bridged router lan ports and put the zosi app on my cell phone and see if the camera pics come up?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
thanks for the reply, maybe it was a pc restart or power on/off at the router but its working now
as expected the c7 wds router shows no internet connect light
but it appears I can no longer log into the c7, when I login which is 192.168.0.1 in the browser address bar ,
(the default gateway is 192.168.0.1) I get the c54 host. when I browser login the to the c54 direct from that pc
I get the c54 as expected.
I will want to change the wireless logins on the c7 and need to be logged into it to edit the wireless there
which is (also) the ip of the host c5 router. 192.168.0.1 is also the gateway for c54 host router.
is this typical for a wds client? there must be a preferred way to login to the c7 while is operating in wds mode?
via the usb?
- Copy Link
- Report Inappropriate Content
as previously stated by others as well, you need to set the lan ip of your wds router (c7) within the same subnet of the 192.168.0.x (i.e. 192.168.0.2).
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, 192.168.0.1 is your host router LAN IP address, right?
If the PC connected to C7 could ping LAN IP address your host router, it means the WDS has been working now. However, if the PC cannot get internet access, please connect the same PC to your host router directly and test if internet works.
In addition, what is the IP address you configured for the Archer C7? please make sure it is within the same subnet as the host router, such as 192.168.0.2 etc.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
thanks for the reply, maybe it was a pc restart or power on/off at the router but its working now
as expected the c7 wds router shows no internet connect light
but it appears I can no longer log into the c7, when I login which is 192.168.0.1 in the browser address bar ,
(the default gateway is 192.168.0.1) I get the c54 host. when I browser login the to the c54 direct from that pc
I get the c54 as expected.
I will want to change the wireless logins on the c7 and need to be logged into it to edit the wireless there
which is (also) the ip of the host c5 router. 192.168.0.1 is also the gateway for c54 host router.
is this typical for a wds client? there must be a preferred way to login to the c7 while is operating in wds mode?
via the usb?
- Copy Link
- Report Inappropriate Content
as previously stated by others as well, you need to set the lan ip of your wds router (c7) within the same subnet of the 192.168.0.x (i.e. 192.168.0.2).
- Copy Link
- Report Inappropriate Content
@NGSC yes it always had same subnet, but evidently this stream has split, I'm past that now and have a live bridged router,
but now I can only log into the host router, which is a problem because I have to change the wireless passwords.
- Copy Link
- Report Inappropriate Content
Did you ever change the IP address for the Archer C7? since its default IP is 192.168.0.1 as well, there will be IP conflict as your host router, you need to change it to 192.168.0.2 etc. to avoid the IP conflict but still within the same subnet.
For now, you could try turnning off your main router first and check if 192.168.0.1 will be able to access the C7 web interface, if the client device has no IP address in this way, you may need to configure a static IP address for your computer first.
However, if it doesn't work either, you could reset the C7 to factory defaults and set up the WDS again, but please remember to change the C7 LAN IP to 192.168.0.2 before disabling DHCP and enabling WDS.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 771
Replies: 7
Voters 0
No one has voted for it yet.