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 to xxx.xxx.xxx.xxx -- renewal in 290593 seconds.
That works out to about 3.36 days, in my case. The message will
probably be different for ppp, but you get the idea. And if the
DHCP server is set up not to honor renewal requests, which is
likely to be the case for dial-up lines, then you have a problem.
I don't see anything like that. This what I do see:
...
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfReq id=0x1 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
Apr 5 12:10:43 debian pppd[1030]: sent [IPCP ConfReq id=0x1 <compress
VJ 0f 00> <addr 0.0.0.0>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [IPCP ConfReq id=0x1 <compress
VJ 0f 01> <addr 200.57.219.18>]
Apr 5 12:10:43 debian pppd[1030]: sent [IPCP ConfNak id=0x1 <compress
VJ 0f 00>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfReq id=0x1 < 11 06 00
01 01 03>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfRej id=0x1 < 11 06 00
01 01 03>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfRej id=0x1 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfReq id=0x2]
Apr 5 12:10:43 debian pppd[1030]: rcvd [IPCP ConfNak id=0x1 <addr
200.57.201.70>]
Apr 5 12:10:43 debian pppd[1030]: sent [IPCP ConfReq id=0x2 <compress
VJ 0f 00> <addr 200.57.201.70>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [IPCP ConfReq id=0x2 <compress
VJ 0f 00> <addr 200.57.219.18>]
Apr 5 12:10:43 debian pppd[1030]: sent [IPCP ConfAck id=0x2 <compress
VJ 0f 00> <addr 200.57.219.18>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfReq id=0x2 <mppe -H -M
-S -L -D +C>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfRej id=0x2 <mppe -H -M
-S -L -D +C>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfRej id=0x2]
Apr 5 12:10:43 debian pppd[1030]: rcvd [IPCP ConfAck id=0x2 <compress
VJ 0f 00> <addr 200.57.201.70>]
Apr 5 12:10:43 debian pppd[1030]: Cannot determine ethernet address for
proxy ARP
Apr 5 12:10:43 debian pppd[1030]: local IP address 200.57.201.70
Apr 5 12:10:43 debian pppd[1030]: remote IP address 200.57.219.18
Apr 5 12:10:43 debian pppd[1030]: Script /etc/ppp/ip-up started (pid 1163)
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfReq id=0x3 < 11 05 00
01 04>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfReq id=0x3 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfRej id=0x3 < 11 05 00
01 04>]
Apr 5 12:10:43 debian chronyd[2217]: Source 200.23.51.205 online
Apr 5 12:10:43 debian chronyd[2217]: Source 132.248.81.29 online
Apr 5 12:10:43 debian chronyd[2217]: Source 148.234.7.30 online
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfRej id=0x3 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfReq id=0x4]
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfReq id=0x4 < 11 05 00
01 03>]
Apr 5 12:10:43 debian pppd[1030]: sent [CCP ConfRej id=0x4 < 11 05 00
01 03>]
Apr 5 12:10:43 debian pppd[1030]: rcvd [CCP ConfRej id=0x4]
I see you have debugging messages turned on. Good. You're right,
there's nothing in there about a lease time. At least none that I can
see. The most important message in there is this one:
Apr 5 12:10:43 debian pppd[1030]: local IP address 200.57.201.70
which tells you what IP address it assigned to you. This should agree
with what is reported by "ifconfig" under device ppp0. But it doesn't
tell you *how long* it belongs to you.
A number of years ago I took a formal networking course from a well-known
company that offers IT training courses for a fee. This was back when
ppp connections via async dial-up were the norm for home users. Few
people had high-speed internet connections at home back then. The
instructor told us a story about one of his experiences. He was having
trouble with his ISP. He could get in and work for a while, but then
he would have trouble and the only fix was to hang up and re-dial.
He called the ISP's support line, and they gave him the run-around, blaming his
phone lines, his modem, the phone company, etc. But he became
suspicious. Since he was a networking guru, he put a sniffer on the
network in promiscuous mode and eventually proved that the ISP was
giving him a DHCP lease for one hour by mailing a print-out from the
sniffer to the ISP. The result? They canceled his service! They
said they didn't want his business! I guess they considered a
knowledgeable customer too dangerous to have around.
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
IP address. First level support might not know what you're talking
about. And if you do get someone who knows what you are asking,
he might not know the answer. And if he does know the answer,
he might lie to you. But you can ask. And you can install a
sniffer and figure out how to use it. Even if you decide not to
tell the ISP what you know, at least you will have the personal
satisfaction of knowing what their lease time *really* is.
And if the lease time turns out to be long, you will have
eliminated a possibility.