RE: options config...|
Thu, 13 Feb 2003 00:00:36 +0100|
It's easier than that: from your peer, ping the ptp address (the CIPE
address) and then on your local system, do a tcpdump -i eth0 udp port xxxx
You should see the encrypted packets arriving.
> -----Original Message-----
> From: Amith Varghese [SMTP:amith,AT,xalan,DOT,com
> Sent: Wednesday, February 12, 2003 2:40 PM
> To: cipe-l,AT,inka,DOT,de
> Subject: RE: options config...
> > Probably you are using your firewall to filter incoming packets so the
> > packets will only pass through if it the conversation is "established"
> > since UDP is a connectionless protocol, there is a timer where after
> > amount of inactivity the return packets are no longer considered as part
> > an "established" conversation.
> > You will need to let ALL UDP packets for the appropriate port (from your
> > peer's IP address) through the firewall.
> In my request for them to open a port I told them to open up port xxxx for
> UDP traffic. I don't know how they could screw that up. Is there any
> easy way
> to run a UDP daemon on that UDP port (when CIPE is down) to check to see
> that port is open? I know I could write a C program, but its been a
> *long* time
> since I've written anything in C.
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: