After updating coreutils to 6.7-r1, pppoe-start complains: # pppoe-start /usr/sbin/pppoe-start: line 44: /bin/id: No such file or directory pppoe-start: You must be root to run this script Reverting to coreutils-6.7 solves the problem. The reason is that /bin/id has been moved to /usr/bin/id, along with several other files. This will probably break a lot of packages out there, rp-pppoe is just a very prominent one.
A simple rp-pppoe reinstall will fix your problem. The configure script detects the @ID@ path.
I had the same problem. Reemerging rp-pppoe after upgrading to coreutils-6.7-r1 solved the problem here. (make sure not to use the linux-headers-2.6.19, because rp-pppoe and ppp don't compile with them)
(In reply to comment #2) > (make sure not to use the linux-headers-2.6.19, because rp-pppoe and ppp don't > compile with them) If that is true, you should open a bug about it.
I have the same problem with linux-headers-2.6.19. I'll open a bug about that; a bug about ppp already exists. Re #1: Thank you for that info, I'll try it as soon as I can recompile rp-pppoe.
rp-pppoe compilation has been solved in bug 159896. Recompiling rp-pppoe has solved this bug, as well. Thanks, guys!
*** Bug 160411 has been marked as a duplicate of this bug. ***
*** Bug 162972 has been marked as a duplicate of this bug. ***
*** Bug 164269 has been marked as a duplicate of this bug. ***
*** Bug 172105 has been marked as a duplicate of this bug. ***
*** Bug 172136 has been marked as a duplicate of this bug. ***
As this problem seems to occur continuously (see list of duplicates) how about adding a comment to sys-apps/coreutils-6.7-r1 that you need to recompile rp-pppoe (and that you need to do it _before_ shutting down the machine). As rp-pppoe is required to read this forum and possibly also to retrieve its own sources, having a solution here is not too helpful.
*** Bug 172335 has been marked as a duplicate of this bug. ***
I must say I'm a bit disappointed. The ppp baselayout net module is in the stable tree for some time now (a year perhaps?) and people still use the crappy rp-pppoe bash scripts?!?
*** Bug 172354 has been marked as a duplicate of this bug. ***
(In reply to comment #13) > The ppp baselayout net module is in the stable tree for some time now (a year > perhaps?) and people still use the crappy rp-pppoe bash scripts?!? The rp-pppoek KDE-button is a nice app for a fast connect/disconnect.
(In reply to comment #13) > I must say I'm a bit disappointed. > The ppp baselayout net module is in the stable tree for some time now (a year > perhaps?) and people still use the crappy rp-pppoe bash scripts?!? I must say I'm a bit disappointed. Although the ppp baselayout net module is in the stable tree for some time now (a year perhaps?) the Gentoo handbook still tells people to use the crappy rp-pppoe bash scripts?!? http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=3#rp-pppoe http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=9#doc_chap6
(In reply to comment #15) > The rp-pppoek KDE-button is a nice app for a fast connect/disconnect. Yeah, but face it; if your Internet connection is some sort of broadband PPP, you are better off with baselayout PPP support. (In reply to comment #16) I find this reply quite rude. > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=3#rp-pppoe > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=9#doc_chap6 Bug 172401 has been added.
(In reply to comment #17) > (In reply to comment #16) > > I find this reply quite rude. Well, my comment is obviously not more rude than yours, since I used almost exactly the same words you did. Anyway, I didn't mean to offend you (or anyone else). I simply tried to show that there are two sides of the same medal and that it might not be ignorance or neglect that has prevented users from following the change of the network scripts. I don't doubt that this change is a change to the better, and I don't doubt that it has been a considerable amount of work to make this change - thanks to the devs (you?) for that. > Bug 172401 has been added. Thanks.
*** Bug 173022 has been marked as a duplicate of this bug. ***
*** Bug 173734 has been marked as a duplicate of this bug. ***
(In reply to comment #13) > I must say I'm a bit disappointed. > The ppp baselayout net module is in the stable tree for some time now (a year > perhaps?) and people still use the crappy rp-pppoe bash scripts?!? > I'd be glad to get rid of rp-pppoe. How does one configure the ppp baselayout module?
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap4
(In reply to comment #13) > I must say I'm a bit disappointed. > The ppp baselayout net module is in the stable tree for some time now (a year > perhaps?) and people still use the crappy rp-pppoe bash scripts?!? Please, put this back into the ebuild in BIG BOLD letters, with a couple of ebeeps and epause. I'm getting _seriously_ fed up w/ all the duplicates. pkg_setup() { einfo "Gentoo is moving toward common configuration file for all network interfaces." einfo "Please use baselayout adsl module for configuring your network using rp-pppoe" einfo "or, better yet, use generic PPP support available in baselayout-1.12." } and add a link to http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap4 there.
(In reply to comment #23) > Please, put this back into the ebuild in BIG BOLD letters, with a couple of > ebeeps and epause. I'm getting _seriously_ fed up w/ all the duplicates. But it will not reduce the frequency of the duplicates! Remember, this is about coreutils breaking *old* (pre coreutils-6.7-r1) installs of rp-pppoe. These users installed rp-pppoe-3.8 a year before this unfortunate incident.
Bleh :/ Lets hope it's over. If not, probably should just revbump the ebuild keeping the stable keywords.
*** Bug 174550 has been marked as a duplicate of this bug. ***
(In reply to comment #25) rp-pppoe has been revbumped. The -r1 is identical with previous revision.
Ok, I hate to generate bugspam, but I got hit with this bug earlier this week. I didn't realize a simple recompile would fix the problem so I tried to get the net script to launch ppp without rp-pppoe (the first module in the net config file). It worked, but on my shorewall router web connections tended to get dropped frquently - pages would not readily load over the connection. Connections from my firewall itself worked just fine. Also, VPN traffic over the firewall worked fine too. Nothing changed on my shorewall config and despite lots of rebuilds and reboots and config tweaks I couldn't get things running normally. Then I tried to troubleshoot rp-pppoe and discovered the references in the connect script to autoconfig on the directory paths, so I rebuilt it, switched back to that module in the net config file, rebooted, and all worked fine instantly. So, there must be some difference between the two modules. Maybe it is some sensitive shorewall config setting, but whatever it is caused me all kinds of hassles. Oh, and many thanks for the config bump - while advance warning would have been a lot better this will at least fix the issue for anyone who can at least get online to rsync.
(In reply to comment #28) > It worked, but on my shorewall router web connections tended to get dropped > frquently - pages would not readily load over the connection. Connections from > my firewall itself worked just fine. Also, VPN traffic over the firewall > worked fine too. Nothing changed on my shorewall config and despite lots of > rebuilds and reboots and config tweaks I couldn't get things running normally. It seems you have the PMTU problem. See this comment in net.example: #WARNING: if MTU of the PPP interface is less than 1500 and you use this #machine as a router, you should add the following rule to your firewall # #iptables -I FORWARD 1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
*** Bug 174925 has been marked as a duplicate of this bug. ***
*** Bug 190773 has been marked as a duplicate of this bug. ***
*** Bug 200250 has been marked as a duplicate of this bug. ***