Date: 15 Jan 2003 23:50:37 +0000 From: Stacey Roberts <stacey@vickiandstacey.com> To: Brian Astill <bastill@adam.com.au> Cc: Nikolaj Farrell <nikk@home.se>, FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Problems w NIC Message-ID: <1042674635.51041.412.camel@localhost> In-Reply-To: <3E25F20A.2030009@adam.com.au> References: <001701c2b987$9fdf72e0$0100a8c0@athlon> <1042300066.51041.227.camel@localhost> <002a01c2b989$f2099e90$1200a8c0@gsicomp.on.ca> <000b01c2b98a$df9981c0$0100a8c0@athlon> <1042301568.51041.233.camel@localhost> <001201c2b98e$063311e0$0100a8c0@athlon> <1042303096.51041.237.camel@localhost> <000301c2b993$55e70610$0100a8c0@athlon> <20030111171152.GH25529@sub21-156.member.dsl-only.net> <001b01c2b995$0dbf6d30$0100a8c0@athlon> <1042305860.51041.240.camel@localhost> <001801c2b999$95567000$0100a8c0@athlon> <1042310110.51041.250.camel@localhost> <002b01c2b9c3$56722e40$0100a8c0@athlon> <1042325630.51041.257.camel@localhost> <003701c2b9c4$db6e6950$0100a8c0@athlon> <1042328202.51041.268.camel@localhost> <00c301c2b9cd$71a44360$0100a8c0@athlon> <1042329896.51041.273.camel@localhost> <000a01c2b9cf$fb483f20$0100a8c0@athlon> <3E25F20A.2030009@adam.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Brian, On Wed, 2003-01-15 at 23:43, Brian Astill wrote: > I was very sad to see this thread die, just as (for me) it was getting > interesting. > My setup and experience is almost identical to Nicola's. > > bra@BAPhD ~ ifconfig -au > rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::200:21ff:fed5:c670%rl0 prefixlen 64 scopeid 0x1 > ether 00:00:21:d5:c6:70 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 > inet 127.0.0.1 netmask 0xff000000 rl0 seem okay., > > Where is the second NIC? > > bra@BAPhD ~ ifconfig -a > rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::200:21ff:fed5:c670%rl0 prefixlen 64 scopeid 0x1 > ether 00:00:21:d5:c6:70 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > rl1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > ether 00:05:1c:01:96:22 > media: Ethernet autoselect (10baseT/UTP) > status: active > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 > inet 127.0.0.1 netmask 0xff000000 > > (I have removed extraneous data) > > SO ... the problem is that the second NIC which is connected to my hub > - (in my case rl1) is not UP. > WHY isn't it UP? Presumably something missing in rc.conf? > > Hope someone can help. > It appears that rl1 is not configured here. Two things of note: 1] Have you actually configured rl1? 2] If so, what IP addr configurations is supposed to have? The reasoning behind my questions is the fact that you mentioned that *both* rl0 & rl1 are connected to "the same hub". Hubs are devices that provide for sharing collision domains on a subnet - hosts / nodes that on the same subnet all see the same traffic. FreeBSD (under normal circumstances) would not allow you to have multiple nics configured with IP addrs within the same subnet. E.G: rl0 = 10.0.0.1 rl1 = 10.0.0.2 FreeBSD wouldn't normally allow you to do this. Do you have rl1 defined in /etc/rc.conf? Post that for us, please. Regards, Stacey > -- > Brian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1042674635.51041.412.camel>