Bug#265183: pppoe workaround of the post-reboot problem
> > It is a gateway and does work as such. Did I not write in my last e-mail
> > that *without* starting pppoe one can reach the provider's WAN via the
> > default route going via the speedtouch?
> Then the modem is configured as a router and you don't need need PPTP
> at all...
Marco, you seem to have forgotten another portion of the info I had
mentioned earlier in the thread (to another portion of the same mail I had
referred in the text you've just quoted!). While my traffic is routed to
the WAN, being a 10..... address it is NOT routable outside of it.
Therefore, to get to the global Internet space, I need to establish PPTP.
(A bit OT: I can still be using the provider's WAN e.g. to use their DNS
forwarders rather than going to the DNS via the PPTP tunnel, but that
would require me to add routes also to the DNS servers on the provider's
LAN. This complication is not worth the negligible benefit of using the
DNS. Overall, for a clean solution I should have the modem negotiate with
my computer using a routing protocol and tell it about the provider WAN
IPs reachable via the ethernet link to the modem, but this option is not
provided, at least not in the default SpeedTouch config. Anyhow, this is
not relevant to the pppoeconfig discussion.)
> > Unfortunately, .138 is the firmware default of my modem, but a lot of
> > folks reconfigure the address; I can also imagine other models using
> Their problem.
Agreed, at least until a lot of folks complain :)
> > addresses other than .138. As pppoeconf already discovers the modem
> > by its own means, so I don't think the hardwiring saves a lot of coding.
> It does not discover the IP address.
It knows its Ethernet address, it's the same LAN, and I bet it can send a
RARP request to obtain one. Anyhow, as I am not giving a script patch and
you do, I think that a hack that does what is needed in the most common
case is definitely better than nothing.
V.
Reply to: