Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
do you have something listening on the port forwarding target ?
maybe choose (and open/forward) a new (previously unused) port and listen there using netcat -l -p portno
(netcat is somtimes called "nc". install it if you don't have it by default.)
then telnet from the OUTSIDE to YOUR_ROUTER_IP OPENPORT and type 123<enter>
and "123" should appear in the shell where you ran netcat.
also, port forwarding might require that you activate "NAT" and/or "masquerading" option in your router (don't know which kind you have...)
if nothin else helps, you might need to sniff where the packets are dropped using ethereal...
...BTW... check the logfile of your router. set it to debug ...
So what's it say...?
Maybe 80 is occupied ? Tried 8081 ?
Quote:
Originally Posted by cskiwi
and the telnet should i execute something like:
telnet OUTSIDE 192.168.0.194 OPENPORT 123
or what?
not realy following you there :S
You go to some machine outside your network, i.e. on the other side of your router, e.g. a friends machine, or an internet cafe, or a remote machine you have access to. Then you type
telnet MYIP MYPORT
where MYIP is the IP that you think you have from the outside. (where your friends are trying to connect to)
and MYPORT is what you gave at -p
root@KiwiServer:~# netcat -l -p 80
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
usage: nc [-46DdhklnrStUuvzC] [-i interval] [-P proxy_username] [-p source_port]
[-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_protocol]
[-x proxy_address[:port]] [hostname] [port[s]]
Well, that works for my netcat, so you need to study the doc for yours.
Anyway, that was just meant at a "quick test" for the connection, if that turs out too complicated, I don't know...
For all that has been done so far, I'm not 100% convinced that you're completely clear about the network route, your external IP vs your internal IP, and settings in your router (hardware box?).
But I have no more ideas how to help you with that.
Rule of thumb:
If "telnet YOUREXTERNALIP SOMEPORT" from OUTSIDE your network does give "connection refused", it means that the route, port and firewall are ok, and you don't have a service listening on the port. If it just times out, there is a firewall in the way somehwere.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.