From: Hugo Tyson <hmt@cygnus.co.uk>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] UDP on EDB7211
Date: Tue, 04 Jul 2000 09:00:00 -0000 [thread overview]
Message-ID: <ptlmzh7uxf.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <17455.962722360@raven.ravenbrook.com>
Nick Barnes <Nick.Barnes@pobox.com> writes:
> Has anyone had any success using UDP in the beta TCP/IP stack?
> connect() is OK but then sendto() always fails. Has anyone had any
> success with these?
Hi Nick,
AIUI, the SNMP server uses UDP (ie. SOCK_DGRAM as opposed to SOCK_STREAM),
and that's all cool. But it doesn't use connect(), it uses a global
listener via bind(), if that's the right words. Ditto the tftp_client,
that binds to a specific address rather than broadcast. So it works more
than somewhat.
Connect's man page sez that in the UDP case, it only selects a peer to
connect to rather than a socket - UDP being connectionless - might that be
a source of confusion? I guess that means you *must* sendto() the same
peer you connect()ed to?
Anyway, we've used UDP a lot with bind() but not with connect().
HTH,
- Huge
prev parent reply other threads:[~2000-07-04 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 7:52 Nick Barnes
2000-07-04 9:00 ` Hugo Tyson [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=ptlmzh7uxf.fsf@masala.cygnus.co.uk \
--to=hmt@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.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 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).