From: Thomas Glanzmann <thomas@glanzmann.de>
To: linux-ppp@vger.kernel.org
Subject: Re: pppoe encapsulated udp packets which appear on ethernet disappear between pppoe and ppp0 after p
Date: Tue, 11 Apr 2017 04:34:32 +0000 [thread overview]
Message-ID: <20170411043432.GA20678@glanzmann.de> (raw)
In-Reply-To: <20170410183851.GA4442@glanzmann.de>
Hello Michael,
* Michael Richardson <mcr@sandelman.ca> [2017-04-10 22:02]:
> Are you using openvpn with a 0.0.0.0/0 route?
no, I don't.
> Can you post your routing table when it is working, and when it is
> not?
The routing table is the same:
(generate-03) [~] ip r s
default dev ppp0 scope link
172.17.0.0/24 via 172.17.0.254 dev falkenstein
172.17.0.254 dev falkenstein proto kernel scope link src 192.168.168.1
172.19.0.0/24 via 172.19.0.254 dev eclogicnew
172.19.0.254 dev eclogicnew proto kernel scope link src 192.168.168.1
172.20.0.0/24 via 172.19.0.254 dev eclogicnew
192.168.168.0/24 dev eth0 proto kernel scope link src 192.168.168.1
217.5.98.12 dev ppp0 proto kernel scope link src 217.92.232.50
The real interesting question is, why do perfectly healthy ip/udp packets from
within the pppoe session drop before reaching ppp0? Why does it only happen
after one hangup?
Cheers,
Thomas
next prev parent reply other threads:[~2017-04-11 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 18:38 pppoe encapsulated udp packets which appear on ethernet disappear between pppoe and ppp0 after pppoe Thomas Glanzmann
2017-04-11 4:34 ` Thomas Glanzmann [this message]
2017-04-11 13:36 ` pppoe encapsulated udp packets which appear on ethernet disappear between pppoe and ppp0 after p Michael Richardson
2017-04-11 13:50 ` Thomas Glanzmann
2017-04-11 14:32 ` Thomas Glanzmann
2017-04-11 16:01 ` Thomas Glanzmann
2017-04-12 2:25 ` Thomas Glanzmann
2017-08-02 8:20 ` Thomas Glanzmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170411043432.GA20678@glanzmann.de \
--to=thomas@glanzmann.de \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).