Slight correction to my previous posting as I forgot that nmap only scans
the first 1000 ports by default. If I do the following command (on the
router) with my iptables started on the router "nmap -sU -p 7777 127.0.0.1"
I get that 7777 is open. If I scan my router from a different machine with
the router iptabes started i.e. "nmap -sU -p 7777 my_router_ip" I get the
port is closed. This lead me to believe that my iptables were to blame, so
I stopped my iptables on the router issued the same two commands from as
before from each machine and the same responses occurred. Anyone have any
----- Original Message -----
From: "David A. Osborn" <david.osborn,AT,mchsi,DOT,com>
Sent: Tuesday, August 26, 2003 8:04 PM
Subject: Re: cipe/router
> Thanks for the quick reply. Currently the two CIPE machines can't even
> each other. This problem just started today. If I do a UDP port scan of
> either system running CIPE should the CIPE port show up? Currently I have
> everything set to use port 7777 but an nmap scan (-sU option) doesn't
> reveal this port. I tried this both with iptables started and stopped.
> Like I said earlier I was able to ping between the CIPE connection today,
> but I made some changes to the iptables and did a restart and now can't.
> The connection doesn't work with iptables stopped though so I am assuming
> that that is not the problem.
> ----- Original Message -----
> From: "Peter van den Heuvel" <peter,AT,bank-connect,DOT,com>
> To: <cipe-l,AT,inka,DOT,de>
> Sent: Tuesday, August 26, 2003 7:03 PM
> Subject: Re: cipe/router
> > > I have a LAN of windows computer that are connected to the Internet
> > > through a computer running Redhat 9 acting as a router using NAT. I
> > > trying to connect an external Redhat 9 computer into the LAN using a
> > > CIPE VPN connection to the router. At one point I actually had the VPN
> > > connection between the external computer and the router working, but
> > > could not ping the internal network from the external computer. After
> > > messing with my iptables thinking that was the reason I couldn't get
> > > the internal network, I managed lose the ability to connect the
> > > computer to the router through the VPN. Does anyone know of a
> > > comprehensive tutorial for doing the about scenario? I hate to waste
> > > everyone's time with questions if there is a tutorial I can be pointed
> > Don't be confused by the fact that you're using cipe. It's all generic
> > networking knowledge, not specific to cipe:
> > - cipe works over some network; usually Internet.
> > - make sure the two cipe machines can ping oneanother.
> > - disable all iptables stuff (allow all for input and output).
> > - bring up cipe and make sure you can ping the other end-point.
> > - now try to ping something beyond the endpoint.
> > If the last step does not work, you simple have a route problem:
> > you must add a route to the remote network on the local cipe machine,
> > setting the remote cipe machine as the gateway. Make sure to only use
> > the "private addresses". All IP's to the "Internet" are irrelevant here.
> > Peter
> > --
> > 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:
> 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: