NetBSD Problem Report #13460
Received: (qmail 878 invoked from network); 13 Jul 2001 22:22:41 -0000
Message-Id: <3B4F7577.24349006@analysisandsolutions.com>
Date: Fri, 13 Jul 2001 18:25:59 -0400
From: Analysis and Solutions <info@analysisandsolutions.com>
To: gnats-bugs@gnats.netbsd.org
Subject: DHCP via DP83815 chip: ip length disagrees with bytes received
>Number: 13460
>Category: kern
>Synopsis: DHCP & DP83815 chip: ip length disagrees with bytes received
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jul 13 22:23:00 +0000 2001
>Closed-Date:
>Last-Modified: Sun Apr 15 21:45:25 +0000 2012
>Originator: Dan Convissor
>Release: NetBSD 1.5.1
>Organization:
Analysis and Solutions
>Environment:
System: NetBSD base.nyc.rr.com 1.5.1 NetBSD 1.5.1 (GENERIC) #56: Mon Jul 2 15:54:23 CEST 2001 he@nsa.uninett.no:/usr/src/sys/arch/i386/compile/GENERIC i386
Machine IBM 300GL, 6591-34U
Processor Pentium II 266
RAM 256 mb
BIOS Revision NZJT42A
Network Card Netgear FA312 10/100 BaseT (PCI) (Chip: DP83815) (sip)
Network RoadRunner Cable Service
Cable Modem Toshiba PCX1100U
PCI Controller Intel FW82371AB F808YB11 SL23P
IDE Controller ATA-33 PCI 32-bit busmaster on planar
Video Control. Cirrus Logic GD5465-HC-C
Sound Card Creative Technologies CT2980 (ISA) (Chip: CT2502-SDQ)
Printer HP OfficeJet 600
>Description:
I install NetBSD. Then tried "dhclient sip0". Worked first time. Was
able to ping and ftp the outside world. Upon rebooting, dhclient obtained
an IP address, but while doing so it produced the following error:
DHCPREQUEST on sip0 to 255.255.255.255 port 67
ip length 328 disagrees with bytes received 330.
accepting packet with data after udp payload.
Pinging my "bound to" IP address worked, but it took an unusually
long time for the results to be displayed. Pinging the IP address
of the assigned name servers or any other IP address returned
"no route to host" after a long delay.
I considered the possibility that files were modified and tripped
up the dhclient. So, I reinstalled, then backed up all of the
/etc files. Tried dhclient. Worked. Shutdown, restart, then do:
rm -rf /etc
cp -RpL /etc.orig /etc
rm /var/db/dhclient.leases
rm /var/run/dhclient.pid
dhclient sip0
The same problem arose.
I've tried SEVERAL reinstalls. This pattern has repeated itself
on nearly every try. But, not EVERY try. On one reinstall, the
error happened the first time I installed. On a different install,
things didn't choke up till the second reboot, but unchoked for
several reboots, but eventually locked up for the next five reboots
before I gave up.
From my experimentation and reading some pages on the net, I stronlgy
suspect the network card driver. The sip driver for the DP83815 driver
was updated in NetBSD 1.5.1, but doesn't seem to have been fully fixed.
Here are some pages that had interesting leads:
http://marc.theaimsgroup.com/?l=dhcp-server&m=99065029016883&w=2
http://marc.theaimsgroup.com/?l=dhcp-server&m=96266206206593&w=2
http://www.scyld.com/pipermail/realtek/2000-October/000658.html
I have had the same problem in 1.5.1_BETA2, 1.5.1 and even
the -current from 28 June.
The card works fine under Windows NT.
>How-To-Repeat:
Described above.
>Fix:
Reinstall. Most times, reinstalling solves the problem.
But the problem is only solved for one try. Also, this
didn't work 100% of the time.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: bouyer
State-Changed-When: Thu Feb 28 08:17:02 PST 2002
State-Changed-Why:
Hi,
can you try the last 1.5.3_ALPHA snapshot ?
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Analysis and Solutions <danielc@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Thu, 7 Mar 2002 20:34:31 +0100
On Thu, Mar 07, 2002 at 02:30:13PM -0500, Analysis and Solutions wrote:
> Howdy:
>
> I reinstalled 20020205-1.5.3_ALPHA just now. Everything went fine
> until I tried:
>
> dhclient sip0
>
> Which resulted in the following output...
>
> Internet Software Consortium DHCP Client V3.0rc10
> ... snip ...
> Listening on BPF/sip0/00:a0:cc:a1:86:27
> Sending on BPF/sip0/00:a0:cc:a1:86:27
> Sending on Socket/fallback
>
> kernel: page fault trap, code=0
> Stopped at bpf_mtap+0x14: add1 0xc(%eax),%esi
>
>
> So, no love, yet. I'm more than willing to help, but I don't know what to
> do. If there's something beside just testing what y'all write, please let me
> know. But if you do, you'll need to break things down to simple step by step
> instructions (or point me to the appropriate documentation/tutorials that
> have such).
At this point, please type 'tr' and write down what's there.
--
Manuel Bouyer <bouyer@antioche.eu.org>
--
From: Analysis and Solutions <danielc@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Thu, 07 Mar 2002 16:05:09 -0500
Hi:
> At this point, please type 'tr' and write down what's there.
YEOW!!!! That's a lot of output! The process of writing it down and retype
it is quite error prone, let alone an inefficient use of time. I tried
outputting it to a file via "tr > foo" but that didn't work. Is there a way
to dump the output to a file? If not, I'm sure all of you have long
realized, there needs to be... Be that as it may, here's the output...
bpf_mtap(c0a96de0,c0aa0038) at bpf_mtap+0x14
sip_start(c0aa0038) at sip_start+0x522
gcc2_compiled.(c0aa0038,c0b9b200,d25e2d88,0) at gcc2_compiled.+0x9c3
nd6_output(c0aa0038,c0aa0038,c0b9b200,d25e2d88,0) at nd6_output+0x2a5
might be a "c" --^
ip6_output(c0b9c200,0,d25e2d84,1,d25e2df8) at ip6_output+0xbf7
nd6_ns_output(c0aa0038,0,c0b8f540,0,1) at nd6_ns_output+0x44c
nd6_dad_ns_olutput(c0b90180,c0b8f500,7fffffff,c0b8f500,c0265bf0)
at nd6_dad_ns_output+0x31
nd6_dad_timer(c0b8f500) at nd6_dad_timer+0xf3
softclock(c0a96c20,d25d1650,d25d1650,4b89,d25e2e88) at softclock+0x121
hardclock(d25e2e94,d25e2e90,c010103c,d25e2e94,0) at hardclock+0x507
clockintr(d25e2e94) at clockintr+0xb
Xintr0() at Xintr0+0x78
--- interrupt ---
idle(d25d1650) at idle+0x1c
bpendtsleep(c0573300,28,c04308e6,0,0) at bpendtsleep
sched_sync(d25d1650) at sched_sync+0x203
I'm glad I printed that out, rebooted, recreated the error and debug output.
Found several mistranspositions and typos.
Enjoy,
--Dan
--
PHP scripts that make your job easier
http://www.analysisandsolutions.com/code/
SQL Solution | Layout Solution | Form Solution
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
4015 7 Ave, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Analysis and Solutions <danielc@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Thu, 7 Mar 2002 22:09:03 +0100
On Thu, Mar 07, 2002 at 04:05:09PM -0500, Analysis and Solutions wrote:
> Hi:
>
> > At this point, please type 'tr' and write down what's there.
>
> YEOW!!!! That's a lot of output! The process of writing it down and retype
> it is quite error prone, let alone an inefficient use of time. I tried
> outputting it to a file via "tr > foo" but that didn't work. Is there a way
> to dump the output to a file? If not, I'm sure all of you have long
> realized, there needs to be... Be that as it may, here's the output...
Well, not easy to write to file: when running the debugger the kernel can't
do much else.
--
Manuel Bouyer <bouyer@antioche.eu.org>
--
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Analysis and Solutions <danielc@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Thu, 7 Mar 2002 23:06:52 +0100
On Thu, Mar 07, 2002 at 04:05:09PM -0500, Analysis and Solutions wrote:
> Hi:
>
> > At this point, please type 'tr' and write down what's there.
>
> YEOW!!!! That's a lot of output! The process of writing it down and retype
> it is quite error prone, let alone an inefficient use of time. I tried
OK, but it allowed me to find the bug :)
There is an uninitialised pointer used. Can you try this patch:
Index: if_sip.c
===================================================================
RCS file: /cvsroot/syssrc/sys/dev/pci/if_sip.c,v
retrieving revision 1.11.4.6
diff -u -r1.11.4.6 if_sip.c
--- if_sip.c 2001/10/27 17:55:47 1.11.4.6
+++ if_sip.c 2002/03/07 22:02:43
@@ -691,6 +691,7 @@
if (m0 == NULL)
break;
+ m = NULL;
dmamap = txs->txs_dmamap;
/*
Alternatively you can grab:
ftp://antioche.lip6.fr/pub/bouyer/tmp/netbsd-i386-1.5.3Z_ALPHA.gz
--
Manuel Bouyer <bouyer@antioche.eu.org>
--
From: Analysis and Solutions <danielc@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Thu, 07 Mar 2002 17:58:37 -0500
Hi:
> ftp://antioche.lip6.fr/pub/bouyer/tmp/netbsd-i386-1.5.3Z_ALPHA.gz
Downloaded. Unzipped. Renamed old netbsd kernel file. Moved this new one
in. Hasn't solved the bug initially reported...
dhclient sip0
Listening on BPF/sip0/00:a0:cc:a1:86:27
Sending on BPF/sip0/00:a0:cc:a1:86:27
Sending on Socket/fallback
DHCPDISCOVER on sip0 to 255.255.255.255 port 67
ip length 352 disagrees with bytes received 354.
accepting packet with data after udp payload
DHCPACK from 24.29.99.65
New Host Name: dhcp-26-14
New Network Number: 24.29.148.0
New Broadcast Address: 255.255.255.255
Bound to 24.29.149.12 -- renewal in 40168 seconds.
Thanks,
--Dan
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: Analysis and Solutions <danielc@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 10:34:32 +0100
On Thu, Mar 07, 2002 at 05:58:37PM -0500, Analysis and Solutions wrote:
> Hi:
>
> > ftp://antioche.lip6.fr/pub/bouyer/tmp/netbsd-i386-1.5.3Z_ALPHA.gz
>
> Downloaded. Unzipped. Renamed old netbsd kernel file. Moved this new one
> in. Hasn't solved the bug initially reported...
>
> dhclient sip0
>
> Listening on BPF/sip0/00:a0:cc:a1:86:27
> Sending on BPF/sip0/00:a0:cc:a1:86:27
> Sending on Socket/fallback
> DHCPDISCOVER on sip0 to 255.255.255.255 port 67
> ip length 352 disagrees with bytes received 354.
> accepting packet with data after udp payload
> DHCPACK from 24.29.99.65
> New Host Name: dhcp-26-14
> New Network Number: 24.29.148.0
> New Broadcast Address: 255.255.255.255
> Bound to 24.29.149.12 -- renewal in 40168 seconds.
Can you ping outside hosts ? What does 'ifconfig -a' say now about this
interface ?
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
--
From: Analysis & Solutions <info@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 11:05:16 -0500
> Can you ping outside hosts ? What does 'ifconfig -a' say now about this
> interface ?
pinging results in "no route to host."
ifconfig -a says...
sip0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:a0:cc:a1:86:27
media: Ethernet autoselect (10baseT)
status: active
inet 24.29.149.12 netmask 0xfffffc00 broadcast 255.255.255.255
inet6 fe80::2a0:ccff:fea1:8627%sip0 prefixlen 64 scopeid 0x1
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33228
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet6 ::1 prefixlen 128
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
ppp1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
strip0: flags=0<> mtu 1100
strip1: flags=0<> mtu 1100
tun0: flags=10<POINTOPOINT> mtu 1500
tun1: flags=10<POINTOPOINT> mtu 1500
gre0: flags=8010<POINTOPOINT,MULTICAST> mtu 1450
gre1: flags=8010<POINTOPOINT,MULTICAST> mtu 1450
ipip0: flags=8010<POINTOPOINT,MULTICAST>
ipip1: flags=8010<POINTOPOINT,MULTICAST>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
Enjoy,
--Dan
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: Analysis & Solutions <info@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 17:10:00 +0100
On Fri, Mar 08, 2002 at 11:05:16AM -0500, Analysis & Solutions wrote:
> > Can you ping outside hosts ? What does 'ifconfig -a' say now about this
> > interface ?
>
> pinging results in "no route to host."
>
> ifconfig -a says...
>
> sip0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> address: 00:a0:cc:a1:86:27
> media: Ethernet autoselect (10baseT)
> status: active
> inet 24.29.149.12 netmask 0xfffffc00 broadcast 255.255.255.255
Hum the broadcast is wrong. This time I suspect the dhcp server sent something
wrong.
Can you try to boot single user (boot -s) and configure the interface
by hand:
ifconfig sip0 inet 24.29.149.12 netmask 0xfffffc00
and see how the broadcast is configured.
Also try to ping some other host on the network.
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
--
From: Analysis & Solutions <info@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 11:18:13 -0500
> Hum the broadcast is wrong. This time I suspect the dhcp server sent
> something wrong.
I really doubt it. These are the same exact problems I've been having
the whole time. The DHCP server works fine under various windows OS's.
I bet it would work fine if I had a network card which used a different
NetBSD driver. I blew several weeks trying all sorts of different
tricks hoping that THIS TIME, it'd would work. Finally boiled down to
some kind people pointing out the bug in the driver.
> Can you try to boot single user (boot -s) and configure the interface
> by hand:
> ifconfig sip0 inet 24.29.149.12 netmask 0xfffffc00
> and see how the broadcast is configured.
Before I try this, I want to make sure I understand what you want me to
do. Should I do the ifconfig and then "dhclient sip0," or the other way
around, or don't do "dhclient sip0" at all?
Thanks!
--Dan
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: Analysis & Solutions <info@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 17:24:12 +0100
On Fri, Mar 08, 2002 at 11:18:13AM -0500, Analysis & Solutions wrote:
> > Hum the broadcast is wrong. This time I suspect the dhcp server sent
> > something wrong.
>
> I really doubt it. These are the same exact problems I've been having
> the whole time. The DHCP server works fine under various windows OS's.
> I bet it would work fine if I had a network card which used a different
> NetBSD driver. I blew several weeks trying all sorts of different
> tricks hoping that THIS TIME, it'd would work. Finally boiled down to
> some kind people pointing out the bug in the driver.
Well, I could be wrong but I don't think the sip driver messes with the
broadcast. There is a common code used by all ethernet drivers for this.
>
>
> > Can you try to boot single user (boot -s) and configure the interface
> > by hand:
> > ifconfig sip0 inet 24.29.149.12 netmask 0xfffffc00
> > and see how the broadcast is configured.
>
> Before I try this, I want to make sure I understand what you want me to
> do. Should I do the ifconfig and then "dhclient sip0," or the other way
> around, or don't do "dhclient sip0" at all?
No dhclient at all.
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
--
From: Analysis & Solutions <danielc@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
Cc: Analysis & Solutions <info@analysisandsolutions.com>,
gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 11:53:16 -0500
Manuel:
> Can you try to boot single user (boot -s) and configure the interface
> by hand:
> ifconfig sip0 inet 24.29.149.12 netmask 0xfffffc00
> and see how the broadcast is configured.
inet 24.29.149.12 netmask 0xfffffc00 broadcast 24.l29.151.255
But, pinging still renders no route to host.
--Dan
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: Analysis & Solutions <danielc@analysisandsolutions.com>
Cc: Analysis & Solutions <info@analysisandsolutions.com>,
gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 18:06:54 +0100
On Fri, Mar 08, 2002 at 11:53:16AM -0500, Analysis & Solutions wrote:
> Manuel:
>
> > Can you try to boot single user (boot -s) and configure the interface
> > by hand:
> > ifconfig sip0 inet 24.29.149.12 netmask 0xfffffc00
> > and see how the broadcast is configured.
>
> inet 24.29.149.12 netmask 0xfffffc00 broadcast 24.l29.151.255
OK, this looks good now.
Re-reading the audit-trail, I noticed this in your dhclient output:
New Broadcast Address: 255.255.255.255
So the server really gave 255.255.255.255 this broadcast address to the
client. This doesn't look correct but it may not be a problem; this broadcast
address should always work (this is the one used by the dhcp protocol for
hosts which don't have an address yet, for example).
>
> But, pinging still renders no route to host.
Just to make sure: you tried pinging a host on the local network, rigth ?
With just an ifconfig, no gateway is configured.
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
--
From: Analysis & Solutions <info@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
Cc: Analysis & Solutions <danielc@analysisandsolutions.com>,
gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Fri, 8 Mar 2002 12:56:11 -0500
Manuel:
> > inet 24.29.149.12 netmask 0xfffffc00 broadcast 24.l29.151.255
>
> OK, this looks good now.
> Re-reading the audit-trail, I noticed this in your dhclient output:
> New Broadcast Address: 255.255.255.255
>
> So the server really gave 255.255.255.255 this broadcast address to the
> client. This doesn't look correct but it may not be a problem; this broadcast
> address should always work (this is the one used by the dhcp protocol for
> hosts which don't have an address yet, for example).
You say this looks good now. Um, want to clue me in as to why? :)
I don't feel any closer to resolving the problem of not being able to
get on the net using NetBSD and my FA312 network card. Perhaps the
following output from Windows NT will help you...
ipconfig /all
Windows NT IP Configuration
Host Name . . . . . . . . . : base.nyc.rr.com
DNS Servers . . . . . . . . : 24.29.99.81
24.29.99.82
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
Ethernet adapter FA312ND45:
Description . . . . . . . . : NETGEAR FA312 Fast Ethernet PCI
Adapter
Physical Address. . . . . . : 00-A0-CC-A1-86-27
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 24.29.149.23
Subnet Mask . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . : 24.29.148.1
DHCP Server . . . . . . . . : 24.29.99.65
Lease Obtained. . . . . . . : Friday, March 08, 2002
11:49:42 AM
Lease Expires . . . . . . . : Saturday, March 09, 2002
9:48:37 AM
> > But, pinging still renders no route to host.
>
> Just to make sure: you tried pinging a host on the local network, rigth ?
> With just an ifconfig, no gateway is configured.
No. I tried something across the internet. I just rebooted and tried
this again on some local IP's. Pinging the broadcast address that
sohwed up, 24.29.151.255, worked fine, with quick response. But,
pinging my DNS server, 24.29.99.36, came back with "no route to host,"
but it did so quickly.
Now, when I rebooted into multiuser mode and ran "dhclient sip0,"
pinging to the DNS 24.29.99.36 also came back with "no route to host,"
_BUT_ it took a LONG time for it to say that. Similarly, it took a long
time to ping my IP, 24.29.149.12, even though the ping succeeded.
Perhaps this provides some clues.
Thanks,
--Dan
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Analysis & Solutions <info@analysisandsolutions.com>
Cc: Analysis & Solutions <danielc@analysisandsolutions.com>,
gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Sat, 9 Mar 2002 15:11:11 +0100
On Fri, Mar 08, 2002 at 12:56:11PM -0500, Analysis & Solutions wrote:
> Manuel:
>
> > > inet 24.29.149.12 netmask 0xfffffc00 broadcast 24.l29.151.255
> >
> > OK, this looks good now.
> > Re-reading the audit-trail, I noticed this in your dhclient output:
> > New Broadcast Address: 255.255.255.255
> >
> > So the server really gave 255.255.255.255 this broadcast address to the
> > client. This doesn't look correct but it may not be a problem; this broadcast
> > address should always work (this is the one used by the dhcp protocol for
> > hosts which don't have an address yet, for example).
>
> You say this looks good now. Um, want to clue me in as to why? :)
In the ifconfig output: the broadcast address is 24.l29.151.255, not
255.255.255.255 (the broadcast address shall be <addr> | ~<netmask>,
24.29.149.12 = 0x181d950c; so <addr> | ~<netmask> = 0x181d97ff;
0x181d97ff = 24.29.151.25)
>
> I don't feel any closer to resolving the problem of not being able to
> get on the net using NetBSD and my FA312 network card. Perhaps the
> following output from Windows NT will help you...
>
> ipconfig /all
>
> Windows NT IP Configuration
>
> Host Name . . . . . . . . . : base.nyc.rr.com
> DNS Servers . . . . . . . . : 24.29.99.81
> 24.29.99.82
> Node Type . . . . . . . . . : Broadcast
> NetBIOS Scope ID. . . . . . :
> IP Routing Enabled. . . . . : No
> WINS Proxy Enabled. . . . . : No
> NetBIOS Resolution Uses DNS : No
>
> Ethernet adapter FA312ND45:
>
> Description . . . . . . . . : NETGEAR FA312 Fast Ethernet PCI
> Adapter
> Physical Address. . . . . . : 00-A0-CC-A1-86-27
> DHCP Enabled. . . . . . . . : Yes
> IP Address. . . . . . . . . : 24.29.149.23
> Subnet Mask . . . . . . . . : 255.255.252.0
> Default Gateway . . . . . . : 24.29.148.1
> DHCP Server . . . . . . . . : 24.29.99.65
> Lease Obtained. . . . . . . : Friday, March 08, 2002
> 11:49:42 AM
> Lease Expires . . . . . . . : Saturday, March 09, 2002
> 9:48:37 AM
>
>
> > > But, pinging still renders no route to host.
> >
> > Just to make sure: you tried pinging a host on the local network, rigth ?
> > With just an ifconfig, no gateway is configured.
>
> No. I tried something across the internet. I just rebooted and tried
> this again on some local IP's. Pinging the broadcast address that
> sohwed up, 24.29.151.255, worked fine, with quick response.
Did you get only one anserw, or anserws from several different hosts
on the local net ?
> But,
> pinging my DNS server, 24.29.99.36, came back with "no route to host,"
> but it did so quickly.
This address is not on the local net. Your local net has addresses
between 24.29.148.0 and 24.29.151.255, in single-user mode with only the
interface configured (no default route) you can only reach machines from
the local net. You can add a default route with:
route add default 24.29.148.1
>
> Now, when I rebooted into multiuser mode and ran "dhclient sip0,"
> pinging to the DNS 24.29.99.36 also came back with "no route to host,"
> _BUT_ it took a LONG time for it to say that. Similarly, it took a long
> time to ping my IP, 24.29.149.12, even though the ping succeeded.
The delays are because it's trying to reach the dns now.
You can avoid this by using 'ping -n'
If the problem comes from the wrong broadcast sent by the server, maybe
you can change /sbin/dhclient-script to ignore it:
In the lines
eval "ifconfig $interface inet $new_ip_address \
$new_netmask_arg $new_broadcast_arg $medium"
route add $new_ip_address 127.0.0.1 >/dev/null 2>&1
remove the "$new_broadcast_arg".
This isn't needed anyway, as ifconfig can find the broadcast by itself
from the ip addr and netmask.
--
Manuel Bouyer <bouyer@antioche.eu.org>
--
From: Analysis and Solutions <danielc@analysisandsolutions.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Tue, 19 Mar 2002 15:43:21 -0500
Hi Manuel:
Manuel Bouyer wrote:
>
> On Fri, Mar 08, 2002 at 12:56:11PM -0500, Analysis & Solutions wrote:
>
> If the problem comes from the wrong broadcast sent by the server, maybe
> you can change /sbin/dhclient-script to ignore it:
> In the lines
> eval "ifconfig $interface inet $new_ip_address \
> $new_netmask_arg $new_broadcast_arg $medium"
> route add $new_ip_address 127.0.0.1 >/dev/null 2>&1
>
> remove the "$new_broadcast_arg".
> This isn't needed anyway, as ifconfig can find the broadcast by itself
> from the ip addr and netmask.
I didn't try this yet.
But, I did score a new network card which uses the fxp driver. Running
"dhclient fxp0" works fine. I got on the internet and connected to things
without a hitch. The card I got was the "Intel PRO/100 S Desktop Adapter,"
(Intel item # PILA8460C3. Uses the 82550EY chip.) So, this indicates that
Time Warner's DHCP server isn't the problem.
This also indicates that the problem is still in the sip driver. Customized
tweaking of the dhclient-script shouldn't be necessary. Also, having made
SEVERAL similar tweaks over the months of trying to sort this out, I bet it
wouldn't make the system work.
I'll be glad to test out revised editions of the driver for you, send the
Netgear FA312 card to someone for testing, or even modify the driver myself
(if you can find me some clear instructions on how to do it and what changes
may need to be tried).
Thanks,
--Dan
--
PHP scripts that make your job easier
http://www.analysisandsolutions.com/code/
SQL Solution | Layout Solution | Form Solution
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
4015 7 Ave, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Analysis and Solutions <danielc@analysisandsolutions.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/13460
Date: Thu, 21 Mar 2002 23:38:45 +0100
On Tue, Mar 19, 2002 at 03:43:21PM -0500, Analysis and Solutions wrote:
> I didn't try this yet.
>
> But, I did score a new network card which uses the fxp driver. Running
> "dhclient fxp0" works fine. I got on the internet and connected to things
> without a hitch. The card I got was the "Intel PRO/100 S Desktop Adapter,"
> (Intel item # PILA8460C3. Uses the 82550EY chip.) So, this indicates that
> Time Warner's DHCP server isn't the problem.
>
> This also indicates that the problem is still in the sip driver. Customized
> tweaking of the dhclient-script shouldn't be necessary. Also, having made
> SEVERAL similar tweaks over the months of trying to sort this out, I bet it
> wouldn't make the system work.
>
> I'll be glad to test out revised editions of the driver for you, send the
> Netgear FA312 card to someone for testing, or even modify the driver myself
> (if you can find me some clear instructions on how to do it and what changes
> may need to be tried).
Well, I won't do much hacking on the driver as I'm not the author, and it's
maintained.
Get in touch with thorpej@netbsd.org. He's the author of the driver and
is actively maintaining it. This driver runs on different adapters (incuding
a gigabit one) so maybe he just lack this specific model to test it ...
--
Manuel Bouyer <bouyer@antioche.eu.org>
--
From: Analysis & Solutions <danielc@analysisandsolutions.com>
To: thorpej@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: kern/13460
Date: Fri, 22 Mar 2002 00:56:48 -0500
Hi Jason:
I'm Dan Convissor. I put in the pr for kern/13460. It's regarding the
combination of the sip driver, DHCP and the Netgear FA312 (DP83815 chip)
card. Manuel Bouyer said I should contact you on this.
A year ago, I started trying to use NetBSD on my own machine (after
using it for some time on my ISP, Panix). I couldn't get the machine on
the net. After _SEVERAL_ weeks of hacking, folks on port-i386 said it
looks like a bug. I reported the matter and gave up.
Manuel, recently picked up the pr and contacted me. Changes to the kern
didn't resolve the issue. As a test, I scored a fxp based card. It,
and NetBSD are now working like a charm. So, the short of it is my
network and computer aren't the problem, leaving the aforementioned
driver/card/network combo in the bullseye.
Here's the pr's URI for your convenience:
http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=13460
I'll be glad to mail you the card if you like. Or I can run stuff here
if you give me clear instructions on what needs to be done.
Enjoy,
--Dan
PS: I checked out your bio page on the NetBSD site. Biking is a great
thing. I've got tons of stuff on bike politics on my site, if that's
your bag: http://www.panix.com/~danielc/bicycle.htm
--
PHP scripts that make your job easier
http://www.analysisandsolutions.com/code/
SQL Solution | Layout Solution | Form Solution
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
State-Changed-From-To: feedback->open
State-Changed-By: fair
State-Changed-When: Sat May 24 04:10:35 UTC 2003
State-Changed-Why:
Feedback has long since been provided.
Responsible-Changed-From-To: kern-bug-people->thorpej
Responsible-Changed-By: fair
Responsible-Changed-When: Sat May 24 05:31:43 UTC 2003
Responsible-Changed-Why:
Jason Thorpe wrote the sip(4) driver.
Responsible-Changed-From-To: thorpej->kern-bug-people
Responsible-Changed-By: wiz@NetBSD.org
Responsible-Changed-When: Sun, 15 Apr 2012 21:45:25 +0000
Responsible-Changed-Why:
Back to role account, thorpej left
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home