XDSL und das Modem. Eine Geschichte in Rot.

Ask here for help - and if the problem is solved, it goes to the ==> Knowledge Base!
Post Reply
Guest

XDSL und das Modem. Eine Geschichte in Rot.

Post by Guest »

Liebe, liebe Leute, bin total vervzweifelt, weil ich regelmäßig (15min bis 4h) mein Modem resetten muss.

Und ich das Problem einfach nicht lösen kann. Bitte um tatkräftige Hilfe (falls möglich). Ein Platz im Himmel sei Euch dafür gesichert. Amen.

Setup:
Via Epia 800 Linuxserver mit Fedora Core 4
eth0: DHCP, hängt an Zyxel-Modem, das an einer Leitung zu Inode hängt (Inode Privat Medium Flat (2048:512)), IP-Bereich 172.x.x.x
ppp0 IP Bereich 85.x.x.x
(eth1 WLAN)
Protokoll pptp
Einwahl: inode-dsl-script von Inode
Hatten vorher Aon als Anbieter, nie Probleme, einfach gewechselt, exakt gleiches Setup (User, Kennwort, DNS der Einwahl geändert)

Problem:
Nach einer Zeit x verliert der Linux-Rechner die Internet-Verbindung.
ifconfig zeigt eth0 nicht mehr an, auch ifconfig eth0 down, dann ifconfig eth0 up löst das Problem nicht. Eth0 bekommt keine neue IP vom Modem. Nach Modem-Neustart geht Verbindung wieder.
Ausfälle sind komplett sporadisch, von 15 min bis 4 h (letzteres v.a. am Vormittag)
Nach Neustart des Modems kein Eingriff ins System notwendig, System wählt sich mit Inode-Skript wieder von alleine ein.

Durchgeführte Ansätze:
/etc/sysconfig/network-scripts/ifcfg-eth0 ausgemistet, um die Reste der statischen IP wirklich loszuwerden.

Code: Select all

DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
dhcpd zeitweise ausgeschaltet, um Konflikt auszuschließen.

Auszüge aus den logs:
Jun 4 00:45:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39295
Jun 4 00:45:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39295
Jun 4 00:45:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39300
Jun 4 00:45:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39300
Jun 4 00:45:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39302
Jun 4 00:45:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39302
Jun 4 00:45:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39303
Jun 4 00:45:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39303
Jun 4 00:45:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39304
Jun 4 00:45:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39304
Jun 4 00:45:26 www dhcpcd[29478]: timed out waiting for a valid DHCP server response
Jun 4 00:48:05 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 00:48:05 www kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 4 00:48:25 www dhcpcd[29586]: timed out waiting for a valid DHCP server response
Jun 4 00:50:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39313
Jun 4 00:50:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39313
Jun 4 00:50:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39314
Jun 4 00:50:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39314
Jun 4 00:51:05 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 00:51:05 www kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 4 00:51:25 www dhcpcd[29710]: timed out waiting for a valid DHCP server response
Jun 4 00:52:27 www nmbd[2462]: [2006/06/04 00:52:27, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353)
Jun 4 00:52:27 www nmbd[2462]: find_domain_master_name_query_fail:
Jun 4 00:52:27 www nmbd[2462]: Unable to find the Domain Master Browser name HEIMNETZ<1b> for the workgroup HEIMNETZ.
Jun 4 00:52:27 www nmbd[2462]: Unable to sync browse lists in this workgroup.
Jun 4 00:54:05 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 00:54:05 www kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 4 00:54:25 www dhcpcd[29799]: timed out waiting for a valid DHCP server response
Jun 4 00:55:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39321
Jun 4 00:55:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39321
Jun 4 00:57:05 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 00:57:05 www kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 4 00:57:25 www dhcpcd[29917]: timed out waiting for a valid DHCP server response
Jun 4 00:59:09 www sshd(pam_unix)[29932]: session opened for user root by root(uid=0)
Jun 4 01:00:10 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 01:00:10 www kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 4 01:00:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39322

Jun 4 01:00:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39331
Jun 4 01:00:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39332
Jun 4 01:00:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39332
Jun 4 01:00:30 www dhcpcd[30065]: timed out waiting for a valid DHCP server response
Jun 4 01:03:07 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 01:03:07 www kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 4 01:03:16 www kernel: eth0: link down
Jun 4 01:03:18 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 01:03:20 www kernel: eth0: link down
Jun 4 01:03:22 www kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Jun 4 01:03:27 www dhcpcd[30194]: timed out waiting for a valid DHCP server response
Jun 4 01:05:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39332
Jun 4 01:05:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39337
Jun 4 01:05:15 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39337
Jun 4 01:05:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39337
Jun 4 01:05:15 www snmpd[2051]: Connection from UDP: [127.0.0.1]:39338
Jun 4 01:05:16 www snmpd[2051]: Received SNMP packet(s) from UDP: [127.0.0.1]:39338
Verbindung dürfte ca. um 01:03 ausgefallen sein. Neustart des Modems um 01:05.


Für jede Hilfe dankbar,
Bugo
Bugo
Active Member
Posts: 13
Joined: Sun Jun 04, 2006 12:20 am

Post by Bugo »

sorry, aus versehen als guest gepostet.
Bugo
Bugo
Active Member
Posts: 13
Joined: Sun Jun 04, 2006 12:20 am

Post by Bugo »

nach kabelwechsel (ohne neustart des modems) gab es wieder internet (nachdem es ausgefallen war)

Werde einmal beobachten, ob's hält.
gilthanaz
Site Admin
Posts: 443
Joined: Fri Aug 29, 2003 9:29 pm
Contact:

Hm

Post by gilthanaz »

1. Welcome to the boards

2. English is the board language

3. I have a weird hangover

4. Welcome to the boards, again.


Now on topic:
As i said yesterday on the phone, first of all, check the following things.

* Cable from Modem to Computer (you already did that)
* NIC eth0 in the computer
* dhcpcd (DHCP client deamon)

If all of that doenst work, the modem is probably broken. We have a modem here with about the same behaviour ... every now and then (1 - 6 hours) it disconnects and denies to reconnect, unless you just unplug/replug it.

Let's hope its just the cable or the NIC (Network Interface Card), or the modem, as the Telecom will replace it for free if its really broken. But if you call them to replace it and its not broken, they want you to pay them... which is a pain in the ass.

- Gil
Guest

Post by Guest »

and as I already told you, I hate pains in my ass (They hurt... oh, the pain!)

So far, the connection holds with the new cable (3 hours and counting)

Sorry for the wrong language. My language of choice at 1 a.m. usually is German. I'm trying to umgewöhn.
Bugo
Active Member
Posts: 13
Joined: Sun Jun 04, 2006 12:20 am

Post by Bugo »

Solution.

The old cable used with the Aon modem is working just fine. No interrupts since then. Strange, but fine with me.

Thanks for your help!
Ezeran
Absolute Beginner
Posts: 5
Joined: Mon Apr 03, 2006 4:46 pm

Post by Ezeran »

I had same problems too with my Router and i had (want) to change my router. Ahh, the hell with this damn old D-Link Crap. :D
Now i have a Linksys WRT-54GL which has an open source firmware.
That means; if i have problems with my wlan-range i just can blow it up to 8x than normal range (ca.) I've not even tried the firmware-project's firmware but i've read a lots of reviews that say that it's fucking cool. 8)
Post Reply