From owner-freebsd-current Fri Jul 23 5:23:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from viking.sophos.com (viking.sophos.com [193.82.145.128]) by hub.freebsd.org (Postfix) with ESMTP id EAE28156F3 for ; Fri, 23 Jul 1999 05:23:29 -0700 (PDT) (envelope-from gjvc@trafalgar.sophos.com) Received: from trafalgar.sophos.com (trafalgar.sophos.com [193.82.145.143]) by viking.sophos.com (MAILER-DAEMON) with SMTP id 187AD45C14 for ; Fri, 23 Jul 1999 12:23:37 +0000 (GMT) Received: (qmail 19116 invoked by uid 540); 23 Jul 1999 12:24:19 -0000 Date: Fri, 23 Jul 1999 12:24:19 +0000 From: George Cox To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Adding route to aliased IP address Message-ID: <19990723122419.A18945@sophos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Operating-System: FreeBSD/i386 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Watcha, When an aliased interface is brought up, no route is added for it. This means that packets from an aliased IP address on one interface do not reach other IP addresses on that interface. Adding a 'route add 127.0.0.1' in the startup scripts would fix it. Is there any place that this route command should go in the current startup scripts which I'm ignorant of? :-) Danke! gjvc -- [gjvc] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message