ck | 27 Mar 22:42 2015

PADO answer incoming wrong VLAN since new linecard

Hi There!
I've been running pppd for years with my PPPoE connection. That was 
working perfectly fine until yesterday.
I am not able to connect via PPPoE anymore, because after I am sending 
an PADI, the received PADO is incoming on a wrong VLAN.

That happend, after the linecard outside has been changed by my ISP. It 
was an Infineon 11.5.3, when it was working and stopped working, after 
it has been changed to a Broadcom 164.34.

Basically, my setup is, that I've to connect via vlan7. I am sending my 
requests on that specific vlan7. But now, after that, I am getting the 
PADO on vlan8, which now causes the problem, that pppd thinks, that 
there is no answer to the PADI request.

That also seems not to be a distribution problem. I am using Gentoo, but 
I've tried also Ubuntu and OpenSUSE. All distributions showed the same 
error. I've tried pppd 2.4.5, 2.4.6 and 2.4.7.

If I am using a BSD-Distribution (like pfSense) or an external hardware 
router (like Fritz!Box), those are perfectly working fine. Those systems 
can connect via PPPoE, the PADO answer is getting there on the correct 
VLAN back (7).

So, what is going? Why does Linux PPP seems to have problems, where 
other systems do not have a problem?
Can anybody help? After my tests, I am just thinking, that there is some 
sort if a bug.. I mean, if was working for years fine and now stopped?

(Continue reading) | 12 Mar 12:49 2015



Respond to my personal email;  mrs.zhangxiao1962 <at> outlook.

Yours Sincerely.
Mrs. Zhang Xiao (Accounts book Keeper)
Steel Company Limited
396 Nan Zhong Hua Lu, Tie Dong District Anshan, 
Liaoning 114021, China.

To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at>
More majordomo info at

Simon Farnsworth | 1 Mar 11:54 2015

[PATCH net-next v2] pppoe: Use workqueue to die properly when a PADT is received

When a PADT frame is received, the socket may not be in a good state to
close down the PPP interface. The current implementation handles this by
simply blocking all further PPP traffic, and hoping that the lack of traffic
will trigger the user to investigate.

Use schedule_work to get to a process context from which we clear down the
PPP interface, in a fashion analogous to hangup on a TTY-based PPP
interface. This causes pppd to disconnect immediately, and allows tools to
take immediate corrective action.

Note that pppd's plugin has code in it to disable the session
when it disconnects; however, as a consequence of this patch, the session is
already disabled before is asked to disable the session. The
result is a harmless error message:

Failed to disconnect PPPoE socket: 114 Operation already in progress

This message is safe to ignore, as long as the error is 114 Operation
already in progress; in that specific case, it means that the PPPoE session
has already been disabled before pppd tried to disable it.

Signed-off-by: Simon Farnsworth <simon <at>>
Tested-by: Dan Williams <dcbw <at>>
Tested-by: Christoph Schulz <develop <at>>

Changes from v1:

 * Amend commit message to tell people about the harmless error from pppd

(Continue reading)

Alan | 19 Feb 22:39 2015

[PATCH] ppp_synctty: remove unneeded NULL check

Fix a random whine found by coverity. Had it been NULL it would have
showered us with oopses long before.

Signed-off-by: Alan Cox <alan <at>>
 drivers/net/ppp/ppp_synctty.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 925d3e2..b5592b8 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
 <at>  <at>  -549,7 +549,7  <at>  <at>  ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)

 	ap->last_xmit = jiffies;

-	if (skb && ap->flags & SC_LOG_OUTPKT)
+	if (ap->flags & SC_LOG_OUTPKT)
 		ppp_print_buffer ("send buffer", skb->data, skb->len);

 	return skb;

To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at>
More majordomo info at

Anljaken . | 10 Feb 13:02 2015

Default Route Problem with pppd


I have a default route problem with a dialup xDSL ppp interface. Even
if i give defaultroute option to pppd service, default route is not
added. I do not have another default route. Running on debug mode, i
can not see any problem at logs.

PPP Version : ppp-2.4.4-2.el5
OS : Centos5
Linux kernel : 3.4.103-2
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at>
More majordomo info at

Easy Finance | 31 Jan 13:57 2015


Good & Bad Credit Loan With No Credit Check. Email us amount needed & duration.

To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at>
More majordomo info at

Lee Essen | 26 Jan 17:29 2015

multiple pppd instances -- resolv.conf challenges and suggested improvement


I’ve hit a bit of a challenge with the way that pppd creates the resolv.conf file.

Basically if you want to get dns servers from the other side you need ‘usepeerdns’ set.

If you set ‘usepeerdns’ then pppd will create resolve.conf (/etc/ppp/resolv.conf as standard,
although changed in many dists)

