ADSL connection unstable

Hello!

I have a DSL connection configured trough Yast. It works well, but every couple of days it gets lost and this is a problem since I use this computer as NAT/Router…

And I have to say I am a little bit confused about ADSL connections in OpenSuse (I come from Fedora where the network manager is nothing like Yast) maybe I did something wrong…

Here is my ifconfig:

dsl0      Link encap:Point-to-Point Protocol  
          inet addr:X.X.X.X  P-t-P:10.249.0.4  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1462  Metric:1
          RX packets:15947 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13649 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:14747326 (14.0 Mb)  TX bytes:1838092 (1.7 Mb)

eth0      Link encap:Ethernet  HWaddr 00:12:3F:A7:4C:AE  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: 2001:470:1d:611:1c12:1447:addb:ec72/64 Scope:Global
          inet6 addr: 2001:470:1d:611:8835:1985:e960:dced/64 Scope:Global
          inet6 addr: 2001:470:1d:611:212:3fff:fea7:4cae/64 Scope:Global
          inet6 addr: fe80::212:3fff:fea7:4cae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:433589592 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32939350 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:647393678069 (617402.7 Mb)  TX bytes:7519216634 (7170.8 Mb)
          Interrupt:16 

eth1      Link encap:Ethernet  HWaddr 00:08:A1:66:6E:D7  
          inet6 addr: fe80::208:a1ff:fe66:6ed7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2917993 errors:0 dropped:239 overruns:0 frame:0
          TX packets:2517836 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3737206624 (3564.0 Mb)  TX bytes:260635360 (248.5 Mb)
          Interrupt:16 Base address:0x8f00 

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:228699 errors:0 dropped:0 overruns:0 frame:0
          TX packets:228699 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1710798790 (1631.5 Mb)  TX bytes:1710798790 (1631.5 Mb)

This works fine (As I am writing right now) but sometimes I come back from work and dsl0 has disappeared…

And what is the difference between “DSL” and “Modem” categories in Yast? Both seem to do the trick…

Any idea what causes dsl0 to disappear? Kind of an inactivity timeout or…? Is it possible to active a kind of “keep-alive” signal in that case?

Thank you!

This may not be the complete solution, but it wonders me. You make a casual remark, which makes me think that you use Networkmanager. Isn’t that a bit strange for a system that (to me) seem to be switched on “allways” (for it’s function as router in your LAN) and thus should not depend on a user being loged in in the GUI and managing through NetworkManager? The more because I assume that the system is not taken awy on a walk to airports/hotel and the like? I aaume that a normal configuration using “classical ifup” is much more in place here. And maybe more stable.

Well, I don’t use NetworkManager, the “use traditional ifup” is checked in Yast’s network management window (Hope I am clear… :sarcastic:)

