From a relative newbie...
I have an embedded box running a 2.4.23 kernel.
Its got inetd configured for telnet and ftp (both work AOK from a
local connection).
I am trying to access the box via an openvpn tunnel.
I can launch the tunnel OK (over PPP, also running OK).
When I try to telnet or FTP to the other end of the tunnel, nothing
happens.
The tunnel-provider swears the request packets are forwarded to the
embedded box...
So - where does inetd listen for requests ?
What if anything do I need to do to the route table so that inetd
listens for requests from the tunnel ?
Any tips on how to debug, including tools to log what's showing up via
the tunnel ?
Thanks in advance for any help,
Best Regards, Dave
PS: here are the default and a suggested route setting; neither
worked...
netstat -nlp|grep 21
netstat -nlp|grep 23
route
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 96/inetd
udp 0 0 0.0.0.0:1024 0.0.0.0:* 217/openvpn
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 96/inetd
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.8.2.161 10.8.2.165 255.255.255.255 UGH 0 0 0 tun0
10.0.0.1 * 255.255.255.255 UH 0 0 0 ppp0
10.8.2.165 * 255.255.255.255 UH 0 0 0 tun0
default * 0.0.0.0 U 0 0 0 ppp0
route del defaultQuote:>>>> Change default route per suggestions, report again...
route add default dev tun0
netstat -nlp|grep 21
netstat -nlp|grep 23
route
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 96/inetd
udp 0 0 0.0.0.0:1024 0.0.0.0:* 217/openvpn
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 96/inetd
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.8.2.161 10.8.2.165 255.255.255.255 UGH 0 0 0 tun0
10.0.0.1 * 255.255.255.255 UH 0 0 0 ppp0
10.8.2.165 * 255.255.255.255 UH 0 0 0 tun0
default * 0.0.0.0 U 0 0 0 tun0