From: Michael Richardson <mcr@sandelman.ca>
To: Sagar Acharya <sagaracharya@tutanota.com>
Cc: Narasimhan S <simha@multitech.co.in>,
Linux Ppp <linux-ppp@vger.kernel.org>
Subject: Re: Support for udp
Date: Fri, 06 Oct 2023 13:55:07 -0400 [thread overview]
Message-ID: <2673951.1696614907@dyas> (raw)
In-Reply-To: <Ng2dOzz--3-9@tutanota.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
Sagar Acharya <sagaracharya@tutanota.com> wrote:
> So are you saying pppd does not support udp or does it? Thanking you
> Sagar Acharya https://humaaraartha.in/selfdost/selfdost.html
You didn't understand the answer because you didn't actually ask a sensible question.
PPP is a "layer-2"
UDP is a "layer-4"
https://en.wikipedia.org/wiki/OSI_model
https://www.oreilly.com/library/view/internet-core-protocols/1565925726/ch01s02s02.html
There are situations where one might encapsulate PPP packets into UDP
packets. This usually happens in back-hauls of ISP/DSL networks using L2TP.
But, that's not a typical situation for an end-user.
Myself and many others have built commercial BRAS using pppd, and there is
even support in the Linux kernel for efficient encap/decap of L2TP/PPP packets.
https://en.wikipedia.org/wiki/Broadband_remote_access_server
>> pppd works at IP layer. All IP protocols not dependent on broadcast
>> capabilities should work.
>>
>> On 05-10-2023 23:30, Sagar Acharya wrote:
>>
>>> Does pppd support udp? I am able to access tcp but not udp with pppd.
>>> Thanking you Sagar Acharya
>>> https://humaaraartha.in/selfdost/selfdost.html
>>>
>>> Kindly cc me as I am not subscribed.
>>>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
prev parent reply other threads:[~2023-10-06 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:00 Support for udp Sagar Acharya
[not found] ` <b750b194-59cf-4a7b-a7c2-2995e5b0d8dc@multitech.co.in>
2023-10-06 6:21 ` Sagar Acharya
2023-10-06 17:55 ` Michael Richardson [this message]
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=2673951.1696614907@dyas \
--to=mcr@sandelman.ca \
--cc=linux-ppp@vger.kernel.org \
--cc=sagaracharya@tutanota.com \
--cc=simha@multitech.co.in \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).