Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: private network to private network gateway
Special Forums IP Networking private network to private network gateway Post 32714 by TioTony on Wednesday 4th of December 2002 09:26:55 PM
Old 12-04-2002
The easiest solution would be to forget about your machine attached to both firewalls and just configure the firewalls to allow what you want. There are several options, but basically you would configure one or both firewalls to create a tunnel between the two firewalls over the internet. The exact details will depend on your firewall vendor but would go like this:

PC1--FW1=====FW2--PC2

The === would be your tunnel. Depending on your security requirements you may want to make FW2 a VPN endpoint so you can connect from anywhere on the internet to the LAN behind it after you give some credentials. If this is too risky, then you can configure FW1 and FW2 to have a permanent tunnel between the two of them so only PCs belonging to LAN1 or LAN2 can talk to each other and there is no (well maybe a little) chance of anyone not on LAN1 or LAN2 connecting to LAN1 or LAN2 via FW1 or FW2.

Hope this helps. This is basically what you were trying to accomplish with your third PC connected to both Firewalls but there is not need as most firewalls have the functionallity to do this and it is much easier to implement.
 

6 More Discussions You Might Find Interesting

1. IP Networking

Private network

Hi all, Currently we are in the progress of setting up a private network on all of our Sun Solaris servers. Purpose is to move all backup tasks to the private, hence reduce load on public network. Some of our servers only consists of 1 network card but with several ports. Shall we purchase... (10 Replies)
Discussion started by: *Jess*
10 Replies

2. IP Networking

Able to ping server's private network

Hi guys, I'm in the progress of setting up a private network in our Sun solaris platform. Existing ip: 172.16.102.101 New private ip: 192.168.2.3 Netmask is the same for both private & public 255.255.255.0 After setting up the ip, I'm able to ping this private ip address from our... (3 Replies)
Discussion started by: *Jess*
3 Replies

3. UNIX for Dummies Questions & Answers

Need help setting up a home solaris private network

Hi all, I just purchased 2 Ultra 10 servers and I want to practice with home networking. I want to create a private network where I can connect both boxes to the internet via broadband using my four port adsl modem/router. My ISP assigns me 192.168 addresses via DHCP and I use the ISP's DNS but... (1 Reply)
Discussion started by: Kongowea
1 Replies

4. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

5. IP Networking

How does a router directs the internet traffic to a specific host in the private network?

how does a router directs the internet traffic to a specific host in the private network? Example: My PC has ip 192.168.134.100 Router has ip 192.168.134.200 My company's ip 202.52.150.33 When i try to access internet, say google, it traverses from... (1 Reply)
Discussion started by: Arun_Linux
1 Replies

6. Windows & DOS: Issues & Discussions

Private Network

Hello, I have a desktop which has two network cards installed on it and I connected these two card through a hub. On the desktop in have installed a Windows Vista Home Edition SO and a Windowx XP SO in a virtual way. I also had intalled a Virtual BOX software and Windows XP run through it. By... (1 Reply)
Discussion started by: zendcool
1 Replies

LEARN ABOUT OSF1

iptunnel

iptunnel(8)						      System Manager's Manual						       iptunnel(8)

NAME

       iptunnel - Creates, deletes, and displays configured tunnels

SYNOPSIS

       /usr/sbin/iptunnel  [operation] [args]

DESCRIPTION

       The  iptunnel  command creates configured tunnels for sending and receiving IPV6 or IPV4 packets that are encapsulated as the payload of an
       IPV4 datagram.

       The iptunnel command can perform one of the following operations: Creates a tunnel interface, which  you  must  subsequently  configure	by
       using the ifconfig command. The syntax of the create operation is as follows:

	      iptunnel create [-I int-name] [v4-dest] [v4-src]

	      Specifies  the  interface unit of the tunnel to be created. This is an optional parameter.  The int-name parameter has the following
	      form: iptx, where x is the interface unit number. By default, the interface name selected for the tunnel is iptx+1, or the value	of
	      the  interface  unit  number  of the last tunnel created plus 1.	Specifies the remote end-point to which a tunnel is to be created.
	      Sets the IPV4 source address in the encapsulating header.  The tunnel is enabled (packets are sent/received on the tunnel)  only	if
	      v4-src  is  a valid address on the system.  This is an optional parameter.  Deletes a tunnel interface.  You must disable the tunnel
	      before you can delete it by executing the following command: # ifconfig tunnel name down	delete abort Shows the	tunnel	attributes
	      (name, tunnel end points, next hop for tunneled packets).

EXAMPLES

       To create a tunnel from hobbes to calvin, enter: # iptunnel create -I ipt5 calvin  ipt5  iftype 208 src 16.140.16.86 dst 16.140.16.91

       To display the tunnel attributes, enter: # iptunnel show ipt5 interface ipt5 src 16.140.16.86 dst 16.140.16.91 gate 16.140.16.86 To config-
       uring the tunnel to encapsulate IPv6 packets, enter: # ifconfig ipt5 ipv6 up

	      IPv6 packets will be sent as payloads of IPv4 datagrams from 16.140.16.86 to 16.140.16.91.

	      The tunnel may also be used to send IPV4 packets encapsulated within IPV4 headers as follows: # ifconfig	ipt5  10.10.80.60  netmask
	      255.255.255.0

	      To verify the previous command, enter: # ifconfig ipt5 ipt5: flags=4c1<UP,RUNNING,NOARP,MULTICAST>
		   16.140.16.86 --> 16.140.16.91
		   rxmt 1000, reach time 30000, dad tries 1, mtu 1280, hops 64, token len 64
		   inet 10.10.80.60 netmask ffffff00  ipmtu 1280
		   inet6  fe80::108c:1056  To  deleting the tunnel, enter: # ifconfig ipt5 down delete abort ipt5: delete inet address 10.10.80.60
	      10.10.80.60: aborting 0 tcp connection(s)

	      Then, enter: # iptunnel delete ipt5 interface ipt5 deleted

SEE ALSO

       Commands: ifconfig(8).

       RFC 2003, IP Encapsulation within IP, Perkins, C., October 1996

																       iptunnel(8)
All times are GMT -4. The time now is 10:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy