From owner-freebsd-net Wed Jun 16 13:24:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.eliancecorp.com (mail.eliancecorp.com [204.73.214.40]) by hub.freebsd.org (Postfix) with ESMTP id A477F14CEB for ; Wed, 16 Jun 1999 13:24:12 -0700 (PDT) (envelope-from guy.gustavson@eliancecorp.com) Received: from ggustavson (ggustavson.eliancecorp.com [204.73.212.24]) by mail.eliancecorp.com (8.9.3/8.9.3) with SMTP id PAA10122 for ; Wed, 16 Jun 1999 15:24:43 -0500 Message-ID: <00de01beb836$30e1c600$18d449cc@eliancecorp.com> From: "Guy W. Gustavson" To: Subject: multiple nics with different IP's on same subnet Date: Wed, 16 Jun 1999 15:24:09 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DB_01BEB80C.47E28B20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_00DB_01BEB80C.47E28B20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=20 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. ------=_NextPart_000_00DB_01BEB80C.47E28B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've got a server hosting pages for = about 100=20 domains. They are all low enough traffic that the box can easily handle = the=20 load, but the IP aliasing is getting tricky.  After about 80 IP's = on the=20 same NIC the IP stack stops responding and we have to reboot the=20 box.
 
Here's an example of how I'm aliasing = the IP's,=20 just repeat the ifconfig and the route add's about 80 = times.
 
ifconfig ep0 inet 206.191.205.6 = alias
ifconfig=20 ep0 inet 206.191.205.9 alias
 
route add 206.191.205.6 = 127.0.0.1
route add=20 206.191.205.8 127.0.0.1
 
We're building a new server anyway, and = I was=20 thinking of adding another NIC and hosting half the IP's one NIC and = half on the=20 other. The box has a class C to itself. Both NIC's would be on the same = network,=20 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=20 of 206.191.205.254 I get all the traffic coming back through one NIC and = the=20 usual ARP complaints...
/kernel: arp: 206.191.205.6 is on ep0 = but got reply=20 from xx:xx:xx:xx on ep1
 
Is there anyway to interleave the = IP's between=20 the two NIC's and still have things route back from the same NIC it came = from,=20 and to get rid of the ARP complaints?
 
The above configuration basically = works, other than=20 the ARP complaints and all the traffic coming back to one = NIC.
 
------=_NextPart_000_00DB_01BEB80C.47E28B20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message