Henning Brauer wrote:
* Dag Richards <[EMAIL PROTECTED]> [2005-11-17 16:32]:

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: xl0 syncpeer: 224.0.0.240 maxupd: 128


should look like this

fw0# cat   hostname.pfsync0
up syncpeer 192.168.10.3 syncdev em1


that is bad advice.


I think that must be why you pfsync0 device using a multicast addr, you have not told it what the peer is.


and using multicast for pfsync is _perfectly_ fine. that's why it is the default, after all...


Sorry,
I should have stated this as ...

"This is working for me configured this way. I have pfsync running on non dedicated links over an ipsec tunnel".

Thank you sir, may I have another?

Reply via email to