I've recently swapped over from a cable internet connection to DSL.
I successfully setup the DSL connection by running â€˜pppoeconfâ€™. After configuration, I can start the connection by running â€˜pon dsl-providerâ€™. This allows the core to access the net (I can ping www.google.com
My first problem was that because of the swap, my internet interface is ppp0 and not eth0 like it used to be (LAN interface is still eth1). Obviously this broke internet sharing for the PCs on the network. I solved this by following the instructions in another post and changing an entry in the database according to:
â€œOn the Core, in the pluto_main database, in the Device_DeviceData table there's an entry with FK_DeviceData=32:
It's value can be found with this SQL statement:
SELECT IK_DeviceData FROM Device_DeviceData WHERE FK_DeviceData=32;
It's format is a little less intuitive, but the general idea is that it follows this format: <external interface>,<data>|<internal interface>,<data>.â€
The <external interface> was eth0, so I changed it to ppp0, and now after a reboot, providing I run â€˜pon dsl-providerâ€™ to establish the DSL connection, computers on the LAN can access the internet.
My problem now is how to make the DSL link connect automatically on boot (before pluto tries to update itself would be nice too).
Running â€˜pppoeconfâ€™ modifies /etc/network/interfaces and adds the following to bring up the connection at boot:
iface dsl-provider inet ppp
# please do not modify the following line
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
Pluto overwrites this file, and thus the DSL link isnâ€™t started at boot and requires me to run â€˜pon dsl-providerâ€™.
How should I configure Pluto to bring my DSL connection up at boot time?