Weird Ethenet dsl setup issue

svar · 08-06-2009, 02:04 AM

The story is: Due to an M/B failure, I had to replace the entire system(holding 3 linux distros). All of them had dsl working fine. Two of them had serious corruption(superblock fot found), but one of them (Slack 12) I was able to recover. DSL(PPPoE) however did not. I also installed Open Suse and again, no DSL. Anyway, after working with an Ubuntu in Live Cd mode, I was able to get Open Suse to work(even with a wrong /etc/resolv.conf)
Slack however still does not work, even though I copied the udev files(/etc/udev/rules.d/70-persistent-net.rules)
, corrected the resolv.conf file and (I think got /etc/rc.d/rc.inet1.conf
correct. The problem is that I cannot ping the gw.
---------------------------------------------------------------

Quote:

bash-3.1# diff 70-persistent-net.rules /mnt/root/etc/udev/rules.d/70-persistent-net.rules
bash-3.1#
cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# PCI device 0x10ec:0x8136 (r8169)
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# PCI device 0x10ec:0x8136 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:66:99:04:f8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

Here is netstat:

Quote:

bash-3.1# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.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
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

For openSuse:

me@dhcppc0:~> su
Password:
dhcppc0:/home/me # ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:66:99:04:F8
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::219:66ff:fe99:4f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3547 errors:0 dropped:125141407 overruns:0 frame:0
TX packets:2521 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5128475 (4.8 Mb) TX bytes:189575 (185.1 Kb)
Interrupt:221 Base address:0x8000

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:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3496 (3.4 Kb) TX bytes:3496 (3.4 Kb)

and for Slack:

ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:66:99:04:F8
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::219:66ff:fe99:4f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:4294967257 overruns:0 frame:0
TX packets:0 errors:0 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0x8000

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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

--------------------
for completeness, here is rc.inet1.conf from Slack(Suse uses xinetd and I forgot where the relevant files are, but this file looks ok):

Quote:

# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]="192.168.1.6"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY="192.168.1.1"

# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"

## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
#IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
#USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=BARRIER05
#WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
##WLAN_IWPRIV[4]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=7B1ABEEB5D197741923ED26727569C365E31212096A0EAFAD563B268BAD01CAF TxRate=0"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=thekey TxRate=0"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (space-separated, see the
# example).

Basically routing should be
ifconfig eth0 192.168.1.6 netmask 255.255.255.0
ifconfig eth0 up
route add default gw 192.168.1.1

or am I missing something?(something changed in 2.6? Do I need sysconfig?)
I should add that changes I make in Slack sometimes result in messing up
OpenSuse too(which is in a different partition). I need to use the Live Cd to get Suse back working with no other changes(just use the Live Cd),
reboot and use Open Suse and it works. I am not sure what I am doing wrong.

P.S. Sorry this has also been posted in the Slack forum-but it looks like there is a network configuration issue I do not understand.

TigerOC · 08-07-2009, 02:26 PM

Everything seems correct but the number of dropped packets doesn't make sense;

Quote:

RX packets:0 errors:0 dropped:4294967257 overruns:0 frame:0
TX packets:0 errors:0 dropped:6 overruns:0 carrier:0

Do you have a firewall of some type that may be preventing all connections?

svar · 08-10-2009, 01:55 AM

No, no fw. But it works now, though I do not understand why. After I booted from the latest Ubuntu Live CD(which set up everything fine), I got both Slack and Suse working fine. I have no idea why this is so. A Live CD should not mess with the configuration of existing partitions....

svar · 08-11-2009, 07:05 AM

Without changing a thing, Slack again does not work, while Suse does... I really don;t undestand what's going on

TigerOC · 08-11-2009, 09:34 AM

Quote:

Originally Posted by svar

Without changing a thing, Slack again does not work, while Suse does... I really don;t undestand what's going on

Flakey ethernet card?

svar · 08-12-2009, 12:16 AM

That CONSISTENTLY works with Ubuntu Live CD and not the others?

TigerOC · 08-12-2009, 08:35 AM

The 2 distros may be using different driver versions for the same device. Funny things happen.

I am having serious problems with a kernel and I have 2 identical boxes running the same kernel. The one is fine, but on the other box the kernel keeps crashing - the very first time I have experienced a kernel crash with Linux is 9 years.

svar · 08-13-2009, 12:15 AM

That would be fine except I also get them to work fine sometimes. Yesterday for example I got into Suse, dsl worked fine, then rebooted int Slack, also dsl worked fine, rebooted again(actually I tried a previously working and untouched app that crashed) into Slack and dsl was dead....
So a driver that sometimes works and sometimes not is weird to me.

TigerOC · 08-13-2009, 02:36 AM

If it's flakey hardware then the simple thing is to swap it out. ethernet cards are so cheap I carry numerous spares for just occassions.

svar · 08-13-2009, 04:50 AM

question is then: what else could it be and why does it ALWAYS work with the Live CD???