Date: Tue, 6 Jun 2006 03:12:43 -0700 From: "Kian Mohageri" <kian.mohageri@gmail.com> To: freebsd-pf@freebsd.org Subject: Re: pfsync after reboot does not synchronize Message-ID: <fee88ee40606060312g76781303p5f8c313911cde4e6@mail.gmail.com> In-Reply-To: <20060606041001.GA4870@verio.net> References: <20060605234031.GA4787@verio.net> <fee88ee40606051828i6b0207b5sad96f76985fcd046@mail.gmail.com> <20060606041001.GA4870@verio.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> As you can see, no IP is put on the sync interface; it is merely > configured up. Auto-negotiation succeeds on both ends of the cross > cable: All the examples I've seen give the syncdev an IP address, my setup included. I'd try that. It's strange that it works partially without having done that, though. Maybe someone with more pfsync knowledge could explain why for me? I'd imagine it has something to do with sending out via multicast. http://www.benzedrine.cx/pf/msg04781.html > > Note that the "set skip" is on the pfsync0 pseudo interface, while the > "pass quick" is on the actual fxp0 interface. My apologies, I misread that :) Is there a protocol other than pfsync that should be permitted on that > interface? I didn't expect I'd see any other protocol there, so I > didn't bother to allow anything else. You don't need anything other than pfsync to pass on fxp0 for this to work. Kian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fee88ee40606060312g76781303p5f8c313911cde4e6>