The challenge is that if you have two pppd’s running, both getting DNS entries, then there is no way to
specify a different file (so that you can be clever later) and the given file will be overwritten by the most
recent connection. Also, with buiildroot builds the path is set to /etc/resolv.conf which causes even
more of a problem since you can’t ‘usepeerdns’ without making your system use the provided resolvers.

It does feel wrong that just about every other aspect of pppd supports isolated multiple connections, but
the resolv.conf file is a single path that will get overwritten by the last connection, and then, of
course, if that connection drops the file is then incorrect!

Could I suggest a ‘noresolv’ config option that simply suppresses the creation of the resolve.conf
file?  It’s a very simple patch, has no compatibility issues with existing configuration and makes it
possible to use ppp-up scripts to do the heavy lifting with no conflicting resolv.conf creations. This
would also allow buildroot users to avoid the “forced use of peer dns”.

(The other option would be to have a configurable path for resolv.conf)



diff -Naur pppd-orig/pppd/ipcp.c pppd-2.4.7/pppd/ipcp.c
(Continue reading)

Matt Dooner | 23 Jan 12:56 2015

pppd hangup only when traffic sent over connection


I'm experiencing an issue where pppd hangs up, but only when traffic
is sent over the connection. The connection is stable if it is idle,
but soon after any traffic is sent over the connection pppd hangs up.
For example, 15-30 pings or a few lines into a telnet session kills
the connection. I suspect this is the result of a lack of support for
a Link Quality Report (which is Confreq'd by the target).

As you can see in the debug about below if-down is started after the
"rcvd [LCP ConfReq id=0xf0 <mru 400> <quality lqr 00 00 01 2c> <magic
0xc0a80ea5> <pcomp> <accomp>]". This ConfReq occured after 17
successful pings over the link, and the link went down after the
ConfReq. Is this expected behaviour?

Thanks in advance,

using channel 14
Using interface ppp0
Connect: ppp0 <--> /dev/ttyO1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ad4ff1a> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0xd5 <mru 400> <quality lqr 00 00 01 2c> <magic
0xc0a80ea5> <pcomp> <accomp>]
sent [LCP ConfRej id=0xd5 <quality lqr 00 00 01 2c>]
rcvd [LCP ConfRej id=0x1 <asyncmap 0x0>]
sent [LCP ConfReq id=0x2 <magic 0x9ad4ff1a> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0xd6 <mru 400> <magic 0xc0a80ea5> <pcomp> <accomp>]
sent [LCP ConfAck id=0xd6 <mru 400> <magic 0xc0a80ea5> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x2 <magic 0x9ad4ff1a> <pcomp> <accomp>]
(Continue reading)

"Antonio Viñal" | 16 Jan 21:56 2015

Please respond!!!

Please respond!!!
Hello friend!

I would like to contact you personally for an important proposal that
could of interest to you.
I send this email only to know if this email address is functional.
I have something very important to discuss with you. Contact me for
details by:  Email: fernrodyup12 <at> with your direct contacts.

Kind regards.
Antonio Viñal.

To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at>
More majordomo info at

Matthias-Christian Ott | 13 Jan 18:33 2015

ppp_async: ioctl to set MTU needed

Some months ago I filed the following bug report (with some sentences
corrected) on the Kernel Bug Tracker but have received no reaction
reaction so far:

Summary: ppp_async: ioctl to set MTU needed

The MTU of a channel of a Multilink PPP link is set from the MRU of a
Configure-Ack LCP packet. However, just because the is able to receive
packets of a certain size it doesn't mean that the link or the sender
are able to transmit packets of that size, so the received MTU of the
channel should not be set to the MRU of the peer.

A practical example is PPP encapsulated in GRE or L2TP over IPv6
(without fragmentation). Peer A sets its MRU to the link MTU minus
maximum IP header length minus GRE/L2TP header length to be able to
receive packets of maximum length over PPP. Peer B connects to peer A
and the maximum payload size, which is derived from the Path MTU, of the
tunnel between peers A and B is lower than the MRU of peer A. If peer B
sends a packet P smaller than the MRU of peer A and larger than the
maximum payload size of the IP packet encapsulating P, it will exceed
the Path MTU and thus will be rejected and never arrive at peer A. Such
scenario is common for VPNs that use PPP or to transport PPP sessions of
broadband/Internet subscribers (e.g. if one ISP manages the physical
network and another ISP provides Internet access and is the endpoint of
the PPP session that runs over the physical network and the PPP session
is transported over IPv6). IPv4 was able to fragment IP packets larger
than the Path MTU, so setting the MTU to the MRU of peer a worked. With
IPv6 (without fragmentation) this no longer works.

As a workaround I patched pppd and sent a Configure-Nak with the correct
(Continue reading)

MR. MORGAN W. THABO | 12 Jan 19:09 2015





Attachment (Fund Transfer.doc): application/msword, 43 KiB