From owner-freebsd-questions Tue Apr 1 07:09:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA05808 for questions-outgoing; Tue, 1 Apr 1997 07:09:19 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA05794 for ; Tue, 1 Apr 1997 07:09:14 -0800 (PST) From: sweeting@tm.net.my Received: from mail.tm.net.my (janeway.tm.net.my [202.188.0.155]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id HAA14690 for ; Tue, 1 Apr 1997 07:08:58 -0800 (PST) Received: from [202.184.153.110] ([202.184.153.110]) by mail.tm.net.my (8.8.5/8.8.4) with SMTP id WAA17772; Tue, 1 Apr 1997 22:55:46 +0800 (SGT) Date: Tue, 1 Apr 1997 22:55:46 +0800 (SGT) X-Sender: sweeting@mail.tm.net.my Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org Subject: Re: [Q] why not use routed ? Cc: softweyr@xmission.com, langfod@dihelix.com Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A lot of thanks to David Langford and Wes Peters for the advice on routing. Switching routed off and adding the route works fine. At the moment i call a simple script from /etc/rc.local, which is : ifconfig ep0 202.184.153.5 netmask 255.255.255.255 alias ifconfig ep0 202.184.153.30 netmask 255.255.255.255 alias ifconfig ep0 202.184.153.31 netmask 255.255.255.255 alias route add -host 202.184.153.13 127.0.0.1 /usr/local/sbin/httpd No problems. I was just wondering if it should be possible to do the ifconfig aliasing and addition of the route within /etc/sysconfig. I tried this in /etc/sysconfig : ifconfig_lo0="inet localhost" ifconfig_ep0="inet 202.184.153.13 netmask 255.255.255.0" ifconfig_ep0="inet 202.184.153.5 netmask 255.255.255.255 alias" and that didn't work. should it ? chas >sweeting@tm.net.my asked: >% Why is it that people here tend to advise against using routed ? >% From what i understand, routed automatically sets up >% the routing tables so it seems better than specifying static routes. > >David Langford (langfod@dihelix.com) replied: >> The biggest problem with routed is that it acts very stupid. >> [...] >> >> One of the biggest problems is if I have multiple routers on a network the >> other hosts running "routed -q" will arbitrarily" lose the default routes. > >Routed doesn't handle links going up and down all that well. PPP does >a better job, because it's route table manipulations are designed to >work with PPP. As David suggested, if you have a smple network, give >all of the workstations a default route to your gateway machine and let >PPP handle the routing on your gateway. >