Bug#265183: pppoe workaround of the post-reboot problem
On Sep 23, Vassilii Khachaturov <vassilii@tarunz.org> wrote:
> Marco has pretty much summed it up. I fail to see though why the modem asking
> the host to consider the modem the default gateway is a bug. The routing
Because the modem is not a gateway and will not work as such?
> I think that to add to pppoeconf the support, the following needs to be done:
No, really. This is too much complex.
> 1) from the routing table, one must deduce that there is no direct route to
> the modem, hence the default route will be used
There is no need for a route, host and modem have IP addresses on the
same subnet and can communicate.
> 2) that default route has to be cloned into a direct route to the modem
> (better yet, make that a network route to the net specified by the network
> portion of the modem address)
There must be no default route pointing to the modem, because the modem
is not able to work as a default gateway.
> 3) after that, ppp has to be invoked with the replacedefaultroute option, and
> it will work
If there is no default route pppd will just work. If there is one there
is probably a good reason to have it, so the default should be to leave
it there.
If the speedtouch DHCP server really provides a default route when it's
configured for PPTP tunnels (something which I doubt and I think should
be verified) *maybe* pppoeconf could check if the local address is
10.0.0.1 and 10.0.0.138 is the modem:
if ping ... 10.0.0.138 && \
wget --quiet --output-document=- http://10.0.0.138/welcome.htm \
| grep -q '^<HEAD><TITLE>ADSL Index'; then
echo yes
fi
Then it would have to check if the PPTP server is enabled.
--
ciao, |
Marco | [8117 sfOak.jbPaG1Y]
Reply to: