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 13:50:41 +0000 [thread overview]
Message-ID: <20170411135041.GA30428@glanzmann.de> (raw)
In-Reply-To: <20170410183851.GA4442@glanzmann.de>
Hello Michael,
> It sounds like they aren't part of the correct PPPoE session to me.
> As if the other end is not killing it's PPP session when the new one forms.
wow. You nailed it. Thank you for identifying the root cause. I'll open a call
with German Telekom to fix there ppp endpoint.
(x1) [~/pcaps] tshark -nr eth1.pcap -T fields -e 'pppoe.session_id' | sort -u
0x0000b53b
0x0000b5e0
0x0000b7b3
These are exactly the packages I was missing:
(x1) [~/pcaps] tshark -nr eth1.pcap -Y 'pppoe.session_id = 0x0000b5e0'
2938 12.176318 88.198.215.20 → 217.92.232.50 UDP 118 5000 → 5000 Lenh
5247 21.951571 88.198.215.20 → 217.92.232.50 UDP 118 5000 → 5000 Lenh
5248 21.952077 88.198.215.20 → 217.92.232.50 UDP 118 5000 → 5000 Lenh
5802 31.641323 88.198.215.20 → 217.92.232.50 UDP 118 5000 → 5000 Lenh
5803 31.641807 88.198.215.20 → 217.92.232.50 UDP 118 5000 → 5000 Lenh
Cheers,
Thomas
next prev parent reply other threads:[~2017-04-11 13:50 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 ` pppoe encapsulated udp packets which appear on ethernet disappear between pppoe and ppp0 after p Thomas Glanzmann
2017-04-11 13:36 ` Michael Richardson
2017-04-11 13:50 ` Thomas Glanzmann [this message]
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=20170411135041.GA30428@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).