Date: Tue, 21 May 1996 10:57:14 +0200 (MET DST) From: grog@lemis.de (Greg Lehey) To: jrclark@felix.iupui.edu (John Clark) Cc: questions@freebsd.org Subject: Re: 3Com Support? -- NOT Message-ID: <199605210857.KAA23810@allegro.lemis.de> In-Reply-To: <2.2.32.19960519140200.002d7ea8@felix.iupui.edu> from "John Clark" at May 19, 96 01:57:12 pm
next in thread | previous in thread | raw e-mail | index | archive | help
John Clark writes:
>
> FreeBSD Group,
>
> I was hoping someone could help me with my 3c509 woes. I have read many
> many questions about the 3c509 card, with no good answers for my problem.
> The largest source of problems seems to be those who are having irq trouble.
> This is not my trouble as I have reconfigured, and recompiled at irq's 5, 7,
> and 10 (orig) with no joy.
Well, as other people have already answered, the board works for most
people. I have a couple here, running on 2.2-current and 2.1-release,
and have no problems.
> My system boots and recognizes everything ok, but hangs when adding the
> default route. Any ideas?
Can you ping to a numeric IP address? If you have to make a name
server lookup to another machine in order to process the 'route add'
command, it will hang.
If you can't ping another machine, you should at least try to monitor
network traffic from another machine.
Try this:
1. Configure and test the board under DOS (Diagnostic Operational
Support, a product of a company called Microsoft). Choose IRQ 10
if you don't have anything else on it.
2. At bootup time, reply '-c' to the 'Boot:' prompt, and set the
config for ep0 to match what you set in step 1. This procedure is
described starting on page 77 of "Installing and Running FreeBSD".
3. When the system is up, enter
# ifconfig ep0 <ip-address>
# ping <other-address>
Make sure both addresses are numeric IP addresses. If this works,
go to step 5.
4. Otherwise, on another machine with BPF support, try:
tcpdump ether host 0:0:c0:2:b9:e
(substitute the ethernet address of your board for the
0:0:c0:2:b9:e).
If you don't see the pings going out, then you do have a problem.
If you see them going out, but not going back, then your problem
is in the net, not with the board. If you see them going out and
going back, you have a problem. We'll discuss them if they
happen.
5. Try 'route add default <ip-address>', again with a numeric IP
address. I can't really see how this can fail, however...
I'm currently working on a book about FreeBSD networking, so I'd be
interested to see if this helps. If it doesn't, let me know and we'll
follow it further.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605210857.KAA23810>