From: Alejandro Colomar <alx@kernel.org>
To: Oliver Crumrine <ozlinuxc@gmail.com>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ip.7: Add not supported by SOCK_STREAM to socket options
Date: Wed, 6 Mar 2024 11:58:32 +0100 [thread overview]
Message-ID: <ZehMWQ0LkemsTHAC@debian> (raw)
In-Reply-To: <7ubz52rfdl2i76sotvd3s4thv6jvbfao6zct3sywqus2owlvkx@wpbeqqdvipo4>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
Hi Oliver,
On Tue, Mar 05, 2024 at 02:31:48PM -0500, Oliver Crumrine wrote:
> Hi Alex,
> I have attached two programs in the form of C source code below. No
> special compilation options required. To change between the three
> different socket options outlined in my patch, there are two options on
> line 16 and 18 with a comment above them explaining how to use the
> fields.
>
> Here's how to use the programs:
> 0. Make sure you have netcat installed.
> 1. Compile the dgram one.
> 2. Run it.
> 3. Run nc localhost 8888 -u (in a seperate terminal window or tab)
> 4. Type whatever into netcat and press enter
> 5. Observe that there is a control message recieved, and there is a byte
> printed, which is the first byte of the data in the control message.
Can't reproduce this. The terminal running nc(1) isn't printing
anything.
alx@debian:~$ which nc
/usr/bin/nc
alx@debian:~$ which nc | xargs realpath
/usr/bin/nc.openbsd
alx@debian:~$ dpkg -S /bin/nc.openbsd
netcat-openbsd: /bin/nc.openbsd
> 6. You may repeat this for the three different socket options.
> 7. Repeat for the stream one, but use nc localhost 8888 (without the -u)
> for #5.
> 8. Observe that there are no control messages recieved with the stream one,
> and byte is 00, which is the initial value of the variable, before it has
> a value assigned when the control messages (of which there are none) are read.
>
> Thanks,
> Oliver
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-06 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 18:19 [PATCH] ip.7: Add not supported by SOCK_STREAM to socket options Oliver Crumrine
2024-03-04 16:15 ` Alejandro Colomar
2024-03-05 19:31 ` Oliver Crumrine
2024-03-06 10:50 ` Alejandro Colomar
2024-03-06 10:58 ` Alejandro Colomar [this message]
2024-03-06 13:02 ` Oliver Crumrine
2024-03-06 13:12 ` Alejandro Colomar
[not found] ` <CAK1VsR3MsyphK+=rA7XcEigiSd6J_-QsVW+8hH1fU9xmRY3nGQ@mail.gmail.com>
2024-03-13 18:27 ` Oliver Crumrine
2024-03-13 22:35 ` Alejandro Colomar
2024-03-16 19:33 ` Alejandro Colomar
2024-03-16 18:41 ` Oliver Crumrine
2024-03-17 2:02 ` Alejandro Colomar
2024-03-17 9:02 ` Oliver Crumrine
2024-03-17 13:55 ` Alejandro Colomar
[not found] ` <hxkixsi6uymkjmt4ughda2xmh6guzcaccrjbvsuasndyuvq5rz@36oqfaepfiql>
2024-03-17 15:17 ` Alejandro Colomar
2024-03-17 11:31 ` Peter Seiderer
2024-03-17 18:27 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2024-03-17 13:55 Oliver Crumrine
2024-03-17 18:28 ` Alejandro Colomar
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=ZehMWQ0LkemsTHAC@debian \
--to=alx@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=ozlinuxc@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.