From: Hasso Tepper <hasso@estpak.ee>
To: davids@webmaster.com
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: raw sockets and blocking
Date: Wed, 18 Feb 2004 08:42:18 +0200 [thread overview]
Message-ID: <200402180842.19288.hasso@estpak.ee> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKIEMGKHAA.davids@webmaster.com>
David Schwartz wrote:
> > we havnt yet tested if it becomes writeable again if we put cable
> > back in, however if we detect absence of IFF_RUNNING and hence
> > manually avoid constructing packets to be sent via link-down
> > interfaces, we avoid this problem. However, this leaves us with a
> > race.
>
> I'm not sure I understand what the problem is. If the network
> cable is disconnected, you couldn't usefully send anything if the
> socket was ready anyway.
One raw socket is used to send packets to several interfaces. If only
one of them is down, socket will be blocked as well.
Related problem is that we have no way to detect if vlan interface
goes down. Wouldn't be correct behavior to remove IFF_RUNNING from
all vlan interfaces bound to ethernet interface if this ethernet
interface goes down? There might be similar problems with other
network interfaces.
--
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator
next prev parent reply other threads:[~2004-02-18 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 1:33 raw sockets and blocking Paul Jakma
2004-02-18 5:37 ` David Schwartz
2004-02-18 6:42 ` Hasso Tepper [this message]
2004-02-18 11:42 ` David Schwartz
2004-02-19 6:28 ` Paul Jakma
2004-02-19 7:53 ` Jamie Lokier
2004-02-19 8:34 ` Paul Jakma
2004-02-19 12:40 ` Hasso Tepper
2004-02-19 12:54 ` Paul Jakma
2004-03-22 7:14 ` Hasso Tepper
2004-02-18 8:43 ` Hasso Tepper
2004-02-19 6:20 ` Paul Jakma
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=200402180842.19288.hasso@estpak.ee \
--to=hasso@estpak.ee \
--cc=davids@webmaster.com \
--cc=linux-kernel@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