• Bug#265183: pppoe workaround of the post-reboot problem

    From Eduard Bloch@1:229/2 to All on Fri Aug 13 10:30:13 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    severity 263224 serious
    reassign 262941 modutils
    severity 262941 serious
    merge 262941 263224
    thanks

    #include <hallo.h>
    * Vassilii Khachaturov [Fri, Aug 13 2004, 08:50:58AM]:
    The thing that happens as a by-product of pppoeconf that enables the
    pppoe to work later on is the loading of the pppoe module. So to have
    pppoe working after reboot, `modprobe pppoe' is needed before `pon dsl-provider'. I think pppoeconf should have done something differently transparent to the user. FWIW, here's the /etc/ppp/peers/dsl-provider it
    had generated. See this also in connection with the routing quirk
    described in the original report (that had to be worked around with the assigning of a static address).

    Eduard: please feel free to fork #265183 to pppoeconf bugs (on the

    As said to the previous bug reporters, it is simply not my job to load
    _kernel_ modules for some other package. It would just additional
    complexity while there are other places where it must be fixed. I agree
    that this bug looks very shameful for a fresh Debian release so it
    should be release critical. Especially when there is such a simple fix.

    PS: I won't clone 265183, there are already enough bug reports to the
    pppoe module problem.

    Regards,
    Eduard.
    --
    OpenBSD fails miserably in this respect, and makes for an example of how NOT
    to work with the community on security issues. Their approach is, roughly,
    "we fixed this a while ago but didn't tell anyone, so you're vulnerable and we're not, ha-ha-ha".


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Vassilii Khachaturov@1:229/2 to All on Fri Aug 13 10:30:13 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    The thing that happens as a by-product of pppoeconf that enables the
    pppoe to work later on is the loading of the pppoe module. So to have
    pppoe working after reboot, `modprobe pppoe' is needed before `pon dsl-provider'. I think pppoeconf should have done something differently
    with the files it generated so that the module loading would have been transparent to the user. FWIW, here's the /etc/ppp/peers/dsl-provider it
    had generated. See this also in connection with the routing quirk
    described in the original report (that had to be worked around with the assigning of a static address).

    Eduard: please feel free to fork #265183 to pppoeconf bugs (on the
    routing and the module loading issues), or just ask me to do so.
    (However, I'm going on vacation and will be offline for the next week,
    though, so I'll be unable to open the new bugs right away).

    # Configuration file for PPP, using PPP over Ethernet
    # to connect to a DSL provider.
    #
    # See the manual page pppd(8) for information on all the options.

    ##
    # Section 1
    #
    # Stuff to configure...

    # MUST CHANGE: Uncomment the following line, replacing the [email protected]
    # by the DSL user name given to your by your DSL provider.
    # (There should be a matching entry in /etc/ppp/pap-secrets with the password.) #user [email protected]

    # Use the pppoe program to send the ppp packets over the Ethernet link
    # This line should work fine if this computer is the only one accessing
    # the Internet through this DSL connection. This is the right line to use
    # for most people.
    #pty "/usr/sbin/pppoe -I eth0 -T 80 -m 1452"

    # An even more conservative version of the previous line, if things
    # don't work using -m 1452...
    #pty "/usr/sbin/pppoe -I eth0 -T 80 -m 1412"

    # If the computer connected to the Internet using pppoe is not being used
    # by other computers as a gateway to the Internet, you can try the following
    # line instead, for a small gain in speed:
    #pty "/usr/sbin/pppoe -I eth0 -T 80"


    # The following two options should work fine for most DSL users.

    # Assumes that your IP address is allocated dynamically
    # by your DSL provider...
    noipdefault
    # Try to get the name server addresses from the ISP.
    usepeerdns
    # Use this connection as the default route.
    # Comment out if you already have the correct default route installed. defaultroute

    ##
    # Section 2
    #
    # Uncomment if your DSL provider charges by minute connected
    # and you want to use demand-dialing.
    #
    # Disconnect after 300 seconds (5 minutes) of idle time.

    #demand
    #idle 300

    ##
    # Section 3
    #
    # You shouldn't need to change these options...

    hide-password
    lcp-echo-interval 20
    lcp-echo-failure 3
    # Override any connect script that may have been set in /etc/ppp/options. connect /bin/true
    noauth
    persist
    mtu 1492

    # RFC 2516, paragraph 7 mandates that the following options MUST NOT be
    # requested and MUST be rejected if requested by the peer:
    # Address-and-Control-Field-Compression (ACFC)
    noaccomp
    # Asynchronous-Control-Character-Map (ACCM)
    default-asyncmap

    plugin rp-pppoe.so eth0

    user "[CENSORED]"



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)