From: Hugo Vanwoerkom on
Hi,

I have a dialup modem.

Pppconfig configured the connection with 'nameservers dynamic'.

/etc/ppp/resolv.conf always contains:

nameserver 148.240.118.40
nameserver 189.209.208.181

although the timestamp on the file changes with each connection:

-rw-r--r-- 1 root root 53 2010-04-03 11:00 resolv.conf

Now the problem:

Several times a day internet communication stops and all that appears on
the status bar of iceweasel is 'Looking up xxxx' where xxxx is the site
that was being displayed.

This is only resolved when you take down the ppp0 interface and bring it
back up, redialling the ISP.

And the same nameservers appear in resolv.conf.

Can anyone explain this behavior? And what to do about it?

BTW it again happened at 11:00 as you can see.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/hp803t$ri5$1(a)dough.gmane.org
From: Ron Johnson on
On 2010-04-03 13:06, Hugo Vanwoerkom wrote:
> Hi,
>
> I have a dialup modem.
>
> Pppconfig configured the connection with 'nameservers dynamic'.
>
> /etc/ppp/resolv.conf always contains:
>
> nameserver 148.240.118.40
> nameserver 189.209.208.181
>
> although the timestamp on the file changes with each connection:
>
> -rw-r--r-- 1 root root 53 2010-04-03 11:00 resolv.conf

Probably because each time you dial in, dhcp gets a pot-load of
config data from your ISP and must put it somewhere.

Since your ISP's DNS servers never change, they keep sending the
same nameserver IP addresses to your machine.

> Now the problem:
>
[snip]
>
> Can anyone explain this behavior? And what to do about it?
>

Dodgy upstrem modems? Overheating causing *your* modem to flake
out? Dodgy copper somewhere between your PC and the ISP which is
nevertheless good enough for voice?

--
"History does not long entrust the care of freedom to the weak
or the timid." Dwight Eisenhower


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BB78679.5050808(a)cox.net
From: Wayne on
Hugo Vanwoerkom wrote:
> Hi,
>
> I have a dialup modem.
>
> Pppconfig configured the connection with 'nameservers dynamic'.
>
> /etc/ppp/resolv.conf always contains:
>
> nameserver 148.240.118.40
> nameserver 189.209.208.181

Don't know. Have you contacted your ISP to see of they are correct?
DNS servers are usually under the ISP's address range.

They look strange to me as the first one is in Montevideo UY and the
next is in Mexico. But I do not know how they do DNS in SA

> although the timestamp on the file changes with each connection:
>
> -rw-r--r-- 1 root root 53 2010-04-03 11:00 resolv.conf
>
> Now the problem:
>
> Several times a day internet communication stops and all that appears on
> the status bar of iceweasel is 'Looking up xxxx' where xxxx is the site
> that was being displayed.

When I was on dialup if I connected and did nothing for some period of
time, the ISP would drop the connection. I set a cron job to ping a web
address every 10 minutes and stopped that nonsense. If I stayed connect
for more then 5 hours they would drop the connect as well. Ask your ISP
what their policy is on this.

>
> This is only resolved when you take down the ppp0 interface and bring it
> back up, redialling the ISP.

Understandable if the ISP timed you out.
>
> And the same nameservers appear in resolv.conf.

They always use the same DNS Servers, which is normal, here anyway.

> Can anyone explain this behavior? And what to do about it?
>

Try the cron suggestion above.

>
Wayne


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BB7907D.7040608(a)gmail.com
From: Stephen Powell on
On Sat, 3 Apr 2010 14:06:51 -0400 (EDT), Hugo Vanwoerkom wrote:
>
> I have a dialup modem.
>
> Pppconfig configured the connection with 'nameservers dynamic'.
>
> /etc/ppp/resolv.conf always contains:
>
> nameserver 148.240.118.40
> nameserver 189.209.208.181
>
> although the timestamp on the file changes with each connection:
>
> -rw-r--r-- 1 root root 53 2010-04-03 11:00 resolv.conf
>
> Now the problem:
>
> Several times a day internet communication stops and all that appears on
> the status bar of iceweasel is 'Looking up xxxx' where xxxx is the site
> that was being displayed.
>
> This is only resolved when you take down the ppp0 interface and bring it
> back up, redialling the ISP.
>
> And the same nameservers appear in resolv.conf.
>
> Can anyone explain this behavior? And what to do about it?
>
> BTW it again happened at 11:00 as you can see.

I'm not surprised that the nameservers don't change. The file
is rewritten with each connection, thus the changing timestamp.
The nameservers' IP addresses don't change often. The real
problem, of course, is the loss of connectivity.

There are two possibilities. ISPs that offer dial-up connectivity
have a limited number of phone lines. If customers get a busy
signal when they try to dial in, the ISPs get complaints. And the
ISPs don't like complaints. So they often have an automatic system
where if all lines are in use and someone tries to dial in, the person
who has been connected the longest gets bumped. In other words,
the ISP will hang up on you to free the phone line for someone who
wants to dial in. Of course, when they hang up on people, they get
complaints too. But not as much as if they can't get in in the
first place.

Another possibility is a short DHCP lease. When the PPP connection
is established, they lease you an IP address. And that IP address
has a limited lifetime. When it expires, you're dead. Not much
you can do about that except reconnect. ISPs don't like you to
keep your PPP connection for an extended period of time. The longer
their customers keep a dial-up connection, the more phone lines
they need to have. And phone lines (and modems) cost money. They
want you to get it, get your e-mail, and get out. They don't want
you connected for a long time. And so they give you a short DHCP
lease. And when it expires, you're dead. (And when you complain,
they'll blame the phone company!) Look at the logs. You may be able
to determine the length of your DHCP lease from there.

--
.''`. Stephen Powell <zlinuxman(a)wowway.com>
: :' :
`. `'`
`-


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/538527349.931671270321617759.JavaMail.root(a)md01.wow.synacor.com
From: Hugo Vanwoerkom on
Ron Johnson wrote:
> On 2010-04-03 13:06, Hugo Vanwoerkom wrote:
>> Hi,
>>
>> I have a dialup modem.
>>
>> Pppconfig configured the connection with 'nameservers dynamic'.
>>
>> /etc/ppp/resolv.conf always contains:
>>
>> nameserver 148.240.118.40
>> nameserver 189.209.208.181
>>
>> although the timestamp on the file changes with each connection:
>>
>> -rw-r--r-- 1 root root 53 2010-04-03 11:00 resolv.conf
>
> Probably because each time you dial in, dhcp gets a pot-load of config
> data from your ISP and must put it somewhere.
>
> Since your ISP's DNS servers never change, they keep sending the same
> nameserver IP addresses to your machine.
>
>> Now the problem:
>>
> [snip]
>>
>> Can anyone explain this behavior? And what to do about it?
>>
>
> Dodgy upstrem modems? Overheating causing *your* modem to flake out?
> Dodgy copper somewhere between your PC and the ISP which is nevertheless
> good enough for voice?
>

Dodgy copper between me and the ISP? In Mexico? You mean dangling
copper? Like that thing hanging down from the pole in front of the house
and that banged-up box on the corner that everybody puts their left-over
soda's on?








--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/hp83oo$6ub$1(a)dough.gmane.org
 |  Next  |  Last
Pages: 1 2 3 4 5 6 7
Prev: ALSA problem? ...SOLVED
Next: Installing Sugar in testing