How to see a wifi device on a 2nd router from my main LAN

Mel_P

Mel_P

Mel_P

Soldato
Joined
27 Feb 2004
Posts
2,577
Location
Kent
Hello,

I have set up a temporary internet (IP) camera on a secondary router connected to my network via a homeplug / wifi router. I have done this because it is an old Linksys device (WVC200) that has a lower WiFi security setting than my main Wif network. Also it only shows images with XP (fixed) PC not Win 7 or Win 8 (the latter 2 show internet camera web interface and I can tilt / pan but the active x control won't work in Win 7 or 8).

It all works at the end of a long cable connected via the homeplugs to the XP PC connected to the Virgin hub BUT because of distance, long cable hazard and location I need to connect the internet camera via Wifi. the IP camera only works on WEP however so I wanted to connect it via a second router but I cannot seem to see it via the second network.

I have this:

Virgin Superhub 2 (192.168.0.1) connected to Homeplug near hub.

Homeplug in Kitchen connected to WiFi Router (192.168.0.16) (connections to this router are in the range 192.168.2.100 - 200).

The WiFi Webcam is connected to this router (192.168.2.104) set up to watch garden for pet.

It works OK and I can see the webcam from my laptop plugged in to the router (192.168.2.102) but not from my XP PC plugged into my primary network (192.168.0.4).

I have also tried it on the Super Hub "Guest" wifi but this sets the internet camera as 192.168.1.2.

How can I see the IP camera across the ".1" and ".2" networks please?

Suggestions?

I know I could buy a new IP camera or reduce the security on my superhub wifi - but there must be a better solution?

Thanks, Mel
 
So you've connected a secondary router (using its WAN) port to one of the Superhub's LAN ports (either directly or via Homeplugs)?

If this is the situation then you've opened the entire network up to the limitations of WEP security. Anything connected to the secondary router (wired or wireless) will be able to see everything connected to the Superhub.

As you've found this setup will also stop machines attached to the Superhub from connecting to machines on the secondary router. To allow access I think you'd need to configure static routes on the Superhub (or the indivual PCs) so that it knows where to send traffic destined for the 192.168.2.n subnet (instead of the default gateway). The secondary router would also need configuring to allow the traffic through and route it correctly.
 
Pah! I think I will just use the long cable for a few weeks! Thanks.

We think we have a fox coming in the garden and I thought this would be an easy thing to set up. I bought the IP camera probalby 5 years ago and used it for watching grandchildren (babies) - then put it in ther cupboard for a few years.

It's obviously become obsolete in the intervening period! The Sitecom router web interface is the same - it will not display properly except in XP - probably outdated active-x controls. BIN IT ALL!

I will disconnect my second router and stop using the old IP camera on the insecure wifi - and just put up with the cable for a week or so! Not worth buying a new IP camera to use a few days / weeks and then put it in the cupboard for a few years again.

Thanks, Mel
 
I know this has been semi resolved with the wep router being removed, but just to answer the original question. If you wanted something with an ip of 192.168.0.1 to see something with an ip of 192.168.2.1 then I think you would need to set the subnets for all devices to 255.255.253.0 (I am a little rusty with networking so may still be wrong :P )
 
AFAIK 255.255.253.0 isn't even a valid mask (it isn't contiguous).

If you want the two subnets to communicate just setup the routers so they know where to send the traffic.

In your case the downstream (192.168.0.n) router needs to know that traffic to 192.168.2.0 isn't destined for the default gateway. Assign a static route and all should be well (firewalls and port forwarding allowing).

The upstream (192.168.2.n) router will already be able to communicate with the 192.168.0.n subnet as that's where its gateway will be pointing to by default.
 
Knew there would be something :p 255.255.252.0 should work then. Usually when I have had a similar situation, I have just disabled dhcp on the secondary router and then ignored the wan part, in this case the IP camera would have got its IP address from the primary router then.
 
It still isn't a masking issue.

The OP was daisy chaining routers which resulted in two separate subnets. The routing in one direction would work by default. Routing in the opposite direction would require some configuration.

If you go down the disable DHCP route then you'll have to be connecting the routers LAN-to-LAN rather than LAN-to-WAN. In this case the secondary router just becomes a wireless access point and switch. There's then only a single subnet to worry about.
 
Kotu said:
Knew there would be something :p 255.255.252.0 should work then. Usually when I have had a similar situation, I have just disabled dhcp on the secondary router and then ignored the wan part, in this case the IP camera would have got its IP address from the primary router then.
Click to expand...

Thanks - I will try this sometime.

Mel
 
You must log in or register to reply here.
Back
Top Bottom