DD-Wrt ClientBridge mode see other PCs and IPs?

MatchToo

Reputable
Apr 6, 2014
2
0
4,510
I **had** DD-Wrt router set with IP 192.168.0.1 when the modem function of the modem/router was used and I could see all (2) other PCs on the wired network from any other PC.

I now have disabled the ADSL2 modem portion, a cell phone tethered and wifi to the router set as ClientBridge and all of the wired-PCs can access the Internet via the router wifi to the phone just fine.

I am using the phone's IP as the gateway 192.168.42.1.

I am using fixed IPs for the wired-PCs, 192.168.42.20, 192.168.42.21 etc.

I also have some security cameras on the wired setup using 192.168.0.50:4560 and 192.168.0.55:4565 to access them.

I can't change the security camera IPs and gateway stuff as their controllers are no longer accessible via the browser due, I think, to the new gateway.

QUESTION: 1:
Now that I am using the phone gateway IP (192.168.42.1), how can I access those two other wired IPs 192.168.0.50:4560 etc?

{edit} I now have the PCs all seeing each other, but still can't see the cameras.
 
Solution
If you can live with not being able to access the camera outside the house you can just add a secondary IP address in your PCs to the 192.168.0.xx network. This would give the pc 2 ip addresses and windows is smart enough to know which to use to accessing the cameras compared to going to the internet.

Otherwise you have lots of work in store and to do it simple you will have to completely redesign.

First option is to go back to router mode. You would define a WAN interface to be the wireless connection to the phone and use the lan back on 192.169.0.x. You would be double NAT.

Second which gets very messy.
Define a second lan vlan. Assign a ip in the 192.168.0.x and make sure the ports your cameras are plugged to are in the...
If you can live with not being able to access the camera outside the house you can just add a secondary IP address in your PCs to the 192.168.0.xx network. This would give the pc 2 ip addresses and windows is smart enough to know which to use to accessing the cameras compared to going to the internet.

Otherwise you have lots of work in store and to do it simple you will have to completely redesign.

First option is to go back to router mode. You would define a WAN interface to be the wireless connection to the phone and use the lan back on 192.169.0.x. You would be double NAT.

Second which gets very messy.
Define a second lan vlan. Assign a ip in the 192.168.0.x and make sure the ports your cameras are plugged to are in the correct vlan.
Put a IP on the router in the 192.168.42.x network in a different vlan and be sure all the ports for your wired pc are in that one.
If your phone supports static routes put in 192.168.0.x and point it to the 192.168.42.x ip you defined for the router. The phone also needs to be able to nat 192.168.0.x addresses to the outside address.
If it does not support static you must put static in all the PC with the route command that say 192.168.0.0/24 is at 192.168.42.x. You must also configure the router to nat ip that are going from the 192.168.0.x network to the internet to be natted to 192.168.42.x...again a double nat.

I would opt for the secondary IP method if you can live without access to the cameras from the internet.
 
Solution

MatchToo

Reputable
Apr 6, 2014
2
0
4,510
Thanks for taking the time to write so much detail. I have been messing with it and not quit egetting what I need. I have two of the cameras visible, but not the third which uses a different older system. I will have to get it and hook it directly to the computer and change the gateway and that might/should fix it.

I was hoping DD-Wrt had an easier approach. I have an old TP-Link router (non-DD-Wrt) with dead-wifi and it has the option for two IP addresses. It will test both ranges when called. I may just push that in between the cameras and the current DD-Wrt router. More work for now, but might be the best option in the long run.

Thanks again for the information.