public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: joseph.bueno@trader.com
To: Justin Guyett <justin@soze.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tulip driver still broken
Date: Thu, 02 Aug 2001 09:35:32 +0200	[thread overview]
Message-ID: <3B6902C4.9B975BEE@trader.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108011354120.8520-100000@kobayashi.soze.net>

Justin Guyett wrote:
> 
> On Wed, 1 Aug 2001 joseph.bueno@trader.com wrote:
> 
> > I am currently using a Xircom Ethernet adapter (tulip_cb module) with a
> > 2.4.5 kernel.
> >
> > The only way I have found to make it work is to turn on promiscuous mode
> > (with 'tcpdump -i eth0 -n > /dev/null') after bootup. I can turn it off
> > after a few minutes without problem.
> 
> i saw something like that with a wireless ethernet card, but presumed it
> to be something wrong with WAP+multicast, plus it doesn't happen with new
> card firmware.
> 
> at any rate, this made my card work, and sounds like it would be better
> than running tcpdump and killing it after a few minutes.  the critical
> element in getting things working was getting traffic while the interface
> was in promisc mode (arp replies to wrong mac address maybe?)
> 

That's right.
In fact, I generally start a ping to a remote IP address after bootup
and, if I don't get any response (which is always the case), I start
tcpdump and I do some network activity before stopping it.

> ifconfig ethX promisc
> ping -n -c 5 <pick a remote ip>
> ifconfig ethX -promisc

In fact, I ran tcpdump to check what was going on and, since it "solved"
the problem, I didn't check for a better way to do it.
Obviously, your solution is better.

> 
> if you have no traffic for a few minutes, it might break again.

Hopefully, there is some periodic network activity on my machine (at
least checking of my POP account), so it doesn't break.

> 
> justin

Thanks
--
Joseph Bueno
NetClub/Trader.com

  reply	other threads:[~2001-08-02  7:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 22:19 tulip driver still broken Thomas Zehetbauer
2001-07-30 22:57 ` Joshua Schmidlkofer
2001-07-30 23:09   ` Jeff Garzik
2001-07-30 23:30     ` Michal Jaegermann
2001-08-01 14:36     ` Patrick Cole
2001-07-31 13:23 ` Chris Friesen
2001-07-31 18:00   ` Jeff Garzik
2001-08-01 15:51   ` Ben Greear
2001-08-01 16:45     ` joseph.bueno
2001-08-01 21:14       ` Justin Guyett
2001-08-02  7:35         ` joseph.bueno [this message]
2001-08-01 21:52       ` Jeff Garzik

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=3B6902C4.9B975BEE@trader.com \
    --to=joseph.bueno@trader.com \
    --cc=justin@soze.net \
    --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