Internet connection dies/won't start - Suse

This is a discussion on Internet connection dies/won't start - Suse ; My Suse 10.3 box was doing fine until recently when it began losing the net connection frequently and then would not restart the net connection. Some facts about the situation. - Known good hardware, internet connection is OK under Win ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Internet connection dies/won't start

  1. Internet connection dies/won't start



    My Suse 10.3 box was doing fine until recently when it began losing the net connection frequently and then would not
    restart the net connection.

    Some facts about the situation.

    - Known good hardware, internet connection is OK under Win
    - I went through a number of attempts to get the connection to work using Yast to switch the configuration between ifup and
    NetworkManager, same results (connection not working or flaky) for both methods. One interesting thing is that I cannot use
    iwconfig to fix this either, changes (like ESSID or key) sometimes seem not to stick.
    - The firewall is currently shut off to prevent problems.
    - When I start XP after a Linux problem it reports that there is a problem with the IP address lease that it has fixed.

    So far I'm puzzled, Yast sets up the connection but then it doesn't work (it used to)

    Are there asome lower-level sanity checks that I can use? Which files control this operation? I am puzzled, TIA for any help
    or troubleshooting tips.

    Jim

    ================================================== ================


    The logs. Here's something that might apply from /var/log/localmessages. I don't know why dhcpd is being killed but it's
    probably a symptom of something serious.
    Feb 2 19:32:33 new64 dhcpcd[4141]: terminating on signal 15
    Feb 2 22:08:56 new64 dhcpcd[4103]: terminating on signal 15
    Feb 2 22:42:58 new64 dhcpcd[5197]: terminating on signal 15
    Feb 3 09:24:40 new64 dhcpcd[3910]: terminating on signal 15
    Feb 3 12:28:19 new64 dhcpcd[5764]: terminating on signal 15
    Feb 3 12:43:56 NEW64 dhcpcd[2807]: terminating on signal 15

    Also here's /var/log/messages for a typical startup, note that dhcpd can't seem to get a connection.
    ================================================== ================================================== ==
    Feb 4 21:14:36 NEW64 syslog-ng[2752]: syslog-ng version 1.6.12 starting
    Feb 4 21:14:41 NEW64 kernel: klogd 1.4.1, log source = /proc/kmsg started.
    Feb 4 21:14:41 NEW64 kernel: IA-32 Microcode Update Driver: v1.14a
    Feb 4 21:14:41 NEW64 kernel: powernow: This module only works with AMD K7 CPUs
    Feb 4 21:14:41 NEW64 kernel: NET: Registered protocol family 10
    Feb 4 21:14:41 NEW64 kernel: lo: Disabled Privacy Extensions
    Feb 4 21:14:41 NEW64 kernel: Mobile IPv6
    Feb 4 21:14:41 NEW64 ifup: lo
    Feb 4 21:14:41 NEW64 ifup: lo
    Feb 4 21:14:41 NEW64 ifup: IP address: 127.0.0.1/8
    Feb 4 21:14:41 NEW64 ifup:
    Feb 4 21:14:42 NEW64 ifup: wlan0 device: RaLink RT2561/RT61 802.11g PCI
    Feb 4 21:14:43 NEW64 ifup-dhcp: wlan0 (DHCP)
    Feb 4 21:14:43 NEW64 ifup-dhcp: .
    Feb 4 21:14:43 NEW64 kernel: NET: Registered protocol family 17
    Feb 4 21:14:44 NEW64 ifup-dhcp: .
    Feb 4 21:14:48 NEW64 syslog-ng[2752]: last message repeated 3 times
    Feb 4 21:14:48 NEW64 hald: mounted /dev/sdd1 on behalf of uid 1000

    ********* Here's a likely symptom *********

    Feb 4 21:14:48 NEW64 ifup-dhcp: no IP address yet... backgrounding.
    Feb 4 21:14:53 NEW64 kernel: wlan0: no IPv6 routers present
    Feb 4 21:15:04 NEW64 auditd[4478]: Started dispatcher: /sbin/audispd pid: 4480
    Feb 4 21:15:04 NEW64 kernel: audit(1202195704.032:3): audit_pid=4478 old=0 by auid=4294967295
    Feb 4 21:15:04 NEW64 auditd[4478]: Init complete, auditd 1.5.5 listening for events (startup state disable)
    Feb 4 21:15:04 NEW64 audispd[4480]: listening on /var/run/audit_events
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Found user 'avahi' (UID 103) and group 'avahi' (GID 105).
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Successfully dropped root privileges.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: avahi-daemon 0.6.20 starting up.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Loading service file /etc/avahi/services/sftp-ssh.service.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Loading service file /etc/avahi/services/ssh.service.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Network interface enumeration completed.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Registering new address record for fe80::21a:70ff:feac:63ec on wlan0.*.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Server startup complete. Host name is NEW64.local. Local service cookie is 3949303192.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Service "NEW64" (/etc/avahi/services/ssh.service) successfully established.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Service "SFTP File Transfer on NEW64" (/etc/avahi/services/sftp-ssh.service)
    successfully established.
    Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Registering HINFO record with values 'I686'/'LINUX'.
    Feb 4 21:15:04 NEW64 avahi-dnsconfd[4505]: Successfully connected to Avahi daemon.
    Feb 4 21:15:10 NEW64 /usr/sbin/cron[4632]: (CRON) STARTUP (V5.0)
    Feb 4 21:15:11 NEW64 smartd[4657]: smartd version 5.37 [i686-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen
    Feb 4 21:15:11 NEW64 smartd[4657]: Home page is http://smartmontools.sourceforge.net/
    Feb 4 21:15:11 NEW64 smartd[4657]: Opened configuration file /etc/smartd.conf
    Feb 4 21:15:11 NEW64 smartd[4657]: Drive: DEVICESCAN, implied '-a' Directive on line 27 of file /etc/smartd.conf
    Feb 4 21:15:11 NEW64 smartd[4657]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
    Feb 4 21:15:11 NEW64 smartd[4657]: Problem creating device name scan list
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device /dev/sda: ATA disk detected behind SAT layer
    Feb 4 21:15:11 NEW64 smartd[4657]: Try adding '-d sat' to the device line in the smartd.conf file.
    Feb 4 21:15:11 NEW64 smartd[4657]: For example: '/dev/sda -a -d sat'
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdb, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device /dev/sdb: ATA disk detected behind SAT layer
    Feb 4 21:15:11 NEW64 smartd[4657]: Try adding '-d sat' to the device line in the smartd.conf file.
    Feb 4 21:15:11 NEW64 smartd[4657]: For example: '/dev/sdb -a -d sat'
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdc, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdc, NO MEDIUM present; skip device
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdd, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdd, Bad IEC (SMART) mode page, err=5, skip device
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sde, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sde, NO MEDIUM present; skip device
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdf, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdf, NO MEDIUM present; skip device
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdg, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdg, NO MEDIUM present; skip device
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, found in smartd database.
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdb, opened
    Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdb, found in smartd database.
    Feb 4 21:15:11 NEW64 kernel: bootsplash: status on console 0 changed to on
    Feb 4 21:15:12 NEW64 sshd[4695]: Server listening on :: port 22.
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list.
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdc, opened
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdc, not ATA, no IDENTIFY DEVICE Structure
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdd, opened
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdd, not ATA, no IDENTIFY DEVICE Structure
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sde, opened
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sde, not ATA, no IDENTIFY DEVICE Structure
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdf, opened
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdf, not ATA, no IDENTIFY DEVICE Structure
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdg, opened
    Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdg, not ATA, no IDENTIFY DEVICE Structure
    Feb 4 21:15:12 NEW64 smartd[4657]: Monitoring 2 ATA and 0 SCSI devices
    Feb 4 21:15:12 NEW64 smartd[4697]: smartd has fork()ed into background mode. New PID=4697.
    Feb 4 21:18:18 NEW64 sudo: jim : TTY=pts/2 ; PWD=/home/jim ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
    Feb 4 21:18:18 NEW64 sudo: jim : TTY=pts/2 ; PWD=/home/jim ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
    Feb 4 21:32:11 NEW64 su: (to root) jim on /dev/pts/3


  2. Re: Internet connection dies/won't start

    Have you tried disabling IPV6 ?

    jim wrote:

    >
    >
    > My Suse 10.3 box was doing fine until recently when it began
    > losing the net connection frequently and then would not
    > restart the net connection.
    >
    > Some facts about the situation.
    >
    > - Known good hardware, internet connection is OK under Win
    > - I went through a number of attempts to get the connection to
    > work using Yast to switch the configuration between ifup and
    > NetworkManager, same results (connection not working or flaky) for
    > both methods. One interesting thing is that I cannot use iwconfig to
    > fix this either, changes (like ESSID or key) sometimes seem not to
    > stick.
    > - The firewall is currently shut off to prevent problems.
    > - When I start XP after a Linux problem it reports that there is
    > a problem with the IP address lease that it has fixed.
    >
    > So far I'm puzzled, Yast sets up the connection but then it
    > doesn't work (it used to)
    >
    > Are there asome lower-level sanity checks that I can use? Which files
    > control this operation? I am puzzled, TIA for any help or
    > troubleshooting tips.
    >
    > Jim
    >
    > ================================================== ================
    >
    >
    > The logs. Here's something that might apply from
    > /var/log/localmessages. I don't know why dhcpd is being killed
    > but it's
    > probably a symptom of something serious.
    > Feb 2 19:32:33 new64 dhcpcd[4141]: terminating on signal 15
    > Feb 2 22:08:56 new64 dhcpcd[4103]: terminating on signal 15
    > Feb 2 22:42:58 new64 dhcpcd[5197]: terminating on signal 15
    > Feb 3 09:24:40 new64 dhcpcd[3910]: terminating on signal 15
    > Feb 3 12:28:19 new64 dhcpcd[5764]: terminating on signal 15
    > Feb 3 12:43:56 NEW64 dhcpcd[2807]: terminating on signal 15
    >
    > Also here's /var/log/messages for a typical startup, note that dhcpd
    > can't seem to get a connection.
    >

    ================================================== ================================================== ==
    > Feb 4 21:14:36 NEW64 syslog-ng[2752]: syslog-ng version 1.6.12
    > starting
    > Feb 4 21:14:41 NEW64 kernel: klogd 1.4.1, log source = /proc/kmsg
    > started.
    > Feb 4 21:14:41 NEW64 kernel: IA-32 Microcode Update Driver: v1.14a
    >
    > Feb 4 21:14:41 NEW64 kernel: powernow: This module only works with
    > AMD K7 CPUs
    > Feb 4 21:14:41 NEW64 kernel: NET: Registered protocol family 10
    > Feb 4 21:14:41 NEW64 kernel: lo: Disabled Privacy Extensions
    > Feb 4 21:14:41 NEW64 kernel: Mobile IPv6
    > Feb 4 21:14:41 NEW64 ifup: lo
    > Feb 4 21:14:41 NEW64 ifup: lo
    > Feb 4 21:14:41 NEW64 ifup: IP address: 127.0.0.1/8
    > Feb 4 21:14:41 NEW64 ifup:
    > Feb 4 21:14:42 NEW64 ifup: wlan0 device: RaLink RT2561/RT61
    > 802.11g PCI
    > Feb 4 21:14:43 NEW64 ifup-dhcp: wlan0 (DHCP)
    > Feb 4 21:14:43 NEW64 ifup-dhcp: .
    > Feb 4 21:14:43 NEW64 kernel: NET: Registered protocol family 17
    > Feb 4 21:14:44 NEW64 ifup-dhcp: .
    > Feb 4 21:14:48 NEW64 syslog-ng[2752]: last message repeated 3 times
    > Feb 4 21:14:48 NEW64 hald: mounted /dev/sdd1 on behalf of uid 1000
    >
    > ********* Here's a likely symptom *********
    >
    > Feb 4 21:14:48 NEW64 ifup-dhcp: no IP address yet... backgrounding.
    > Feb 4 21:14:53 NEW64 kernel: wlan0: no IPv6 routers present
    > Feb 4 21:15:04 NEW64 auditd[4478]: Started dispatcher: /sbin/audispd
    > pid: 4480
    > Feb 4 21:15:04 NEW64 kernel: audit(1202195704.032:3): audit_pid=4478
    > old=0 by auid=4294967295
    > Feb 4 21:15:04 NEW64 auditd[4478]: Init complete, auditd 1.5.5
    > listening for events (startup state disable)
    > Feb 4 21:15:04 NEW64 audispd[4480]: listening on
    > /var/run/audit_events
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Found user 'avahi' (UID 103)
    > and group 'avahi' (GID 105).
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Successfully dropped root
    > privileges.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: avahi-daemon 0.6.20 starting
    > up.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Loading service file
    > /etc/avahi/services/sftp-ssh.service.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Loading service file
    > /etc/avahi/services/ssh.service.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Network interface
    > enumeration completed.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Registering new address
    > record for fe80::21a:70ff:feac:63ec on wlan0.*.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Server startup complete.
    > Host name is NEW64.local. Local service cookie is 3949303192.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Service "NEW64"
    > (/etc/avahi/services/ssh.service) successfully established.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Service "SFTP File Transfer
    > on NEW64" (/etc/avahi/services/sftp-ssh.service) successfully
    > established.
    > Feb 4 21:15:04 NEW64 avahi-daemon[4493]: Registering HINFO record
    > with values 'I686'/'LINUX'.
    > Feb 4 21:15:04 NEW64 avahi-dnsconfd[4505]: Successfully connected to
    > Avahi daemon.
    > Feb 4 21:15:10 NEW64 /usr/sbin/cron[4632]: (CRON) STARTUP (V5.0)
    > Feb 4 21:15:11 NEW64 smartd[4657]: smartd version 5.37
    > [i686-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen
    > Feb 4 21:15:11 NEW64 smartd[4657]: Home page is
    > http://smartmontools.sourceforge.net/
    > Feb 4 21:15:11 NEW64 smartd[4657]: Opened configuration file
    > /etc/smartd.conf
    > Feb 4 21:15:11 NEW64 smartd[4657]: Drive: DEVICESCAN, implied '-a'
    > Directive on line 27 of file /etc/smartd.conf
    > Feb 4 21:15:11 NEW64 smartd[4657]: Configuration file
    > /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
    > Feb 4 21:15:11 NEW64 smartd[4657]: Problem creating device name scan
    > list
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device /dev/sda: ATA disk detected
    > behind SAT layer
    > Feb 4 21:15:11 NEW64 smartd[4657]: Try adding '-d sat' to the
    > device line in the smartd.conf file.
    > Feb 4 21:15:11 NEW64 smartd[4657]: For example: '/dev/sda -a -d
    > sat'
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdb, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device /dev/sdb: ATA disk detected
    > behind SAT layer
    > Feb 4 21:15:11 NEW64 smartd[4657]: Try adding '-d sat' to the
    > device line in the smartd.conf file.
    > Feb 4 21:15:11 NEW64 smartd[4657]: For example: '/dev/sdb -a -d
    > sat'
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdc, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdc, NO MEDIUM
    > present; skip device
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdd, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdd, Bad IEC (SMART)
    > mode page, err=5, skip device
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sde, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sde, NO MEDIUM
    > present; skip device
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdf, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdf, NO MEDIUM
    > present; skip device
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdg, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdg, NO MEDIUM
    > present; skip device
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, found in smartd
    > database.
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sda, is SMART
    > capable. Adding to "monitor" list.
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdb, opened
    > Feb 4 21:15:11 NEW64 smartd[4657]: Device: /dev/sdb, found in smartd
    > database.
    > Feb 4 21:15:11 NEW64 kernel: bootsplash: status on console 0 changed
    > to on
    > Feb 4 21:15:12 NEW64 sshd[4695]: Server listening on :: port 22.
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdb, is SMART
    > capable. Adding to "monitor" list.
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdc, opened
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdc, not ATA, no
    > IDENTIFY DEVICE Structure
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdd, opened
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdd, not ATA, no
    > IDENTIFY DEVICE Structure
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sde, opened
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sde, not ATA, no
    > IDENTIFY DEVICE Structure
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdf, opened
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdf, not ATA, no
    > IDENTIFY DEVICE Structure
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdg, opened
    > Feb 4 21:15:12 NEW64 smartd[4657]: Device: /dev/sdg, not ATA, no
    > IDENTIFY DEVICE Structure
    > Feb 4 21:15:12 NEW64 smartd[4657]: Monitoring 2 ATA and 0 SCSI
    > devices
    > Feb 4 21:15:12 NEW64 smartd[4697]: smartd has fork()ed into
    > background mode. New PID=4697.
    > Feb 4 21:18:18 NEW64 sudo: jim : TTY=pts/2 ; PWD=/home/jim ;
    > USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
    > Feb 4 21:18:18 NEW64 sudo: jim : TTY=pts/2 ; PWD=/home/jim ;
    > USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
    > Feb 4 21:32:11 NEW64 su: (to root) jim on /dev/pts/3


    --
    Regards:
    Baron.

  3. Re: Internet connection dies/won't start

    Baron wrote:
    > Have you tried disabling IPV6 ?


    Thanks for the idea, I didn't know this could be a problem. Didn't work, though

    Jim

  4. Re: Internet connection dies/won't start

    On Tue, 05 Feb 2008 12:53:21 +0000, Baron wrote:

    > Have you tried disabling IPV6 ?


    It's kind of ironic to ask that on the exact same day that ICANN finally
    begins taking ipv6 seriously :-)

  5. Re: Internet connection dies/won't start

    Mark South wrote:

    > On Tue, 05 Feb 2008 12:53:21 +0000, Baron wrote:
    >
    >> Have you tried disabling IPV6 ?

    >
    > It's kind of ironic to ask that on the exact same day that ICANN
    > finally begins taking ipv6 seriously :-)


    I've had one or two instances of funny behaviour that turning IPV6
    support off has cured.
    --
    Regards:
    Baron.

+ Reply to Thread