public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hasso Tepper <hasso@estpak.ee>
To: Paul Jakma <paul@clubi.ie>
Cc: Jamie Lokier <jamie@shareable.org>,
	David Schwartz <davids@webmaster.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Quagga Dev <quagga-dev@lists.quagga.net>
Subject: Re: raw sockets and blocking
Date: Mon, 22 Mar 2004 09:14:13 +0200	[thread overview]
Message-ID: <200403220914.13676.hasso@estpak.ee> (raw)
In-Reply-To: <Pine.LNX.4.58.0402191252010.25392@fogarty.jakma.org>

Paul Jakma wrote:
> On Thu, 19 Feb 2004, Hasso Tepper wrote:
> > And maybe it makes sense to mention that all packets ospf daemon
> > sends to actually down ethernet interface are multicast packets.
>
> nearly all. unicast packets are sent too.

Hello's in broadcast network are multicast. Problem is solved now for 
me, btw. It appears to be bug in e100 driver in 2.4.x.

I can't reproduce it any more with e100 development driver (from 
http://sf.net/projects/e1000/). And I can't it reproduce it with 
forcing network to non-broadcast either (in this case unicast hello's 
are sent).

So it's multicast problem with e100 2.x driver.


-- 
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator

  reply	other threads:[~2004-03-22  7:14 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
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 [this message]
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=200403220914.13676.hasso@estpak.ee \
    --to=hasso@estpak.ee \
    --cc=davids@webmaster.com \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    --cc=quagga-dev@lists.quagga.net \
    /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