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.
using RH 7.1
when on the pc, i can use any services (telnet to myself, ssh, httpd) but when i try to connect from the outside (my pc at work) i can't. hosts.allow/deny don't have anything.
what can be blocking ouside connections? ipchains seems to be allowing all tcp connections from anywhere to everywhere...
can't even get to the login prompt. on telnet the connection just times out. on httpd (if i try to connect to my ip through a browser) it doesn't connect either, timeout. but the same things i can do from this machine with no problem.
i'm thinking maybe it's a firewall problem. but this is what ipchains gives me:
[root@24-168-135-170 val]# /sbin/ipchains -L
Chain input (policy ACCEPT):
target prot opt source destination ports
ACCEPT udp ------ nycdns4fa.rdc-nyc.rr.com anywhere domain -> any
ACCEPT udp ------ nycdns3fa.rdc-nyc.rr.com anywhere domain -> any
ACCEPT udp ------ anywhere anywhere bootps:bootpc -> bootps:bootpc
ACCEPT udp ------ anywhere anywhere bootps:bootpc -> bootps:bootpc
ACCEPT all ------ anywhere anywhere n/a
REJECT tcp -y---- anywhere anywhere any -> 0:1023
REJECT tcp -y---- anywhere anywhere any -> nfs
REJECT udp ------ anywhere anywhere any -> 0:1023
REJECT udp ------ anywhere anywhere any -> nfs
REJECT tcp -y---- anywhere anywhere any -> x11:6009
REJECT tcp -y---- anywhere anywhere any -> xfs
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):
How is your PC at work connected? As the risk of instulting you intelligence can you ping your home machine? Are you sure that your work's network doesn't only have http access via a proxy so your ipchains rule of allowing connections from nycdns4fa.rdc-nyc.rr.com (I'm assuming this is your work address) doesn't match the proxy's IP, and all other IP don't get out of your work's network.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.