Problem getting Internet on dual-NIC Slack 10.1 box

keefaz · 07-10-2005, 04:20 PM

Do you use the right network cables, I mean they are not cross over ?
Maybe the hub support both though...

Staedtler · 07-10-2005, 05:16 PM

Quote:

Originally posted by keefaz
Do you use the right network cables, I mean they are not cross over ?
Maybe the hub support both though...

I made sure crossover cables are not being used. I confirmed the link lights on the hub and the cable modem, so the physical connections are fine.

keefaz · 07-10-2005, 05:54 PM

I would not be suprised if you could not ping a XP machine,
(built-in firewall enabled by default) but slackware hasn't
any rules to block ping by default so it should be pinguable...

You tried without the modem connected to the hub didn't you ?

Also you double checked ifconfig in slackware and ipconfig in
windows ? No trouble from this side ? Outputs look correct ?

/sbin/route in slackware and route print in windows both show
the 192.168.0.0 network ?

Staedtler · 07-10-2005, 06:31 PM

Quote:

Originally posted by keefaz
I would not be suprised if you could not ping a XP machine,
(built-in firewall enabled by default) but slackware hasn't
any rules to block ping by default so it should be pinguable...

You tried without the modem connected to the hub didn't you ?

Also you double checked ifconfig in slackware and ipconfig in
windows ? No trouble from this side ? Outputs look correct ?

/sbin/route in slackware and route print in windows both show
the 192.168.0.0 network ?

Whenever I connect the cable modem to the Slack box, it's directly into eth0 (and not through a hub). I'm only using a hub to go directly between eth0 and the WinXP box.

Right now I have the 3c503 in the Slack box as eth0, connected to a hub, which then goes to my WinXP box. Let me give you some outputs.

On Slackware:

Code:

# ifconfig -a
eth0    Link encap:Ethernet  HWaddr 02:60:8C:D9:91:2D
        inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:430 errors:0 dropped:0 overruns:0 frame:0
        TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:1000
        RX bytes:35345 (34.5 Kb)  TX bytes:4094 (3.9 Kb)
        Interrupt:5 Base address:0x280 Memory:d8000-da000

(stuff about lo cut to save typing)

# ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
From 192.168.1.1 icmp_seq=2 Destination Host Unreachable
From 192.168.1.1 icmp_seq=3 Destination Host Unreachable
From 192.168.1.1 icmp_seq=4 Destination Host Unreachable
From 192.168.1.1 icmp_seq=5 Destination Host Unreachable
From 192.168.1.1 icmp_seq=6 Destination Host Unreachable

--- 192.168.1.3 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6025ms, pipe 3

# ifconfig -a
eth0    Link encap:Ethernet  HWaddr 02:60:8C:D9:91:2D
        inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:430 errors:0 dropped:0 overruns:0 frame:0
        TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:1000
        RX bytes:35345 (34.5 Kb)  TX bytes:4634 (4.5 Kb)
        Interrupt:5 Base address:0x280 Memory:d8000-da000

# route
Kernel IP routing table
Destination     Gateway        Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *              255.255.255.0   U     0      0        0 eth0
loopback        *              255.0.0.0       U     0      0        0 l0

And on WinXP:

Code:

>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : naru
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : wlfdle.phub.net.cable.rogers.com

Ethernet adapter Onboard Adapter:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
        Physical Address. . . . . . . . . : 00-0A-E6-C5-4B-92
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.3
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 24.226.10.193
                                            24.226.1.93
                                            24.226.10.194

>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x20004 ...00 0a e6 c5 4b 92 ...... SiS 900 PCI Fast Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.3       30
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.1.0    255.255.255.0      192.168.1.3     192.168.1.3       30
      192.168.1.3  255.255.255.255        127.0.0.1       127.0.0.1       30
    192.168.1.255  255.255.255.255      192.168.1.3     192.168.1.3       30
        224.0.0.0        240.0.0.0      192.168.1.3     192.168.1.3       30
  255.255.255.255  255.255.255.255      192.168.1.3     192.168.1.3       1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None

Turning the WinXP firewall on or off makes no difference to these outputs.

egag · 07-10-2005, 06:46 PM

do you have a crossover cable to connect them both nic to nic ?
if so, try that.
( really looks like some cabling- or hw-fault )

egag

Staedtler · 07-10-2005, 08:39 PM

Quote:

Originally posted by egag
do you have a crossover cable to connect them both nic to nic ?
if so, try that.
( really looks like some cabling- or hw-fault )

egag

Well hot damn, using a crossover cable between the two boxes results in successful pings (in both directions). Now I have to build on this somehow...

Staedtler · 07-11-2005, 08:53 PM

So after some more fiddling, I've come up with some conclusions.

First of all, my Ethernet hub seems to be faulty. No matter what cables I use with it, I just can't make a connection between the two boxes. If I use a crossover cable directly between the two boxes, everything communicates perfectly. egag really clued me into that one (I thought getting a link light was good enough, but apparently not).

Secondly, my DHCP issues *were* related to the lease not being renewed correctly. gbonhevi suggested that right after I started this thread, and I followed his advice by turning my modem off and on. As it turns out, that's not good enough. I had to actually cut power to the modem in order to reset it. After that, dhcpcd had no problems whatsoever.

Thanks to everyone for all the help, especially since I don't have to buy new hardware now. :-) (Well, except for a new hub...)