-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi folks,
On 04/02/17 11:48, Bryan Linton wrote: > On 2017-04-02 10:47:41, Konstantin Schukraft <konstan...@schukraft.org> wrote: > > "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. > I am surely not afraid to rebuild the kernel, but since I don't have a static IPv4 address, I would assume that setting PPPOE_TERM_UNKNOWN_SESSIONS wouldn't make a difference in this case, correct? Regards Harri -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAljiUtAACgkQCp4qnmbT gcv8UAf+J03eqtRcsBV23TrVQUstImXwrUFxrtZ5VWohLDIYG8dguvhEYi0w8e6j VkBMTdXg6E1dEW+5nIw20I/MICuVxL/Kc6PHR+rtYPwApzeT0TdKUUSyWzxz4rLy qicnjMphHeZkoORb6vveoETA80EUdyTE0+HREgGu1ja4ZPBXs72lN8Q9g0udAxrT 4JVtQUErQLT1zBVg5mqdNbdgXui1TbuThZH8ZqtHpyzb0nDVnuLbL3SyGG/E8Uqo LnDBz6GKaRxZPjfL6mQH6/9YrSqbbSscg/bEEWoSddA7CD+9l34kUP5fSKEGlKmQ cEBrXGN5bsT7YtqNLvY0EAtn5k6q2Q== =t4ga -----END PGP SIGNATURE-----
