On 2012-06-05 03:50, Peter Lothberg wrote: For people who don't need LAT and have a Cisco box, this is way better than the bridge program. (If you really want LAT with other parts of HECnet, then there is no alternative to the bridge...) You can bridge LAT with the cisco box... -:) ((It might even HELP you with LAT over WAN....)) (And it can act as a LAT termianl server) Nice. I did not know that. That's even better. Will it just bridge the protocols you ask for, or will it do them all? Hmm, I assume it's using GRE for this? Johnny I -think- there where special stuff to help with LAT in WAN scenarios, at some point there might even have been a telnet/lat gw.. I have to go and refresh my memory.. There are many ways of putting foo-in-ip, to many, but the cisco box have two that are actually pretty RFC compliant. GRE and L2tpV3. GRE uses the Ethernet protocol ID to demux what's in the packet, and it can be treated as a "interface" and made part of a bridge group. L2TPV3 basically takes a physical port and X-connects that to another physical port on another box across a IP network. If you have a real core that do 4470MTU or 9000MTU, 1500 byte payload is a no_brainer.. As it's IPv6 day, let me mention that in the IPv6 version of L2tpv3 we did a mode where you give IPv6 addresses to logical/physical ports and encap/decap just becomes a push/pop "label" operation, instead as in IPv4, there the outer IPv4 header are interfaces/loopbacks on the endpoint and you have to look inside the packet for a session ID to knew where it actually belongs... Okey, enough... --P