From owner-freebsd-questions Sat May 20 10:11:56 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 54BD637B5AD for ; Sat, 20 May 2000 10:11:53 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e4KHjFc20466; Sat, 20 May 2000 10:45:15 -0700 (PDT) Date: Sat, 20 May 2000 10:45:15 -0700 From: Alfred Perlstein To: Kirill Ponomarew Cc: questions@FreeBSD.ORG Subject: Re: Routing Table in FreeBSD 4.0 Message-ID: <20000520104515.C28097@fw.wintelcom.net> References: <00052018392100.00771@ponomare.krion> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <00052018392100.00771@ponomare.krion>; from ponomare@uni-duesseldorf.de on Sat, May 20, 2000 at 06:24:16PM +0200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kirill Ponomarew [000520 10:13] wrote: > -----BEGIN PGP SIGNED MESSAGE----- There's no need to PGP sign a support question. > Hallo > I have the following problem with my network configuration: > my normal routing tables is: > Destination Gateway Genmask IFace > 134.99.26.17 0.0.0.0 255.255.255.255 eth0 > 134.99.26.0 0.0.0.0 255.255.255.0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0. etho > 0.0.0.0 134.99.26.1 > > (sorry that i'm using here route table from Linux, I can't mail from FreeBSD > because of network troubles) > > IP is 134.99.26.17 > Gateway is 134.99.26.1 > > the problem is that gateway 134.99.26.1 is behind firewall at the university > I can't use such things like ftp <-- for ports downloading, icq, real audio etc. > On purpose to make our student life better, our UniAdmin has made the second > gateway, we have to log in the second gateway with ssh and then we can use all > services like ftp etc. > The question is - how to add in FreeBSD the second gateway from the other > subnetwork ??? > > IP of second gateway is 134.99.162.254 > I tried the following things: > route add -net 134.99.162.0 -mask 255.255.255.0 0.0.0.0 wrong. > route add default 134.99.162.254 right, but you must: 'route delete default' before applying this command. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message