RE: dual-homed problems
I've got a machine that's been running fine for years with one NIC. I want to experiment with setting it up as a gateway and have installed a second NIC in it. I can't seem to get the second NIC working fully. Here's the dmesg output on the two NICs: dc0: 82c169 PNIC 10/100BaseTX port 0x9100-0x91ff mem 0x81061000-0x810610ff irq 1 at device 11.0 on pci0 dc0: interrupting at CIA irq 1 dc0: Ethernet address: 00:02:e3:07:17:3b miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: D-Link DFE-530TX+ 10/100BaseTX port 0x9200-0x92ff mem 0x81061100-0x810611ff irq 3 at device 12.0 on pci0 rl0: interrupting at CIA irq 3 rl0: Ethernet address: 00:05:5d:36:15:a7 miibus1: MII bus on rl0 rlphy0: RealTek internal media interface on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here's the ifconfig output on the two NICs: dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.1.144 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::202:e3ff:fe07:173b%dc0 prefixlen 64 scopeid 0x1 ether 00:02:e3:07:17:3b media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::205:5dff:fe36:15a7%rl0 prefixlen 64 scopeid 0x2 ether 00:05:5d:36:15:a7 media: Ethernet autoselect (100baseTX full-duplex) status: active Here's my /etc/rc.conf lines for the two NICs: ifconfig_dc0=inet 192.168.1.144 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.1.145 netmask 255.255.255.0 As you can see from the ifconfig output, the new NIC is UP and RUNNING, but has no IP address (even though I have it in /etc/rc.conf). I can bring rl0 down and up again without a problem. If I try to add the IP data manually using ifconfig, I get this error: zeus# ifconfig rl0 inet 192.168.1.145 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): File exists Any ideas for getting this NIC up and running properly?? I haven't seen that error before, but you do have a small problem with the config. You shouldn't have two cards on the same subnet. If you just want to try it out, assign the new card a 192.168.2.xxx address. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: dual-homed problems
Hello, On Tue, 2003-07-08 at 17:05, Derrick Ryalls wrote: I've got a machine that's been running fine for years with one NIC. I want to experiment with setting it up as a gateway and have installed a second NIC in it. I can't seem to get the second NIC working fully. Here's the dmesg output on the two NICs: dc0: 82c169 PNIC 10/100BaseTX port 0x9100-0x91ff mem 0x81061000-0x810610ff irq 1 at device 11.0 on pci0 dc0: interrupting at CIA irq 1 dc0: Ethernet address: 00:02:e3:07:17:3b miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: D-Link DFE-530TX+ 10/100BaseTX port 0x9200-0x92ff mem 0x81061100-0x810611ff irq 3 at device 12.0 on pci0 rl0: interrupting at CIA irq 3 rl0: Ethernet address: 00:05:5d:36:15:a7 miibus1: MII bus on rl0 rlphy0: RealTek internal media interface on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here's the ifconfig output on the two NICs: dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.1.144 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::202:e3ff:fe07:173b%dc0 prefixlen 64 scopeid 0x1 ether 00:02:e3:07:17:3b media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::205:5dff:fe36:15a7%rl0 prefixlen 64 scopeid 0x2 ether 00:05:5d:36:15:a7 media: Ethernet autoselect (100baseTX full-duplex) status: active Here's my /etc/rc.conf lines for the two NICs: ifconfig_dc0=inet 192.168.1.144 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.1.145 netmask 255.255.255.0 You're not allowed to have two interfaces active on the same subnet As you can see from the ifconfig output, the new NIC is UP and RUNNING, but has no IP address (even though I have it in /etc/rc.conf). I can bring rl0 down and up again without a problem. If I try to add the IP data manually using ifconfig, I get this error: zeus# ifconfig rl0 inet 192.168.1.145 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): File exists This is a warning that the IP details you've attempted to assign to the nic is already loaded, and that it cannot be loaded again. Any ideas for getting this NIC up and running properly?? The second nic is not coming up for the simple reason (I presume) that the former nic is already up and active on the 192.168.1.x subnet. Dual-homed hosts (PC-based routers) are usually set up to route packets between two *different* networks. So, as suggested below, you'll want to assign a different network address to the second nic, and (providing there's a lan there) all should be well. Regards, Stacey I haven't seen that error before, but you do have a small problem with the config. You shouldn't have two cards on the same subnet. If you just want to try it out, assign the new card a 192.168.2.xxx address. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dual-homed problems
On Tue, Jul 08, 2003 at 12:41:43PM -0400, Michael A. Smith wrote: rl0: D-Link DFE-530TX+ 10/100BaseTX port 0x9200-0x92ff mem Ugh... I've never liked those cards. I had two in a gateway a couple of years ago -- the box spontaneously rebooted twice a week until I replace them with fxp's, at which point the only thing to take it down was a power supply fan rl0: interrupting at CIA irq 3 Ooh, the CIA is in your computer. Here's my /etc/rc.conf lines for the two NICs: ifconfig_dc0=inet 192.168.1.144 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.1.145 netmask 255.255.255.0 This is wrong. When you assign IP addresses to interfaces, you give them a subnet they know they can find on the Ethernet segment connected to that interface. Where should your computer send traffic for 192.168.1.100? Out which interface? zeus# ifconfig rl0 inet 192.168.1.145 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): File exists This error occurs when FreeBSD tries to overwrite the routing info set by the ifconfig statement for the first NIC. Do a `netstat -rn` to see relationships between subnets and interfaces. Any ideas for getting this NIC up and running properly?? Use a different IP network for it: ifconfig_dc0=inet 192.168.1.144 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.2.1netmask 255.255.255.0 Or use a smaller IP network for it: ifconfig_dc0=inet 192.168.1.144 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.1.253 netmask 255.255.255.252 But if 192.168.1.0/24 is in your routing table, its traffic goes out of one, and only one, interface. -- Paul Chvostek [EMAIL PROTECTED] it.canadahttp://www.it.ca/ Free PHP web hosting!http://www.it.ca/web/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
