Hugo Vanwoerkom wrote:
Stephen Powell wrote:
On Mon, 5 Apr 2010 13:26:14 -0400 (EDT), Hugo Vanwoerkom wrote:
Stephen Powell wrote:
This is a graphical representation of the problem:
http://www.esnips.com/doc/84c672ef-50e8-446e-9560-4c4316ae68e9/do_sysup_201004
Hugo
--
To UNSUBSCRIBE, email
On Tue, 6 Apr 2010 16:52:25 -0400 (EDT), Ron Johnson wrote:
>
> My concern is that, since the upstream dhcpd sends the lease info at
> the moment of negotiation, you'd need to start tshark *before* pon
> and I don't know if tshark will see the new interface and start
> capturing on it.
Good po
On 2010-04-06 15:28, Stephen Powell wrote:
On Tue, 6 Apr 2010 14:20:11 -0400 (EDT), Hugo Vanwoerkom wrote:
But what would I be looking for?
You would be looking for DHCP-related packets that would
identify the length of the DHCP lease. I've never used wireshark;
I only know conceptually the k
On Tue, 6 Apr 2010 14:20:11 -0400 (EDT), Hugo Vanwoerkom wrote:
>
> But what would I be looking for?
You would be looking for DHCP-related packets that would
identify the length of the DHCP lease. I've never used wireshark;
I only know conceptually the kinds of things it can do; so if you
need sp
Stephen Powell wrote:
On Mon, 5 Apr 2010 15:33:20 -0400 (EDT), Hugo Vanwoerkom wrote:
Stephen Powell wrote:
You might want to try a Linux sniffer and see what you can come up
with. I've heard about a product called wireshark, but I've never
used it. You can also ask your ISP how long the leas
On Mon, 5 Apr 2010 15:33:20 -0400 (EDT), Hugo Vanwoerkom wrote:
> Stephen Powell wrote:
>> You might want to try a Linux sniffer and see what you can come up
>> with. I've heard about a product called wireshark, but I've never
>> used it. You can also ask your ISP how long the lease is for the
>>
Stephen Powell wrote:
On Mon, 5 Apr 2010 13:37:42 -0400 (EDT), Hugo Vanwoerkom wrote:
Stephen Powell wrote:
Look through /var/log/syslog and see if you can find something which
identifies the lease length. For example, on my ethernet link, I
see a message in the log which says
dhclient: bo
On Mon, 5 Apr 2010 13:37:42 -0400 (EDT), Hugo Vanwoerkom wrote:
> Stephen Powell wrote:
>>
>> Look through /var/log/syslog and see if you can find something which
>> identifies the lease length. For example, on my ethernet link, I
>> see a message in the log which says
>>
>>dhclient: bound t
Stephen Powell wrote:
On Mon, 5 Apr 2010 13:26:14 -0400 (EDT), Hugo Vanwoerkom wrote:
Stephen Powell wrote:
This is sounding more and more like an expired DHCP lease.
You really need to investigate this, as I suggested earlier.
ISPs really don't want dial-up users to be connected very long.
Th
On Mon, 5 Apr 2010 13:26:14 -0400 (EDT), Hugo Vanwoerkom wrote:
> Stephen Powell wrote:
>>
>> This is sounding more and more like an expired DHCP lease.
>> You really need to investigate this, as I suggested earlier.
>>
>> ISPs really don't want dial-up users to be connected very long.
>> They wan
Stephen Powell wrote:
On Sun, 4 Apr 2010 11:41:32 -0400 (EDT), Hugo Vanwoerkom wrote:
But if the ISP hung up on me I would get a 'debian pppd[1192]: Hangup
(SIGHUP)' and I don't get that.
If my IP expired I would not be able to ping it, but I can. I just can't
dig anything.
A better test wo
Stephen Powell wrote:
On Sun, 4 Apr 2010 17:12:32 -0400 (EDT), Hugo Vanwoerkom wrote:
It still happens with static nameservers of Google and OpenDNS.
It's the ISP
This is sounding more and more like an expired DHCP lease.
You really need to investigate this, as I suggested earlier.
ISPs reall
Stephen Powell writes:
> They give you a short DHCP lease and no renewals. DHCP lease time
> varies from ISP to ISP. Generally, the less you pay per month, the
> shorter the DHCP lease time. They force *you* to hang up on *them*.
Dial on demand makes this fairly easy to deal with.
--
John Hasl
On Sun, 4 Apr 2010 17:12:32 -0400 (EDT), Hugo Vanwoerkom wrote:
>
> It still happens with static nameservers of Google and OpenDNS.
> It's the ISP
This is sounding more and more like an expired DHCP lease.
You really need to investigate this, as I suggested earlier.
ISPs really don't want dial-u
Hugo Vanwoerkom wrote:
Camaleón wrote:
On Sat, 03 Apr 2010 12:06:51 -0600, Hugo Vanwoerkom wrote:
I have a dialup modem.
Pppconfig configured the connection with 'nameservers dynamic'.
Is there any chance you could setup pppconfig to use "static
nameservers"? If yes, choose that and set th
On Sun, 4 Apr 2010 11:41:32 -0400 (EDT), Hugo Vanwoerkom wrote:
>
> But if the ISP hung up on me I would get a 'debian pppd[1192]: Hangup
> (SIGHUP)' and I don't get that.
>
> If my IP expired I would not be able to ping it, but I can. I just can't
> dig anything.
A better test would be whethe
Mihira Fernando wrote:
On Sun, 04 Apr 2010 12:00:52 -0500
Hugo Vanwoerkom wrote:
I can now host 8.8.8.8 and get google-public-dns-a.google.com
I can dig google-public-dns-a.google.com and get
google-public-dns-a.google.com. 86283 IN A 8.8.8.8
But when I ping 8.8.8.8 I get no response e
Camaleón wrote:
On Sat, 03 Apr 2010 12:06:51 -0600, Hugo Vanwoerkom wrote:
I have a dialup modem.
Pppconfig configured the connection with 'nameservers dynamic'.
Is there any chance you could setup pppconfig to use "static
nameservers"? If yes, choose that and set the nameservers you want
On Sun, 04 Apr 2010 12:00:52 -0500
Hugo Vanwoerkom wrote:
> I can now host 8.8.8.8 and get google-public-dns-a.google.com
> I can dig google-public-dns-a.google.com and get
> google-public-dns-a.google.com. 86283 IN A 8.8.8.8
>
> But when I ping 8.8.8.8 I get no response even though I can
Wayne wrote:
Hugo Vanwoerkom wrote:
Wayne wrote:
Hugo Vanwoerkom wrote:
Hi,
I have a dialup modem.
O
<--- SNIP --->
They work now because I can 'dig www.google.com' and get 216.239.32.10
and then 'host 216.239.32.10' and get
Name: ns1.google.com
Address: 216.239.32.10
How did you get
Mihira Fernando wrote:
On Sun, 04 Apr 2010 10:42:49 -0500
Hugo Vanwoerkom wrote:
But if it dropped me I would see a SIGHUP in syslog and I don't. I
can still ping the IP that was assigned to me.
Hugo
You can always ping the IP assigned to you from your OWN PC. At the
times you cannot resolv
On Sat, 03 Apr 2010 12:06:51 -0600, Hugo Vanwoerkom wrote:
> I have a dialup modem.
>
> Pppconfig configured the connection with 'nameservers dynamic'.
Is there any chance you could setup pppconfig to use "static
nameservers"? If yes, choose that and set the nameservers you want
(openDNS or Go
Hugo Vanwoerkom wrote:
Wayne wrote:
Hugo Vanwoerkom wrote:
Hi,
I have a dialup modem.
O
<--- SNIP --->
They work now because I can 'dig www.google.com' and get 216.239.32.10
and then 'host 216.239.32.10' and get
Name: ns1.google.com
Address: 216.239.32.10
How did you get Montevideo UY
John Hasler wrote:
Run Pppconfig and enable either "Persist" or "Demand".
But then it would dial again after SIGHUP and I know that works. I am
trying to find out why I cannot dig anything anymore but still ping my
own IP.
Hugo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.
On Sun, 04 Apr 2010 10:42:49 -0500
Hugo Vanwoerkom wrote:
> But if it dropped me I would see a SIGHUP in syslog and I don't. I
> can still ping the IP that was assigned to me.
>
> Hugo
You can always ping the IP assigned to you from your OWN PC. At the
times you cannot resolve any domains, can
On 2010-04-04 10:26, Hugo Vanwoerkom wrote:
[snip]
But we run Linux. The ISP will say it's my problem for running Linux.
Fib.
(I'd write "lie", but there are too many ESLs on the list who might
think it means "lay down"...)
--
"History does not long entrust the care of freedom to the weak
Freeman wrote:
On Sat, Apr 03, 2010 at 12:06:51PM -0600, 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
Stephen Powell wrote:
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 th
Wayne wrote:
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
Freeman wrote:
On Sat, Apr 03, 2010 at 01:09:11PM -0600, Hugo Vanwoerkom wrote:
...
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-ov
Run Pppconfig and enable either "Persist" or "Demand".
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bpe0jlqd@thumper.dhh.gt.org
On Sat, Apr 03, 2010 at 01:09:11PM -0600, Hugo Vanwoerkom wrote:
...
>
> 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
On Sat, Apr 03, 2010 at 12:06:51PM -0600, 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
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 wit
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 f
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 u
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:
37 matches
Mail list logo
