Date: Fri, 2 Feb 2001 13:31:29 -0700 (MST) From: Nick Rogness <nick@rapidnet.com> To: parminder.mudhar@bt.com Cc: freebsd-net@FreeBSD.org Subject: RE: Routes and tunnels Message-ID: <Pine.BSF.4.21.0102021305510.33204-100000@rapidnet.com> In-Reply-To: <71DA16F18D32D2119A1D0000F8FE9A9409D21C69@mbtlipnt01.btlabs.bt.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 1 Feb 2001 parminder.mudhar@bt.com wrote: > Nick > > Thanks for taking the time to reply to query. Here is more information that > may help you. No problem. Comments below. Sorry for the late reply. [snip] > > the_swamp# ifconfig gif0 132.146.115.164 132.145.113.1 > the_swamp# netstat -rnf inet > Routing tables Are you using gifconfig(8) to configure the outside header of the tunnel? I am running several tunnels using gif and have never had a problem yet. Also check your firewall. Here is an example of one of the tunnels: | | FreeBSD1 | | FreeBSD2 192.168.1.0/24 --- 1.1.1.1 -|- Internet -|- 2.2.2.2 --- 172.16.1.0/24 Gif Tunnel: 10.1.1.1 <--|------------|--> 10.1.1.2 | | | | //On FreeBSD1: # gifconfig gif0 inet 1.1.1.1 2.2.2.2 # ifconfig gif0 10.1.1.1 10.1.1.2 netmask 255.255.255.252 # route add -net 172.16.1.0 10.1.1.2 -netmask 255.255.255.0 //On FreeBSD2 # gifconfig gif0 inet 2.2.2.2 1.1.1.1 # ifconfig gif0 10.1.1.2 10.1.1.1 netmask 255.255.255.252 # route add -net 192.168.1.0 10.1.1.1 -netmask 255.255.255.0 That should be all you need. Like I mentioned earlier, also make sure that your firewall is letting it through. Nick Rogness - Keep on routing in a Free World... "FreeBSD: The Power to Serve " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0102021305510.33204-100000>