I have been using a packet monitor (WinDump, i.e. a tcpdump clone for
Windows). The hex dumps of the packets are taken with WinDump at the Windows
end of the connection and with tcpdump at the Linux end. All UDP packets
sent by the Linux box arrive at my computer. The packet IP header changes
along the way because of TTL changes and address changes, but there seems to
be nothing wrong. The UDP part of the packet is otherwise intact but
something has added the checksum along the way.
But, yes, I think I'll try the "Adidas network" next and take my computer
very near to the Linux box.
Thanks for help!
---- Original Message -----
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Sent: Thursday, November 16, 2000 22:28
Subject: Re: Deaf CIPE-Win32
> You're using address translation. You must make sure that traffic going to
> the masquerading router on the chosen CIPE port is forwarded to the right
> box. You don't say how you've verified that the UDP traffic is arriving at
> the NT box from the Linux box. It may be that the UDP packets are
> disappearing into a "black hole" created by the ISP router's address
> translation tables. First, connect the two computers to the same ethernet
> segment and configure them to converse using IP. Then configure CIPE over
> that. If that doesn't work then there is probably something wrong with the
> CIPE-Win32 setup. If it does work, then it's your routing/ISP setup.
> As it stands, you can try to verify whether or not the UDP traffic
> gets to the NT box by using a packet monitor. Until you can verify that
> return CIPE packets are even getting across the WAN to the ADSL modem, you
> can't proceed any further. Don't worry about the checksums just yet.