Date: Thu, 15 Mar 2001 19:00:08 -0600 From: "Thomas T. Veldhouse" <veldy@veldy.net> To: <freebsd-stable@FreeBSD.ORG> Subject: Bridging and IP on one interface Message-ID: <001101c0adb4$722d3de0$0100a8c0@cascade>
next in thread | raw e-mail | index | archive | help
I was wondering if anybody else has noticed the following symptoms -- and if this is the expected behavior. I use two Linksys cards (dc driver) in my machine that firewalls my DSL connection. Since I have 4 bridged IP addresses assigned by my ISP (these are non-routed IPs), I have chosen to bridge them across the interfaces. I generally set the internal interface to one of the IP addresses so that I can run basic services like http, smtp, imap, dhcp, dns, etc. I chose the internal interface because I need to run dhcpd on it for my network. This has worked well enough in the past (on and off depending on the state of the bridging code). Currently, it does not work as expected. All machines internal and external can see all the bridged IP addresses OK. However, the machine running the bridge can not see any external (Internet) addresses. I can ping internal addresses just fine, but external addresses are not accessible. I have tried shifting the IP address to the external interface, but then the machine can not see the internal network. It appears the local machine can not communicate across the bridge as the other machines on the network do. This exact setup used to work until I built the world to just prior to 4.3-BETA. I have opened the firewall wide (ipfw add 1 allow all from any to any) -- and I even tried compiling the kernel with the default to accept on firewall rules. Nothing allows communication across the bridge for the local machine. Is this expected behavior? Thank you, Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001101c0adb4$722d3de0$0100a8c0>