Date: Mon, 18 Jul 2005 09:06:56 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: sledgehammer@revier.net Cc: freebsd-current@freebsd.org Subject: Re: re Problems with dhclient Message-ID: <20050718160656.GC8822@odin.ac.hmc.edu> In-Reply-To: <33051.82.141.44.113.1121525238.squirrel@webmail.kamp-dsl.de> References: <20050716091735.53D4C16A428@hub.freebsd.org> <33051.82.141.44.113.1121525238.squirrel@webmail.kamp-dsl.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--0vzXIDBeUiKkjNJl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 16, 2005 at 04:47:18PM +0200, sledgehammer@revier.net wrote: > Hi. >=20 > I'm having the same problems here in FreeBSD 7.0 current....wired > connection only going to a Draytek Vigor 2600 DSL router...I just tried to > transfer a couple of GB over my LAN via SSH from my PC running FreeBSD 7.0 > to my Mac Mini running Mac OS X 10.4.2 and the connection got lost all of > a sudden...FreeBSD wasn't able to connect to the internet either for a > while while the Mac had no such problems..here's the part from the log for > my SSH transfer: >=20 > Jul 16 16:28:43 lepus kernel: rl0: discard oversize frame (ether type ffff > flags 3 len 5628 > max 1514) >=20 > When I run a dmesg I get this: >=20 > I had never seen that in 5.4 >=20 > $ dmesg | grep rl > rl0: <RealTek 8139 10/100BaseTX> port 0x9800-0x98ff mem > 0xd7eff800-0xd7eff8ff irq 17 at device 9.0 on pci1 > miibus0: <MII bus> on rl0 > rlphy0: <RealTek internal media interface> on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:11:d8:05:10:ae > rl0: discard oversize frame (ether type ffff flags 3 len 5628 > max 1514) > rl0: discard oversize frame (ether type f427 flags 3 len 11428 > max 1514) > rl0: discard oversize frame (ether type e467 flags 3 len 57295 > max 1514) > rl0: discard oversize frame (ether type 80a flags 3 len 20975 > max 1514) >=20 > $ uname -psr > FreeBSD 7.0-CURRENT i386 It's hightly unlikely this has anything to do with dhclient. It appears your nic or the driver is totally foobar. You're getting major undeteted packet corruption which is generally a bad sign and way below the level of dhclient. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --0vzXIDBeUiKkjNJl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFC29OfXY6L6fI4GtQRAu53AJ9ili3YJgYbLiwWCNYyAbPw9MHyyACdHibK 8MBb+YCKNkuD7NjM5apPhV4= =ScbH -----END PGP SIGNATURE----- --0vzXIDBeUiKkjNJl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050718160656.GC8822>