Date: Sat, 3 Feb 2001 22:56:11 -0800 (PST) From: Rich Wales <richw@webcom.com> To: freebsd-net@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: BRIDGE breaks ARP? (more info) Message-ID: <20010204062837.94849.richw@wyattearp.stanford.edu> In-Reply-To: <20010203220223.86591.richw@wyattearp.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Earlier, I reported an ARP problem on a 4.2-STABLE bridge system. A few people wrote me privately, advising me to include a firewall rule passing UDP packets on port 2054 to/from the IP address 0.0.0.0. I've tried this, but it doesn't help any. I should mention, though, that I don't think this firewall rule is relevant in any case. First, the "port 2054" kludge doesn't appear to be in the networking code any more. I grep'ed the entire -STABLE base source for any references to UDP port 2054, and I found nothing at all except for the commented-out line in the etc/rc.firewall file. As far as I'm aware, bridging of non-IP packets is now controlled by the kernel's default "ipfw" rule -- and, yes, I do have the options IPFIREWALL and IPFIREWALL_DEFAULT_TO_ACCEPT in my configuration. Second, I'm not talking about bridging of ARP packets anyway. I'm trying to connect directly to the bridge machine -- but the bridge is failing to respond to requests for its own hardware address on its "rl0" interface. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010204062837.94849.richw>