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.
Here you go guys, this is the output for 'ifconfig -a' , 'iptables -L -v -n' and my route dump.
I've disabled iptables and there are no policies configured so I'm not sure if this is an issue. Unless I need a policy to allow for packets to come in and out?
It appeared to me that you have high counts of collisions. Do you have spare NICs and a Hub/Switch? Try to isolate. It could be harware or cable causing it.
Is the "route -n" dump from other box? Its IP is different from what is in your eth0's "ifconfig -a" dump. It looks to me that your route is okey though noticed that in "route -n" eth0 is 10.0.1.3 whereas in your "ifconfig -a" it's 10.0.1.1. If this is in the same box, this could be a problem.
You can try to view this config file: /etc/sysconfig/network-scripts/ifcfe-eth0. For what I can recall (coz I'm no longer using RH) your network settings are stored here. As with Slackware it is in /etc/rc.d/rc.inet1.conf (not quite sure also since I also stopped using Slackware). Sometimes I just don't need to run ifconfig to change my IP, netmask and gateway, I just have to edit this file via vi or joe or whaterver.
Try to change all your netmask to 255.0.0.0.
Since you disabled your firewall and that all your chains' defalult policy is ACCEPT, you should be able to accept connections from everywhere. Though still ask others opinion coz I'm not that really familiar with iptables coz I'm using OpenBSD's PF instead as firewall.
This is what I can give based on my very limited knowledge. I still consider myself a newbie.
Originally posted by gani Is the "route -n" dump from other box? Its IP is different from what is in your eth0's "ifconfig -a" dump. It looks to me that your route is okey though noticed that in "route -n" eth0 is 10.0.1.3 whereas in your "ifconfig -a" it's 10.0.1.1. If this is in the same box, this could be a problem.
Good point! Plus there is no network address route defined for eth0. The output of "route -n" should look the same on both systems. Only the output of ifconfig should be different. i.e .The IP address. Also note that the default gateway should fall within the host address range for the network address (192.168.8.0/24 in my example).
Originally posted by gani The default gateway could be his ISP's gateway: 131.198.115.1?
True! If the output of ifconfig -a showed another interface like ppp0, eth1, etc... Given that ifconfig -a only shows eth0 and lo, there is no way that the default route can work as shown. Which of the "defined" interfaces will issue an arp for the 131.198.115.1 address? None of the defined interfaces/routes (as shown) fall within the host address range/network address.
I'd like to thank everyone for their insightful input. The discrepancies found are due to me copying and pasting configs from a totally different machine. The computers I'm having problems with are in a secure lab so there is really no way for me to easily copy and paste the stuff for everyone to see.
After further troubleshooting and some assistance I was able to get the machines to ping one another. To be honest I don't think I know what the problem was but after playing around with the configs I ruled out that routes were fine, the firewall issue was fine and basically all config issues were fine. I even hardcoded the mac addresses of the opposite machine in the arp table thinking somehow the mac addresses weren't recognized. At one point I would ping a computer and the pings would hang. This indicated to me that packets were sent to the hub but weren't getting to the other machine. So after powering down the hub and leaving it offline for a few minutes the problem seemed to clear. My guess is that the hub got confused during all the changes and simply wasn't advertising to its ports. I'm still not sure but that's the best I can come up with.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.