ethernet connection wizard says okay, but browsers won't go
Posted: Sun 19 Apr 2009, 19:50
howdy all,
on an old toshiba laptop, 4010cds, p2, 266mhz, 160mb ram, 60gb hd
full installs of the 2.17, 4.1.2, w98se [not connecting either]
d-link dfe-690txd wired cable adapter using the 8139too module
in both Puppy 2.17 and 4.1.2, using auto dhcp
cable goes to a wireless router with 4 cable sockets, [dlink di-524],
then to a modem [3com adsl modem ethernet]
two compus running xp and one old clamshell ibook g3 running os8.6
are connected and provide info about their ip addresses
i've looked in the forum, interesting, useful reading [ http://www.murga-linux.com/puppy/viewtopic.php?t=40525] and tried some stuff
without success, obviously
at one point i saw that the terminal showed an apipa address, 169.xxx,
which i learned a bit about in this forum yesterday
here's the end of dmesg output and ifconfig after right-clicking on the connect icon
and choosing autoconnect...no joy although the address, bcast, mask numbers look right
8139too Fast Ethernet driver 0.9.28
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:01:00.0 to 64
eth0: RealTek RTL8139 at 0xca852000, 00:1b:11:49:a4:0c, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x220-0x22f 0x278-0x27f 0x330-0x337 0x388-0x38f
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x220-0x22f 0x278-0x27f 0x330-0x337 0x388-0x38f
cs: IO port probe 0xa00-0xaff: clean.
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:11:49:A4:0C
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:880 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:283260 (276.6 KiB) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:624 (624.0 B) TX bytes:624 (624.0 B)
then i tried the network wizard off start menu which said a-ok but skipstone browser said no
and then config -a gave a different set of ip numbers, as follows:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1B:11:49:A4:0C
inet addr:169.254.37.175 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2066 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:663428 (647.8 KiB) TX bytes:5046 (4.9 KiB)
Interrupt:11 Base address:0x2000
irda0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1248 (1.2 KiB) TX bytes:1248 (1.2 KiB)
any help with this would be most welcome; it's been a long, winding road with this classic laptop and i'm not even sure what i did that caused puppy to recognise the adapter after not doing so. when i saw the apipa address info yesterday i tried some bios changes which caused kernel panics and non-recognition of pcmcia until i refound the appropriate bios settings. that same thread, in beginner help, closed with a set of manual commands:
rmmod 8139too
modprobe 8139too
ifconfig 192.168.1.1 netmask 255.255.255.0
route add default gw 192.168.1.1
echo "nameserver 192.168.1.1" >> /etc/resolv.conf
when i tried them with the good ip numbers, the third line failed:
#ifconfig: SIOCSIFNETMASK: no such device
best wishes. mm
on an old toshiba laptop, 4010cds, p2, 266mhz, 160mb ram, 60gb hd
full installs of the 2.17, 4.1.2, w98se [not connecting either]
d-link dfe-690txd wired cable adapter using the 8139too module
in both Puppy 2.17 and 4.1.2, using auto dhcp
cable goes to a wireless router with 4 cable sockets, [dlink di-524],
then to a modem [3com adsl modem ethernet]
two compus running xp and one old clamshell ibook g3 running os8.6
are connected and provide info about their ip addresses
i've looked in the forum, interesting, useful reading [ http://www.murga-linux.com/puppy/viewtopic.php?t=40525] and tried some stuff
without success, obviously
at one point i saw that the terminal showed an apipa address, 169.xxx,
which i learned a bit about in this forum yesterday
here's the end of dmesg output and ifconfig after right-clicking on the connect icon
and choosing autoconnect...no joy although the address, bcast, mask numbers look right
8139too Fast Ethernet driver 0.9.28
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:01:00.0 to 64
eth0: RealTek RTL8139 at 0xca852000, 00:1b:11:49:a4:0c, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x220-0x22f 0x278-0x27f 0x330-0x337 0x388-0x38f
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x220-0x22f 0x278-0x27f 0x330-0x337 0x388-0x38f
cs: IO port probe 0xa00-0xaff: clean.
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:11:49:A4:0C
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:880 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:283260 (276.6 KiB) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:624 (624.0 B) TX bytes:624 (624.0 B)
then i tried the network wizard off start menu which said a-ok but skipstone browser said no
and then config -a gave a different set of ip numbers, as follows:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1B:11:49:A4:0C
inet addr:169.254.37.175 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2066 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:663428 (647.8 KiB) TX bytes:5046 (4.9 KiB)
Interrupt:11 Base address:0x2000
irda0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1248 (1.2 KiB) TX bytes:1248 (1.2 KiB)
any help with this would be most welcome; it's been a long, winding road with this classic laptop and i'm not even sure what i did that caused puppy to recognise the adapter after not doing so. when i saw the apipa address info yesterday i tried some bios changes which caused kernel panics and non-recognition of pcmcia until i refound the appropriate bios settings. that same thread, in beginner help, closed with a set of manual commands:
rmmod 8139too
modprobe 8139too
ifconfig 192.168.1.1 netmask 255.255.255.0
route add default gw 192.168.1.1
echo "nameserver 192.168.1.1" >> /etc/resolv.conf
when i tried them with the good ip numbers, the third line failed:
#ifconfig: SIOCSIFNETMASK: no such device
best wishes. mm