Date: Fri, 19 Aug 2005 15:24:36 +0300 From: =?ISO-8859-9?Q?=D6zkan_KIRIK?= <ozkan@mersin.edu.tr> To: Daniel Valencia <fetrovsky@yahoo.com>, freebsd-net@freebsd.org Subject: Re: multiple interfaces Message-ID: <4305CF84.60409@mersin.edu.tr> In-Reply-To: <20050818194031.59265.qmail@web53908.mail.yahoo.com> References: <20050818194031.59265.qmail@web53908.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You cannot define same network to more then one interface! As you post below; xl0: inet 10.0.1.1 netmask 0xffff0000 broadcast 10.0.255.255 xl1: inet 10.0.1.2 netmask 0xffff0000 broadcast 10.0.255.255 They are at the same network, so your freebsd searchs 10.0.1.2 at xl0. You should define your xl1 as inet 10.0.1.2 netmask 255.255.255.255 With Best Regards, Ozkan KIRIK EnderUNIX SDT@Turkey Software Developer Daniel Valencia wrote: >Hi > >from the boot messages, i can see that the network >devices are started up properly. Strangely enough, >the one that doesnt seem to be assigned an IRQ# is not >having any problems, but one of the ones that is. > >Here are the boot messages > >de0: <Digital 21140A Fast Ethernet> port 0x4000-0x407f >mem 0xf4a01000-0xf4a0107f at device 11.0 on pci2 >de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 >de0: Ethernet address: 00:00:c0:7f:a1:fd >de0: if_start running deferred for Giant >xl0: <3Com 3c905C-TX Fast Etherlink XL> port >0x4080-0x40ff mem 0xf4a01400-0xf4a0147f irq 10 at >device 13.0 on pci2 >miibus0: <MII bus> on xl0 >xlphy0: <3c905C 10/100 internal PHY> on miibus0 >xlphy0: 10baseT, 10baseT-FDX, 100baseTX, >100baseTX-FDX, auto >xl0: Ethernet address: 00:01:02:c1:ba:82 >xl1: <3Com 3c905C-TX Fast Etherlink XL> port >0x4400-0x447f mem 0xf4a01800-0xf4a0187f irq 11 at >device 15.0 on pci2 >miibus1: <MII bus> on xl1 >xlphy1: <3c905C 10/100 internal PHY> on miibus1 >xlphy1: 10baseT, 10baseT-FDX, 100baseTX, >100baseTX-FDX, auto >xl1: Ethernet address: 00:01:02:44:3c:22 > >Here goes my ifconfig > > > >>ifconfig >> >> >de0: >flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> >mtu 1500 > inet 128.200.38.140 netmask 0xffffff00 >broadcast 128.200.38.255 > inet6 fe80::200:c0ff:fe7f:a1fd%de0 prefixlen >64 scopeid 0x1 > ether 00:00:c0:7f:a1:fd > media: Ethernet autoselect (100baseTX ><full-duplex>) > status: active >xl0: >flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu >1500 > options=9<RXCSUM,VLAN_MTU> > inet 10.0.1.1 netmask 0xffff0000 broadcast >10.0.255.255 > inet6 fe80::201:2ff:fec1:ba82%xl0 prefixlen 64 >scopeid 0x2 > ether 00:01:02:c1:ba:82 > media: Ethernet autoselect (100baseTX ><full-duplex>) > status: active >xl1: >flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu >1500 > options=9<RXCSUM,VLAN_MTU> > inet 10.0.1.2 netmask 0xffff0000 broadcast >10.0.255.255 > inet6 fe80::201:2ff:fe44:3c22%xl1 prefixlen 64 >scopeid 0x3 > ether 00:01:02:44:3c:22 > media: Ethernet autoselect (100baseTX ><full-duplex>) > status: active >lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu >16384 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > > > >And, at last, a few ping attempts > > > >>ping -c 1 128.200.38.140 >> >> >PING 128.200.38.140 (128.200.38.140): 56 data bytes >64 bytes from 128.200.38.140: icmp_seq=0 ttl=64 >time=0.130 ms > >--- 128.200.38.140 ping statistics --- >1 packets transmitted, 1 packets received, 0% packet >loss >round-trip min/avg/max/stddev = >0.130/0.130/0.130/0.000 ms > > >>ping -c 1 10.0.1.1 >> >> >PING 10.0.1.1 (10.0.1.1): 56 data bytes >64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=0.128 >ms > >--- 10.0.1.1 ping statistics --- >1 packets transmitted, 1 packets received, 0% packet >loss >round-trip min/avg/max/stddev = >0.128/0.128/0.128/0.000 ms > > >>ping -c 1 10.0.1.2 >> >> >PING 10.0.1.2 (10.0.1.2): 56 data bytes > >--- 10.0.1.2 ping statistics --- >1 packets transmitted, 0 packets received, 100% packet >loss > > >> >> >> > > >Thank you very much, > >Daniel > > >--- Brooks Davis <brooks@one-eyed-alien.net> wrote: > > > >>On Thu, Aug 18, 2005 at 11:36:55AM -0700, Daniel >>Valencia wrote: >> >> >>>Hello, everybody >>> >>>Is there any limit as of how many interfaces can >>>freebsd handle? Im trying to build a switch in a >>> >>> >>PC >> >> >>>box, putting multiple NICs and some software... >>> >>> >>The >> >> >>>issue is, even though all of the cards work >>> >>> >>correctly >> >> >>>by themselves, once I put them together, it doesnt >>>matter what slots i use, I can never make more >>> >>> >>than >> >> >>>two of them work. For even though all the rest >>> >>> >>appear >> >> >>>up as well, I cant ping neither them nor their >>> >>> >>peers >> >> >>>(Im using crossover cables). >>> >>> >>The software limit is 2^16-1. It sounds like you >>are having hardware >>issues. I'd tend to guess interrupt routing issues. >> I'd suggest >>posting details to freebsd-questions or possibly >>freebsd-stable. >> >>-- Brooks >> >>-- >>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 >> >> >> > > > > >____________________________________________________ >Start your day with Yahoo! - make it your home page >http://www.yahoo.com/r/hs > >_______________________________________________ >freebsd-net@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-net >To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4305CF84.60409>