From owner-freebsd-hackers  Tue Mar 11 13:17:28 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 820A137B401
	for <hackers@freebsd.org>; Tue, 11 Mar 2003 13:17:27 -0800 (PST)
Received: from priv-edtnes09-hme0.telusplanet.net (outbound02.telus.net [199.185.220.221])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8A0A343F75
	for <hackers@freebsd.org>; Tue, 11 Mar 2003 13:17:26 -0800 (PST)
	(envelope-from sh@bel.bc.ca)
Received: from REASON ([216.232.215.209])
          by priv-edtnes09-hme0.telusplanet.net
          (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP
          id <20030311211726.DJJL26116.priv-edtnes09-hme0.telusplanet.net@REASON>
          for <hackers@freebsd.org>; Tue, 11 Mar 2003 14:17:26 -0700
Message-ID: <000601c2e813$9d849650$d1d7e8d8@slugabed.org>
From: "Sean Hamilton" <sh@bel.bc.ca>
To: <hackers@freebsd.org>
Subject: IP addresses of bridge interfaces
Date: Tue, 11 Mar 2003 13:17:25 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Greetings,

I recently upgraded a FreeBSD 4.6.2 bridge to 5.0, and am having troubles
with how it handles IP addresses.

   router
     |
     | t1
     |
   [fxp0]
FreeBSD bridge
   [fxp1]
     |
  switch
     |
   hosts

The problem is that if the external interface is assigned an address, then
hosts on the same block can't access it. Likewise if the internal interface
is given an address, *only* hosts on the same block can access it! I have
verified that in both cases the bridge has its default route correctly set.

I won't be too suprised if this is due to screwey ISP routing, but I don't
recall this ever being a problem with 4.6.2.

Any tips?

thanks,

sh


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message