Bug 1002738
Summary: | Kernel mode pppoe fails to connect to the correct access concentrator specified by the rp_pppoe_sevice parameter in a multi-ac environment | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | R. K. Rajeev <rajeevrk> |
Component: | ppp | Assignee: | Michal Sekletar <msekleta> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | jsynacek, maclean, msekleta, rajeevrk, thozza |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 19:26:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
R. K. Rajeev
2013-08-29 20:30:37 UTC
I've also seen this bug, where the rp_pppoe_service parameter is not seen by pppd when using the plugin rp-pppoe.so. A fix is to specify the interface name last in the PLUGIN_OPTS within pppoe-connect. pppoe-connect already does that in the case of the pppoatm.so plugin, with a comment: "# Interface name MUST BE LAST!!". When pppd is parsing options in the runstring, and encounters the interface option for the plugin ("nic-xxx") it calls PPPoEDevnameHook(), and if the interface exists, calls PPPOEInitDevice(). PPPOEInitDevice checks for the existence of the acName and pppd_pppoe_service options, but at that time they will be NULL since they haven't yet been parsed from the runstring. Here'a a patch to pppoe-connect which should fix the problem. --- pppoe-connect.orig 2014-07-17 23:19:18.393983364 -0600 +++ pppoe-connect 2014-07-17 23:20:38.370638631 -0600 @@ -261,10 +261,12 @@ # If we're using kernel-mode PPPoE on Linux... if test "`basename \"$LINUX_PLUGIN\"`" = "rp-pppoe.so" ; then - PLUGIN_OPTS="plugin $LINUX_PLUGIN nic-$ETH" + # Interface name MUST BE LAST!! + PLUGIN_OPTS="plugin $LINUX_PLUGIN" if test -n "$SERVICENAME" ; then PLUGIN_OPTS="$PLUGIN_OPTS rp_pppoe_service $SERVICENAME" fi + PLUGIN_OPTS="$PLUGIN_OPTS nic-$ETH" modprobe pppoe > /dev/null 2>&1 fi # If we're using kernel-mode PPPoATM on Linux... This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |