Routing between 2 networks - HotUKDeals
We use cookie files to improve site functionality and personalisation. By continuing to use HotUKDeals, you accept our cookie and privacy policy.
Get the HotUKDeals app free at Google Play

Search Error

An error occurred when searching, please try again!

Login / Sign UpSubmit

Routing between 2 networks

£0.00 @
Hi I have 2 networks in one building 192.68.1.x & 10.10.10.x Currently these are not connected They both need to have access to a device on 192.168.1.200. Normal traffic HTTP, FTP, Telnet, Mu… Read More
TomT Avatar
6y, 8m agoPosted 6 years, 8 months ago
Hi
I have 2 networks in one building 192.68.1.x & 10.10.10.x
Currently these are not connected

They both need to have access to a device on 192.168.1.200. Normal traffic HTTP, FTP, Telnet, Multicast etc.

Obviously for the 192.168.1.x range this isn't an issue, bot how do I get 10.10.10.x to have access without compromising either networks security..

On 192.168.1.200 I can configure routes !

I've been told D-Link or Netgear route will work, anyone any ideas or advice on models and how to !!

Thanks for your advice..
TomT Avatar
6y, 8m agoPosted 6 years, 8 months ago
Options

All Comments

(18) Jump to unreadPost a comment
Comments/page:
#1
you could ID the 2 subnets as VLANs on a layer 3 switch using RIP or OSPF with 192.168.1.200 as your gateway

any reason why you can't put the whole network on the same subnet?

i haven't the time to check what models of router can do this. sorry


Edited By: Alfonse on Oct 14, 2010 11:05: df
#2
Thanks
any reason why you can't put the whole network on the same subnet?


2 unique clients in one serviced office. Landlord wants them to share one device, but he can't join the networks.

Any simple how to's etc.. would be great :)
#3
But 2 IP addresses on the shared device and it will appear on both networks. Job done.

p.s. they may as well all be in the same subnet as subnetting doesn't offer any security at all.

Edited By: ro53ben on Oct 14, 2010 11:28: added p.s.
#4
Unfortunately the shared device can only have one IP Address !
#5
TomT
Unfortunately the shared device can only have one IP Address !


can you do a network diagram for us to explain, what is the share device etc
#6
Assuming you're on a budget, but the shared device in a 3rd subnet on the same network as your internet access. Then put both customer networks each behind a domestic router. They will both have access to the shared device but neither to each other's networks.
#7
Assuming you're on a budget, but the shared device in a 3rd subnet on the same network as your internet access. Then put both customer networks each behind a domestic router. They will both have access to the shared device but neither to each other's networks.

Hmm.. can you explain this a bit more ?

Thanks
#8
you have a router for internet access, right? plug the shared device into it as well as the 2 routers from the customer networks. Job done.
#9
I take it this will only work if they are both using the same router for internet access ?
#10
http://img233.imageshack.us/img233/3702/captureic.png
#11
TomT
I take it this will only work if they are both using the same router for internet access ?


They will be using their own router for internet access and those routers will each be using the same router as their external gateway.

VLAN will only work if you have kit that supports it, you likely don't.

Edited By: ro53ben on Oct 14, 2010 13:09: added vlan info
#12
Hi
I seem to think each 'client' has there own DSL and router. So the networks are completely standalone.
#13
Well, don't try and join them then!

What's this mysterious shared device? Why would they share it and not a network connection?

Incidentally if they run over the same switches, just on a different IP range, they are not standalone at all

Edited By: ro53ben on Oct 14, 2010 15:34: added info
#14
ro53ben
Well, don't try and join them then!

What's this mysterious shared device? Why would they share it and not a network connection?

Incidentally if they run over the same switches, just on a different IP range, they are not standalone at all


yeah reinforces the need for a quick diagram just to see clearly whats going on.
banned#15
Get a professional in or learn to do your job properly.
#16
ro53ben
Well, don't try and join them then!

What's this mysterious shared device? Why would they share it and not a network connection?

Incidentally if they run over the same switches, just on a different IP range, they are not standalone at all

yeah reinforces the need for a quick diagram just to see clearly what's going on.


The kit is a bespoke IP Call Manager, it can only have one IP address specified on it.

The clients have their own data networks, their own DSL & routers and don't share the switches etc.

The landlord wants them to share the CallManager, so we need it to be accessible via both networks.

Get a professional in or learn to do your job properly.

LOL
#17
From what you have said, there's no way of doing this securely unless you purchase 2 dedicated firewalls, one for each LAN, and put the call manager in-between in a DMZ.

Not sure why 2 separate companies, with their own data connection, would want to share a VoIP system.
#18
Not sure why 2 separate companies, with their own data connection, would want to share a VoIP system.


I agree :) But it's not my decision..

Post a Comment

You don't need an account to leave a comment. Just enter your email address. We'll keep it private.

...OR log in with your social account

...OR comment using your social account

Thanks for your comment! Keep it up!
We just need to have a quick look and it will be live soon.
The community is happy to hear your opinion! Keep contributing!