Date: Wed, 16 Jun 1999 15:24:09 -0500 From: "Guy W. Gustavson" <guy.gustavson@eliancecorp.com> To: <freebsd-net@freebsd.org> Subject: multiple nics with different IP's on same subnet Message-ID: <00de01beb836$30e1c600$18d449cc@eliancecorp.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] I've got a server hosting pages for about 100 domains. They are all low enough traffic that the box can easily handle the load, but the IP aliasing is getting tricky. After about 80 IP's on the same NIC the IP stack stops responding and we have to reboot the box. Here's an example of how I'm aliasing the IP's, just repeat the ifconfig and the route add's about 80 times. ifconfig ep0 inet 206.191.205.6 alias ifconfig ep0 inet 206.191.205.9 alias route add 206.191.205.6 127.0.0.1 route add 206.191.205.8 127.0.0.1 We're building a new server anyway, and I was thinking of adding another NIC and hosting half the IP's one NIC and half on the other. The box has a class C to itself. Both NIC's would be on the same network, I could put in a switch if needed. If I setup things like this. ifconfig ep0 inet 206.191.205.6 alias ifconfig ep1 inet 206.191.205.9 alias . . . with a default route of 206.191.205.254 I get all the traffic coming back through one NIC and the usual ARP complaints... /kernel: arp: 206.191.205.6 is on ep0 but got reply from xx:xx:xx:xx on ep1 Is there anyway to interleave the IP's between the two NIC's and still have things route back from the same NIC it came from, and to get rid of the ARP complaints? The above configuration basically works, other than the ARP complaints and all the traffic coming back to one NIC. [-- Attachment #2 --] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.2314.1000" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>I've got a server hosting pages for about 100 domains. They are all low enough traffic that the box can easily handle the load, but the IP aliasing is getting tricky. After about 80 IP's on the same NIC the IP stack stops responding and we have to reboot the box.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>Here's an example of how I'm aliasing the IP's, just repeat the ifconfig and the route add's about 80 times.</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>ifconfig ep0 inet 206.191.205.6 alias<BR>ifconfig ep0 inet 206.191.205.9 alias</FONT> </DIV> <DIV><FONT face=Arial size=2>route add 206.191.205.6 127.0.0.1<BR>route add 206.191.205.8 127.0.0.1</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>We're building a new server anyway, and I was thinking of adding another NIC and hosting half the IP's one NIC and half on the other. The box has a class C to itself. Both NIC's would be on the same network, I could put in a switch if needed.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>If I setup things like this.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>ifconfig ep0 inet 206.191.205.6 alias</FONT></DIV> <DIV><FONT face=Arial size=2>ifconfig ep1 inet 206.191.205.9 alias</FONT></DIV> <DIV><FONT face=Arial size=2>.</FONT></DIV> <DIV><FONT face=Arial size=2>.</FONT></DIV> <DIV><FONT face=Arial size=2>.</FONT></DIV> <DIV> </DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>with a default rout</FONT><FONT face=Arial size=2>e of 206.191.205.254 I get all the traffic coming back through one NIC and the usual ARP complaints...</FONT></DIV> <DIV><FONT face=Arial size=2>/kernel: arp: 206.191.205.6 is on ep0 but got reply from xx:xx:xx:xx on ep1</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>Is there anyway to interleave the IP's between the two NIC's and still have things route back from the same NIC it came from, and to get rid of the ARP complaints?</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>The above configuration basically works, other than the ARP complaints and all the traffic coming back to one NIC.<BR></DIV></FONT> <DIV> </DIV></BODY></HTML>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00de01beb836$30e1c600$18d449cc>