Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31015 - [rp-pppoe 3.10-7] pppoe-start unable to connect while network daemon is running.

Attached to Project: Arch Linux
Opened by Jake Parker (tskmgrar) - Sunday, 05 August 2012, 07:02 GMT
Last edited by Jan de Groot (JGC) - Saturday, 11 August 2012, 10:04 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture i686
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

========Description:============
pppoe-start is unable to connect to the internet or ping google.com while network daemon is running.


========Additional info:========
[rp-pppoe 3.10-7]

========Files affected:========
/etc/rc.conf

=========Files unaffected but used by [rp-pppoe] to store settings========
/etc/ppp/pppoe.conf


========Steps to reproduce:========
1] Enable the "network" daemon in rc.conf.
2] Configure rp-pppoe with your ISP settings.
3] Start pppoe using "pppoe-start" command.
4] After connecting, ping google.com and the ping request will cease to work or it will try pinging via 192.168.1.1 and halt without ping replies.
5] stop pppoe by issuing "pppoe-stop" command.

========Possible Workaround:========
1] Remove "network" daemon from /etc/rc.conf
2] Stop the daemon if running/restart the computer.
3] Issue the "pppoe-start" command to start PPPOE
4] After connecting, ping google.com and it should ping back.

========Cat output before the workaround, of the rc.conf file========
sudo cat /etc/rc.conf
#
# /etc/rc.conf - configuration file for initscripts
#
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
#
# For more details on rc.conf see rc.conf(5).
#

DAEMONS=(syslog-ng alsa network dbus ufw tor crond)

# Storage
#
# USEDMRAID="no"
# USELVM="no"

# Network
#
# interface=
# address=
# netmask=
# gateway=


========Cat output after the workaround , of the rc.conf file========
sudo cat /etc/rc.conf
#
# /etc/rc.conf - configuration file for initscripts
#
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
#
# For more details on rc.conf see rc.conf(5).
#

DAEMONS=(syslog-ng alsa dbus ufw tor crond)

# Storage
#
# USEDMRAID="no"
# USELVM="no"

# Network
#
# interface=
# address=
# netmask=
# gateway=

========Ping output after the workaround, while attempting to ping google.com========
# ping google.com

========Ping output after the workaround, while attempting to ping google.com========
# ping google.com
PING google.com (74.125.236.142) 56(84) bytes of data.
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=1 ttl=53 time=64.2 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=2 ttl=53 time=64.0 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=3 ttl=53 time=64.1 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=4 ttl=53 time=63.4 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=5 ttl=53 time=63.3 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=6 ttl=53 time=62.7 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=7 ttl=53 time=61.6 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=8 ttl=53 time=63.7 ms
64 bytes from xxxxxxxx (74.125.236.142): icmp_req=9 ttl=53 time=63.8 ms

========Copy of the pppoe.conf file========

sudo cat /etc/ppp/pppoe.conf
#***********************************************************************
#
# pppoe.conf
#
# Configuration file for rp-pppoe. Edit as appropriate and install in
# /etc/ppp/pppoe.conf
#
# NOTE: This file is used by the pppoe-start, pppoe-stop, pppoe-connect and
# pppoe-status shell scripts. It is *not* used in any way by the
# "pppoe" executable.
#
# Copyright (C) 2000 Roaring Penguin Software Inc.
#
# This file may be distributed under the terms of the GNU General
# Public License.
#
# LIC: GPL
# $Id$
#***********************************************************************

# When you configure a variable, DO NOT leave spaces around the "=" sign.

# Ethernet card connected to DSL modem
ETH='eth0'

# PPPoE user name. You may have to supply "@provider.com" Sympatico
# users in Canada do need to include "@sympatico.ca"
# Sympatico uses PAP authentication. Make sure /etc/ppp/pap-secrets
# contains the right username/password combination.
# For Magma, use xxyyzz@magma.ca
USER='xxxxxxxx'

# Bring link up on demand? Default is to leave link up all the time.
# If you want the link to come up on demand, set DEMAND to a number indicating
# the idle time after which the link is brought down.
DEMAND=no
#DEMAND=300

# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SPECIFY

# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS. Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=no

DNS1=XXX.XXX.XXX.XXX
DNS2=XXX.XXX.XXX.XXX

# Make the PPPoE connection your default route. Set to
# DEFAULTROUTE=no if you don't want this.
DEFAULTROUTE=yes

### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT

# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong. If you use 0, then pppoe-start
# exits immediately with a successful status and does not wait for the
# link to come up. Time is in seconds.
#
# WARNING WARNING WARNING:
#
# If you are using rp-pppoe on a physically-inaccessible host, set
# CONNECT_TIMEOUT to 0. This makes SURE that the machine keeps trying
# to connect forever after pppoe-start is called. Otherwise, it will
# give out after CONNECT_TIMEOUT seconds and will not attempt to
# connect again, making it impossible to reach.
CONNECT_TIMEOUT=30

# How often in seconds pppoe-start polls to check if link is up
CONNECT_POLL=2

# Specific desired AC Name
ACNAME=

# Specific desired service name
SERVICENAME=xxxxxxxxxx

# Character to echo at each poll. Use PING="" if you don't want
# anything echoed
PING="."

# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
# $PIDFILE contains PID of pppoe-connect script
# $PIDFILE.pppoe contains PID of pppoe process
# $PIDFILE.pppd contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"

# Do you want to use synchronous PPP? "yes" or "no". "yes" is much
# easier on CPU usage, but may not work for you. It is safer to use
# "no", but you may want to experiment with "yes". "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no

# Do you want to clamp the MSS? Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
# "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
# The setting of 1412 is safe for either setup, but uses slightly more
# CPU power.
CLAMPMSS=1412
#CLAMPMSS=no

# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3

# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80

# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE

# Linux kernel-mode plugin for pppd. If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=

# Any extra arguments to pass to pppoe. Normally, use a blank string
# like this:
PPPOE_EXTRA=""

# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"

# Any extra arguments to pass to pppd. Normally, use a blank string
# like this:
PPPD_EXTRA=""


########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"

# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=no
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 11 August 2012, 10:04 GMT
Reason for closing:  Duplicate
Additional comments about closing:  This is a duplicate of  FS#30929 .

Launching the network daemon without configuration launches dhcpcd on all interfaces, which blocks rp-pppoe from functioning.
Comment by Jan de Groot (JGC) - Sunday, 05 August 2012, 21:23 GMT
I guess this is a duplicate of 30929. Can you confirm that killing dhcpcd fixes your problem?
Comment by Jake Parker (tskmgrar) - Monday, 06 August 2012, 10:05 GMT
This aint a duplicate of 30929, in my case, the network daemon is active, and I cant ping it, while in 30929, the networkmanager daemon is active. I think rp-pppoe has its on dhcp client, I dont know about dhcpdcd though. Maybe sudo ifconfig eth0 down might help.

Loading...