On 2017-04-02 10:47:41, Konstantin Schukraft <[email protected]> wrote:
> Hello,
>
>> I am using pppoe on OpenBSD 6.0 stable to setup a connection
>> to Deutsche Telekom (VDSL). Problem: Usually it takes 3 or 4
>> minutes to establish the connection. Is this as expected?
>
> I'm in the same situation. The problem seems to lie with with VDSL,
> the modem takes a long time compared to the old ADSL modems to
> synchronise with the DSLAM on the other side; 2 minutes are not unusual.
>
> [...]
>
> I already contemplated asking on this list if there is a way to
> modify these wait periods, since I can't find anything in the
> documentation.
>
If this is truly due to the modem itself not having sync, then I
doubt the following option will help, but I've found that in my
case I need to have the kernel option PPPOE_TERM_UNKNOWN_SESSIONS
added to my kernel build in order to avoid long time-outs if I
reboot my machine for instance.
By default, the kernel will not send a PADT request to terminate
the old PPPoE session in order to not interfere with other PPPoE
sessions.
"man 4 pppoe" explains this better than I could. To wit:
------------8<---------------
KERNEL OPTIONS
A pppoe enabled kernel will not interfere with other PPPoE
implementations running on the same machine. Under special
circumstances (details below) this is not desirable, so the
pppoe driver can be told to kill all unknown PPPoE sessions
received by the Ethernet interface used for a configured
pppoe interface. To do this, add the following to your
kernel config file:
option PPPOE_TERM_UNKNOWN_SESSIONS
This option is only useful if you have a static IP address
assigned and your ISP does not use LCP echo requests to
monitor the link status. After a crash or power failure the
peer device still tries to send data to the no longer active
session on your computer, and might refuse to reestablish a
new connection, because there already is an open session. On
receipt of such packets, the pppoe driver with this option
set will send a PADT packet (request to terminate the
session). The peer will immediately disconnect the orphaned
session and allow a new one to be established.
------------8<---------------
Again, this option is only meant to apply in very specific
circumstances, which is likely why it is not the default. I only
mention it because it seems like it might be worthwhile to see if
it fixes the issues you're seeing. Though as I stated above, if
this is due to the modem itself not having sync with the DSLAM,
then I doubt that it will have any effect.
As always, the standard disclaimer applies to anyone who modifies
their kernel.
--
Bryan
