Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The product I work on has a communication network of 192.168.0 (four systems 100, 101, 102, and 103). From time to time there is a desire to patch in a set of these systems (using their 192 addresses) to the site network to communicate using various instrumentation tools that have tight licensing that is bound to a site machine.

Apparently this poses a non-trivial route issue as 192 addresses could pop up here, there or anywhere (However only one set of 192's on the site at any one time obviously).

Thank you kindly for your help.

share|improve this question
add comment

3 Answers

up vote 2 down vote accepted

A router of some sort (i.e. router or firewall) is the obvious answer to connect the two networks. If IP address conflicts are a concern, then using NAT will prevent problems.

Always be careful when connecting development to production. You could accidentally bind to the production database and delete a table or something... not that this ever happens of course.

share|improve this answer
    
So I have the router DHCP from site and then do the NAT translation for the 192 addresses without involving the IT dept to setup VLANs. Thank you much. –  another average joe May 22 '09 at 17:50
1  
I wouldn't recommend connecting networks, routers or firewalls without involving your IT department. You run the risk of creating a network loop or breaching security. In many companies, doing something like this is a fire-able offense. –  Peter May 22 '09 at 20:30
    
I agree with the statement above, however when I mentioned "not involving my IT dept" I meant, "once this solution is cleared with IT I can use it and do not require IT to setup VLANs each time I need to connect up a new set of 192 computers at a different router port". Basically saying if they agree after that point they do not need to assist me in settig it up; I can just plug it in use it, then unplug it. Cheers! –  another average joe May 22 '09 at 20:48
add comment

There is a related post here, and here is (my)an answer that is directly related to your issue. In your case, routing private addresses to the public is not a concern, although it does explain why you will have routing issues (initially). The simple solution would be to look at a VPN setup that would "tie" the different networks together. This would solve your routing problem while connecting secure all at the same time.

share|improve this answer
add comment

If you need an exception for a system to jump subnets look into the windows route command. It is often the solution to these kinds of things (assuming your on a windows machine). This works especially well in a temporary situation where adding new hardware might be more cumbersome.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.