tron@lyssa.owl.de (Matthias Scheler) writes:

> That should not happen. When the packets get to the external interface
> they are already encapsulated and thus originating from 24.112.22.6.
> 
> What does "ifconfig ipip0" on both systems say?

It appears that there is a bug.

Try #1:

ipip0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1480
        inet 204.152.186.42 --> 195.66.28.130 netmask 0xfffffffc 

20:02:30.034585 moghedien.rc.vix.com > rd1154.quicknet.nl:
moghedien.rc.vix.com > 192.168.42.1: icmp: echo request (ttl 255, id
58051) (ttl 255, id 58052)

Try #2:

ipip0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1480
        inet 192.168.42.2 --> 195.66.28.130 netmask 0xfffffffc 

20:16:10.731628 192.168.42.2 > rd1154.quicknet.nl:
moghedien.rc.vix.com > 192.168.42.1: icmp: echo request (ttl 255, id
2497) (ttl 255, id 2498)

It seems to me the gre method for this should be saner.  Here's what
makes sense to me anyway:

	ifconfig ipip0 192.168.42.2 192.168.42.1 netmask 255.255.255.252
	ipipcfg ipip0 204.152.186.42 195.66.28.130

That would be what "makes sense" to me -- set up the interface, and
then set up the tunnel.

--Michael