Tobias Walkowiak wrote:
On Wed, Nov 16, 2005 at 04:21:00PM -0800, Dag Richards wrote:
pfsync0: flags=41<UP,RUNNING> mtu 1348
pfsync: syncdev: em1 syncpeer: 192.168.10.3 maxupd: 128
hm, i get
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
...
status: active
inet 10.250.0.1 netmask 0xffffff00 broadcast 10.250.0.255
...
pfsync0: flags=41<UP,RUNNING> mtu 1348
pfsync: syncdev: xl0 syncpeer: 224.0.0.240 maxupd: 128
although i chose 10.250.0.0/24 as the pfsync-net between both NICs. so,
The above output means you did not choose what you think you did.....
doesnt the syncpeer have to be from that class-c net? my hostname.pfsync0
Same network yes ... class c no
says
up syncdev xl0
did i forget something?
cheers
should look like this
fw0# cat hostname.pfsync0
up syncpeer 192.168.10.3 syncdev em1
I think that must be why you pfsync0 device using a multicast addr, you
have not told it what the peer is.
