I tested Puppy 4.00 and using our somewhat primitive frontend to the Roaring Penguin utilities I was able to make a connection. Except for that problem where /etc/ppp/resolv.conf and /etc/resolv.conf became symlinks to each other. I reversed the original arrangement, made /etc/resolv.conf a symlink to /etc/ppp/resolv.conf, the latter being a normal file, and we were in business.
Then we tackled Ubuntu. Oh no, first we tried Windows XP, as Phil had recently reinstalled it and it wasn't setup -- oh what a ratsnest of paths we followed, trying to setup PPPOE! Eventually we phoned BBNet tech support and they walked us through it.
Then we got onto Ubuntu. Phil had some prior information that we should open a terminal window and run 'sudo pppoeconf'. That was a very pleasant experience indeed and we were quickly online.
So what is this 'pppoeconf'? It's a great little script, that uses Xdialog for the GUI. What really interested me is that it can use the 'ppp' package only (as that now has pppoe capability) and the Roaring Penguin utilities are not required.
I hacked the 'pppoeconf' script a bit to get it to work in Puppy, but as I'm home now I can't test it. I only get through the first couple of dialog windows. Anyone interested in testing it? I have made it into a PET package, 'pppoeconf_pup-1.17' and uploaded to here:
(nothing to do with UniPup, that was just a convenient place to upload to)
To test/debug, run 'pppoeconf' in a terminal window so that you can see any error messages.
Comments:Posted on 10 Jul 2008, 20:05 by adi
pppoe can be also solved buying a router from shop. The router is accessed with the browser and the network automaticaly through dhcp but in puppy 3.01 pppoe works fine.