Re: [SLE] Problem Installing NIC in SuSE 8.0

Thanks again for the help. Before hooking up cables again I tried the arp -n (since it's easier) and got this: armand:/home/kjgraham # arp -a ? (169.237.94.254) at <incomplete> on eth0 Now we're getting somewhere. I just don't know where! Ken At 03:44 PM 6/20/02 -0700, you wrote:

Yeh, you do not have a firewall running.

This just got to be a routing problem. I noticed that ju said you got destination unreachable when using cross over cables..

If I were you I would try the crossover cables once again.

169.237.94.131 | 169.237.94.0/24 | 169.237.94.132

In this case remove default gateway. route del default gw 169.237.94.254

The routing table should look like this on both machines.

169.237.94.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

Do a ping from the 132 machine and if you get destination unreachable. The arp is not working. You will probably get timeout if it is not working...

After that check the arp cache with arp -n: No you have an arp entry like this on 132???

169.237.94.131 ether 00:04:5A:62:21:DB C eth0

Using crossover cable can once and a while be a hazzle. After connecting the cable make sure you do this: 1. ifconfig eth0 down on 131 2. ifconfig eth0 down on 132 3. ifconfig eth0 up on 132 4. ifconfig eth0 up on 131

It is better is you have a hub in between, they work with just plugin the cable.

/Magnus

Ken Graham wrote:

...

When I boot the system I get the message "personal-firewall not active [unused]" I assume that means that I'm not using a firewall. Also I have no inet services active. I ran iptables (see below) but it doesn't tell me anything. Does this look right? I ran iptables on the the Linux box that works and got the same results. ___________________________________________________ armand:/etc/sysconfig # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination I also changed the two lines FW_ALLOW_PING to yes. Still doesn't work.... Thanks again, Ken At 02:15 PM 6/20/02 -0700, you wrote:

...

Hmm, the NIC is dropping incoming packets. Do you have a firewall blocking stuff? I have repeatedly got kicked in the butt because I had a firewall enabled dropping pings. Run iptables -L or ipchains -L to check if you have that running. Might want to shutdown the firewall briefly to test. SuSEfirewall stop or SuSEfirewall2 stop. Make sure to start it later if it is running.

If I were you I would look for FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="yes" in /etc/rc.config.d/firewall.rc.config

I believe Yast2 has a GUI for this kind of stuff...

Everything else seems to be correct....

/Magnus

Ken Graham wrote:

...

Thanks for the quick replies. I'm certain that this is not a hardware issue since I've replaced the NIC (it is a PCI NIC) with a working one and this NIC will work in another box. Also, I used a crossover cable to check between two working systems and the bad one - so it's not the LAN. Thanks for the 'hwinfo --network_ctrl' command it may direct me towards the problem (see below) Here's the output from the bad Linux box: armand:/home/kjgraham # ifconfig eth0 Link encap:Ethernet HWaddr 00:04:5A:62:21:DB inet addr:169.237.94.131 Bcast:169.237.94.255 Mask:255.255.255.0 inet6 addr: fe80::204:5aff:fe62:21db/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:21917 overruns:0 frame:0 TX packets:0 errors:23 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:18 Base address:0xd400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:55 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4660 (4.5 Kb) TX bytes:4660 (4.5 K) _______________________________________________________ armand:/home/kjgraham # ifstatus eth0 eth0 is up 2: eth0: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:04:5a:62:21:db brd ff:ff:ff:ff:ff:ff inet 169.237.94.131/24 brd 169.237.94.255 scope global eth0 inet6 fe80::204:5aff:fe62:21db/10 scope link Configured routes for interface eth0: default 169.237.94.254 - eth0 Active routes for interface eth0: 169.237.94.0/24 proto kernel scope link src 169.237.94.131 default via 169.237.94.254 1 of 1 configured routes for interface eth0 up _______________________________________________________ armand:/home/kjgraham # hwinfo --network_ctrl 16: PCI 07.0: 0200 Ethernet controller [Created at pci.65] Unique ID: M71A.IH1TcNNtXe0 Hardware Class: network Model: "Linksys Network Everywhere Fast Ethernet 10/100 model NC100" Vendor: 1317 "Linksys" Device: 0985 "Network Everywhere Fast Ethernet 10/100 model NC100" SubVendor: 1317 "Linksys" SubDevice: 0574 "?" Revision: 0x11 I/O Ports: 0xd400-??? (rw) Memory Range: 0xdfffdc00-??? (rw,non-prefetchable) Memory Range: 0xdffc0000-??? (ro,disabled) IRQ: 18 (no events) Driver Info #0: Driver Status: tulip is active Driver Activation Cmd: "insmod tulip" _______________________________________________________ I'm still new to Linux, so bear with me, but I don't like the look of the line "IRQ: 18 (no events)". The good Linux system shows 19141 events for it's IRQ. Is this significant? Thanks again, Ken Graham