s2s over WAN

[Sifter]

Is s2s (v1) encrypted in any sort of way? If I were to run wireshark and sniff the packets would I be able to see anything? What ports are used by s2s?

Also, does s2s depend on netbios packets in order to see the other s2s servers? If this is the case, can one specify by IP address? Netbios discovery is not supported over regular ipsec vpn. One would have to use openvpn to get netbios support.

And finally, does s2s do bit layer examination/copies to avoid copying the same thing over and over, and just copying what has changed?

[Sifter]

Wow 30 views and no takers? I must have stumped you all.

[Phoenix32]

I am a hardware guy, not software, and I don't use S2S. Sorry.

[blue68f100]

Some inside info. The s2s use JVM if that helps. I do not know if it encrypts it but my guess is know since in most cases they are sync in the same server room. You should beable to use wireshark if you use a hub or a switch so you can capture the packets.

We do have a few users that use s2s but not us. Sorry

You can test it and pass the info onto to us. This is the way the open forum works.

[Sifter]

So Im thinking that this is more of a limitation of my current firewall at the moment. Im running a wrap board (233 MHz AMD Geode SC1100 CPU (fast 486 core)) with 128meg of memory running m0n0wall, and set my 4100 up on the 3rd interface, which is my dmz. Added firewall rules to only allow the 4 ports needed for s2s to communicate with the 2nd interface, which is my lan. It took about 2 minutes, but the 4100 found my 4000 on the different network and started the sync. I consistently ran 15mbps. The cpu on the wrap board ran around 92%. I have a watchguard x700 on the way (Ill be running pfsense on it) that is a much more powerful box, so Ill be curious to see what kind of throughput Ill get on it. Its stats are a PIII 1.4 MHz, with 512meg of memory, and 6 interfaces.