Having announced last night that I had fixed the problem I now have 
to reply to one of my postings once again to announce that the 
problem is there - bigger and badder than ever... actually it's a 
different problem now...

basically I can get the interface recognised but it's not receiving 
or transmitting anything as far as I can tell - basically the network 
segment it's serving is pretty dead as far as the clients are 
concerned. Following are some diagnostic type things that may help....

[root@server src]# ifdown eth0

[root@server src]# ifup eth0
SIOCADDRT: Network is unreachable

[root@server src]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:40:95:1A:07:89 
           inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:4 overruns:0 frame:0
           TX packets:0 errors:146 dropped:0 overruns:0 carrier:0
           collisions:0

[root@server src]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
139.139.65.60   *               255.255.255.255 UH    0      0        0 ppp0
192.168.2.1     *               255.255.255.255 UH    0      0        0 eth0
192.168.2.0     *               255.255.255.0   U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         139.139.65.60   0.0.0.0         UG    0      0        0 ppp0

[root@server src]# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) from 192.168.2.1 : 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=0 ttl=255 time=0.8 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=255 time=0.6 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=255 time=0.5 ms

--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.5/0.6/0.8 ms

[root@server src]# ./ne2k-diag -p 0x260 -ee -aa -v
ne2k-diag.c:v2.00 4/19/2000 Donald Becker ([EMAIL PROTECTED])
Checking the ethercard at 0x260.
   Receive alignment error counter (0x26d) is 00
   Passed initial NE2000 probe, value 00.
Station Address PROM    0: 00 00 40 40 95 95 1a 1a 07 07 89 89 00 00 00 00
Station Address PROM 0x10: 00 00 00 00 e7 e7 08 08 00 00 00 00 57 57 57 57
   NE2000 found at 0x260, using start page 0x40 and end page 0x80.
The current MAC stations address is 00:40:95:1A:07:89.
8390 page 0: 20 3c 78 7f 01 00 00 40 20 00 5b 03 01 00 00 00.
8390 page 1: 60 00 40 95 1a 07 89 4c 00 00 00 81 00 ff 00 80.
8390 page 2: a0 4c 80 27 40 78 00 20 00 9c 00 40 20 00 4d 00.
8390 page 3: e0 00 40 95 1a 07 89 00 00 00 00 81 00 ff 00 80.

[root@server src]# cat /etc/conf.modules
alias char-major-108 ppp
alias eth0 ne
options eth0 io=0x260 irq=5

[root@server src]# ping 192.168.2.107
PING 192.168.2.107 (192.168.2.107) from 192.168.2.1 : 56(84) bytes of data.
 From fw (192.168.2.1): Destination Host Unreachable
 From fw (192.168.2.1): Destination Host Unreachable
 From fw (192.168.2.1): Destination Host Unreachable

--- 192.168.2.107 ping statistics ---
5 packets transmitted, 0 packets received, +3 errors, 100% packet loss

can anyone enlighten me as to what's going on - it all seems fine to 
me from here... should be working right? Why is the card not 
responding?

- dan.

At 10:04 PM +1100 30/8/00, Dan Horth wrote:
>ok - now I'm feeling a bit sheepish! I got donald becker's ne2k 
>diagnostic utility and tried using it to check my card - which 
>didn't come back  with any promising results - after screwing around 
>with a bunch of other stuff I decided to try some different io ports 
>and found that the io listed in my conf.modules was infact incorrect 
>- it's 0x260 not 0x300 as I previously had in there...
-- 

        Nitro - 3D Visualisation, Graphics & Animation
                Ph (+61 2) 9810 5177 - Fx (+61 2) 9810 0199
                        http://www.nitro.com.au/



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to