Date: Wed, 25 Apr 2001 09:21:22 -0700 From: Sean Chittenden <sean@chittenden.org> To: Dave VanAuken <dave@hawk-systems.com> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: FreeBSD w 3C905 cannot connect to/through Cisco 3524XL switch Message-ID: <20010425092122.F13545@rand.tgd.net> In-Reply-To: <DBEIKNMKGOBGNDHAAKGNEELKFBAA.dave@hawk-systems.com>; from "dave@hawk-systems.com" on Wed, Apr 25, 2001 at = 07:57:15AM References: <Pine.BSF.4.21.0104250844210.24730-100000@velvet.sensation.net.au> <DBEIKNMKGOBGNDHAAKGNEELKFBAA.dave@hawk-systems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--XIiC+We3v3zHqZ6Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 25, 2001 at 07:57:15AM -0400, Dave VanAuken wrote: > router(also cisco) speaks to switch just fine Win2K workstations > using 3C905 cards speak to switch just fine FreeBSD servers using > 3C905 cards have problems... Autonegotiation of network speeds and duplexes is horribly unreliable. I have administered clusters of FreeBSD systems that plug into 6006's and 3524's and there wasn't rhym or reason as to which boxes autonegotiated correctly. 100% of the time, with maybe the exception of a workgroup environment, you want to manually set it's speed to 100 and duplex to full. Cisco: in if-conf: speed 100 duplex full on server in /etc/rc.conf: ifconfig_foo0=3D".... media 100baseTX mediaopt full-duplex" > ping and other network utils respond with "host is down" That's because the switch doesn't see the computer as up. > am wondering if it is not picking up the switch during boot > or something. Maybe, but auto-neg is bad in every way shape and form and was designed for workgroup environments, not servers. If a server doesn't negotiate at 100 full, then I've got a problem and I want the server to disappear from the network. > using unroutables, here is what the network looks like: > Network 192.168.1.0/26 > Router 192.168.1.1 255.255.255.192 WAN (upstream IP addr) > Switch 192.168.1.5 255.255.255.192 Network 192.168.1.1 > Workstations 192.168.1.20-24 255.255.255.192 Gateway > 192.168.1.1 > FreeBSD1 192.168.1.10 255.255.255.192 Gateway Router > 192.168.1.1 > aliased 192.168.1.15-17 255.255.255.192 > FreeBSD2 192.168.1.11 255.255.255.192 Gateway Router > 192.168.1.1 This won't matter, the 3524XL doesn't, by and large, see layer three traffic. They're great switches though, I've only had one problem a cluster of 5 of them in over a year of operation. -sc --=20 Sean Chittenden --XIiC+We3v3zHqZ6Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden <sean@chittenden.org> iEYEARECAAYFAjrm+YIACgkQn09c7x7d+q2XMQCfVO0SSfdTsBW49LbP5ZIszVQR eV0AnjovmNBM69P8E2hSHrVYuLX3Az62 =NO9D -----END PGP SIGNATURE----- --XIiC+We3v3zHqZ6Z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010425092122.F13545>