On Sun, 09 Dec 2007 14:01:27 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
cpghost wrote:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
--- manually restarting ppp(1), then:
17:10:47.306928 00:00:24:c2:45:74
cpghost wrote:
On Sun, 09 Dec 2007 14:01:27 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
cpghost wrote:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
--- manually restarting ppp(1), then:
17:10:47.306928 00:00:24:c2:45:74
On Sun, 09 Dec 2007 14:02:50 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
Adding brian to CC list.
Alexander Motin wrote:
cpghost wrote:
I think such behaviour can take place if ppp daemon for some
reason don't waits for reply but closes session immediately after
sending connect
On Thu, 6 Dec 2007 16:11:07 +0100
cpghost [EMAIL PROTECTED] wrote:
On Thu, 06 Dec 2007 13:57:16 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
The problem is that the last mile carrier of the PPP provider
that this router is attached to disconnects the ppp session
cpghost wrote:
On Thu, 6 Dec 2007 16:11:07 +0100
cpghost [EMAIL PROTECTED] wrote:
On Thu, 06 Dec 2007 13:57:16 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
The problem is that the last mile carrier of the PPP provider
that this router is attached to disconnects the ppp
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
cpghost wrote:
On Thu, 6 Dec 2007 16:11:07 +0100
cpghost [EMAIL PROTECTED] wrote:
On Thu, 06 Dec 2007 13:57:16 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
The problem is that the last
cpghost wrote:
Could you provide tcpdump output for connection tries from your
Ethernet interface? Use -pes 0 options please.
Will do; but I'll first have to wait 24h from now to get a
forcibly disconnected session (I've just had to restart ppp
again).
All right, I've got a good tcpdump now:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
--- manually restarting ppp(1), then:
17:10:47.306928 00:00:24:c2:45:74 ff:ff:ff:ff:ff:ff, ethertype
PPPoE D (0x8863), length 32: PPPoE PADI [Host-Uniq 0x40C663C1]
cpghost wrote:
If I remember correctly, sending two PADIs in quick succession
was ppp's normal behaviour for *years* now (is it expected or
required by the protocol? I don't know). I've always wondered
why it was so. But that didn't cause any harm as it seemed one
of the two PADO was picked up
On Sun, 09 Dec 2007 22:57:46 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
Your host generates huge number of simultaneous session requests.
Looking on different Host-Uniq values it should be different ng_pppoe
sessions/hooks as Host-Uniq is actually pointer to the hook/session
internal
cpghost wrote:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
cpghost wrote:
On Thu, 6 Dec 2007 16:11:07 +0100
cpghost [EMAIL PROTECTED] wrote:
On Thu, 06 Dec 2007 13:57:16 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
The problem is that the
cpghost wrote:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
--- manually restarting ppp(1), then:
17:10:47.306928 00:00:24:c2:45:74 ff:ff:ff:ff:ff:ff, ethertype
PPPoE D (0x8863), length 32: PPPoE PADI [Host-Uniq 0x40C663C1]
On Sun, 09 Dec 2007 23:52:01 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
I think such behaviour can take place if ppp daemon for some
reason don't waits for reply but closes session immediately after
sending connect request. If it so it also explains original no
On Sun, 09 Dec 2007 14:01:27 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
cpghost wrote:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer [EMAIL PROTECTED] wrote:
--- manually restarting ppp(1), then:
17:10:47.306928 00:00:24:c2:45:74
On Thu, 06 Dec 2007 13:57:16 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
The problem is that the last mile carrier of the PPP provider
that this router is attached to disconnects the ppp session
forcibly once every 24h. Before the update, ppp would detect
this and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
cpghost wrote:
The problem is that the last mile carrier of the PPP provider
that this router is attached to disconnects the ppp session
forcibly once every 24h. Before the update, ppp would detect
this and reconnect immediately. After the update,
On Thu, 06 Dec 2007 13:57:16 +0200
Alexander Motin [EMAIL PROTECTED] wrote:
cpghost wrote:
The problem is that the last mile carrier of the PPP provider
that this router is attached to disconnects the ppp session
forcibly once every 24h. Before the update, ppp would detect
this and
Hello,
Since I've updated a RELENG_6 router a few days ago, a long
gone problem with ppp cropped up (again?); and I'm suspecting
a regression between ng_pppoe.c 1.74.2.3 and 1.74.2.4.
The problem is that the last mile carrier of the PPP provider
that this router is attached to disconnects the
18 matches
Mail list logo