The network went down this morning also, so it is really recurring problem, but I think I found a solution here (seems to be the same symptoms as me: https://forums.opensuse.org/english/get-technical-help-here/network-internet/413403-dsl0-disconnect.html )

I will try this:

Change the IDLETIME parameter value in /etc/sysconfig/network/providers/provider? file.

Or, the "Idle Seconds" value in /etc/wvdial.conf file.

and I will post the results here.

Thank you!

OK, with the last solution the connection seems much more stable, but still dsl0 has disappeared yesterday (has been on for couple of weeks). It disappeared again not even an hour after, and now it seems to be OK…

This problems seems really random, any idea?

My solution for getting it back on is just to open YasT, do a minor change in the network configuration (kind of changing the dns) and save.

Also, is there a command-line that does like Fedora?:

#:service networking restart

I could manage to program a little script that constantly checks for DSL0 and restarts the network when it is not there…

[QUOTEAlso, is there a command-line that does like Fedora?:

#:service networking restart

[/QUOTE]

This is the systemd method:

sudo systemctl restart NetworkManager.service

Just a thought: I’ve never had to configure a DSL connection, but perhaps /etc/ppp/options comes into play as well. In particular, there is an ‘idle’ parameter, which may be relevant here. From ‘man pppd’:

idle n Specifies that pppd should disconnect if the link is idle for n seconds. The link is idle when no data packets (i.e. IP packets) are being sent or
received. Note: it is not advisable to use this option with the persist option without the demand option. If the active-filter option is given,
data packets which are rejected by the specified activity filter also count as the link being idle.

m6OpenSuse wrote:
> I have a DSL connection configured trough Yast. It works well, but
> every couple of days it gets lost and this is a problem since I use this
> computer as NAT/Router…

That sounds a fairly unusual configuration; it’s normal to use an
external modem/router with ADSL, AFAIK. I notice you haven’t provided
any detail of your hardware or where you are (i.e. the ADSL service
provider) nor any indication whether you have looked in logs for an
indication of what happens when the link drops. I would expect whichever
driver you are using for whatever adapter you have to log errors, and
possibly more information if configured to do so. I’m also a little
surprised that the driver doesn’t automatically reconnect after a
dropped connection. Again, perhaps that is configurable.

This is the systemd method:

sudo systemctl restart NetworkManager.service

Thank you I will try that next time :wink:

Just a thought: I’ve never had to configure a DSL connection, but perhaps /etc/ppp/options comes into play as well. In particular, there is an ‘idle’ parameter, which may be relevant here. From ‘man pppd’:


idle n Specifies that pppd should disconnect if the link is idle for n seconds. The link is idle when no data packets (i.e. IP packets) are being sent or
received. Note: it is not advisable to use this option with the persist option without the demand option. If the active-filter option is given,
data packets which are rejected by the specified activity filter also count as the link being idle.

I will also try that and feedback. But I doubt that it is an “idle” problem, since my roommate and I were not there for a whole week due to christmas and the connection was still active when we got back…

That sounds a fairly unusual configuration; it’s normal to use an external modem/router with ADSL, AFAIK.

Unusual configuration? I think that is pretty much the basic configuration for everybody that has a DSL connection and wants to share it with the LAN without a D-Link/Linksys router…

I notice you haven’t provided any detail of your hardware or where you are (i.e. the ADSL service provider)

The computer i a small Dell Optiplex Celeron 2.8, 512Mb RAM, with the onboard NIC and a Realtek PCI NIC. My provider is Radioactif, a small provider in Quebec City (Is this relevant?)

nor any indication whether you have looked in logs for an
indication of what happens when the link drops. I would expect whichever
driver you are using for whatever adapter you have to log errors, and
possibly more information if configured to do so. I’m also a little
surprised that the driver doesn’t automatically reconnect after a
dropped connection. Again, perhaps that is configurable.

Which logs should I check on the system? I will check the drivers name when home and feedback in…

Thank you all!

m6OpenSuse wrote:
> Unusual configuration? I think that is pretty much the basic
> configuration for everybody that has a DSL connection and wants to share
> it with the LAN without a D-Link/Linksys router…

Well, IME every ISP provides a free ADSL modem/router except some weird
ones that only used tp provide a modem. But in any case I’ve never come
across a case where you connect directly to an ADSL line.

>> I notice you haven’t provided any detail of your hardware or where you
>> are (i.e. the ADSL service provider)
>
> The computer i a small Dell Optiplex Celeron 2.8, 512Mb RAM, with the
> onboard NIC and a Realtek PCI NIC.

Well I think the ADSL modem card might be quite relevant, as well!

> My provider is Radioactif, a small
> provider in Quebec City (Is this relevant?)

The provider might be relevant since somebody else may have experience
and/or know some details of the service that might cause the symptoms.
(DSLAMs that need resetting, or whatever)

>> nor any indication whether you have looked in logs for an
>> indication of what happens when the link drops. I would expect
>> whichever
>> driver you are using for whatever adapter you have to log errors, and
>> possibly more information if configured to do so. I’m also a little
>> surprised that the driver doesn’t automatically reconnect after a
>> dropped connection. Again, perhaps that is configurable.
>
> Which logs should I check on the system? I will check the drivers name
> when home and feedback in…

I don’t know which logs; it’s been many years since I configured a PPP
connection and I’ve never done it on a Linux system. Perhaps somebody
else can tell you if you can’t figure it out. Certainly dmesg and
/var/log/messages but there may well be more.

Well, IME every ISP provides a free ADSL modem/router except some weird
ones that only used tp provide a modem. But in any case I’ve never come
across a case where you connect directly to an ADSL line.

I think I got misunderstood here: I have a modem plugged in eth1. I only configured it via Yast to connect to my ISP with username/password

Sorry for the confusion :frowning:

Well if that’s the case, the ADSL modem device manages the connection to the internet, provides routing, gateway, and DHCP IP addresses etc. Configuring via YaST >> Network Devices >> DSL is not applicable. All that is needed is to configure your ethernet port suitably.

Any modem configuration that may be required can usually be done via a web interface.

deano ferrari wrote:
> m6OpenSuse;2519197 Wrote:
>> I think I got misunderstood here: I have a modem plugged in eth1. I only
>> configured it via Yast to connect to my ISP with username/password
>>
>> Sorry for the confusion :frowning:

> Well if that’s the case, the ADSL modem device manages the connection
> to the internet, provides routing, gateway, and DHCP IP addresses etc.
> Configuring via YaST >> Network Devices >> DSL is not applicable. All
> that is needed is to configure your ethernet port suitably.
>
> Any modem configuration that may be required can usually be done via a
> web interface.

Well no, not if it is just a modem. And it must be a modem since it
mostly works when configured as one. ADSL modems are similar to the old
analogue modems in what they do and how they are driven. The ones I have
seen use a USB connection to the PC, but this one apparently has an
Ethernet connection. Something like this:

http://www.broadbandbuyer.co.uk/Shop/ShopDetail.asp?ProductID=7898

Most ISPs use a device that includes the modem in the same box as a
small computer providing various gateway services and they can be
configured by a browser interface as you say. But some just provide the
modem that must be connected to a host.

But we still don’t know what the modem model is, so we don’t know what
facilities it has to discover the state of the ADSL connection. And
personally I have no idea what facilities Linux provides for controlling
such a device.

Just for additional information, the modem is a Paradyne 6210-A1.

Apparently there might be a Web Interface in the A2 revision, but I couldn’t connect to it (the default address did not ping). I will try while being on the same subnet…

Right now the connection has not been lost for at least two week…

Still weird…

Thank you all!

Okay, so it is just an ADSL modem (CPE Bridge) rather than a modem/router.

m6OpenSuse wrote:
> Just for additional information, the modem is a Paradyne 6210-A1.
>
> Apparently there might be a Web Interface in the A2 revision, but I
> couldn’t connect to it (the default address did not ping). I will try
> while being on the same subnet…

Well, yes, that is what the user manual says …

“Before you start to access the CPE via Ethernet, you must configure
your PC’s TCP/IP address to be
192.168.1.x, where x is any number between 3 and 254. The subnet mask
must be 255.255.255.0. Your
CPE’s default IP address is 192.168.1.1.”

“By default, the LAN port IP address of the CPE is 192.168.1.1. (You can
change this address, or
another address can be assigned by your ISP.)
Note
Your PCs must have IP addresses that place them in the same
subnet as the CPE’s LAN port.”

There doesn’t appear to be a log facility, but there are both ATM and
ADSL statistics pages and a test page that should give you a clue and
information to talk to your ISP

There are also LEDs on the front that give pretty good information.

> Right now the connection has not been lost for at least two week…
>
> Still weird…
>
> Thank you all!