I have several client's I've setup with multiple gateways (office WAN, Internet
Gateway). I think this thread is derailed. 4.3 Release and prior (as far as I know)
have long supported this configuration.
At 08:08 AM 9/19/2001 +0800, [EMAIL PROTECTED] wrote:
>Is it possible to specify a gateway for each NIC on the next release of
>FreeBSD?
>
>> -----Original Message-----
>> From: Anuranjan [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, September 19, 2001 8:02 AM
>> To: 'Mike Saunders'; [EMAIL PROTECTED]
>> Subject: RE: kernel arp messages
>>
>> I recently came across the same prblem myself. You're facing it because of
>> the same subnet mask on your cards. In freeBSD if you configure two cards
>> on the same subnet the kernel gets confused as to which card is the
>> gateway
>> to the router. THe kernel seems to make this decision based on the fact
>> that if you want to configure two cards on the same machine you want to
>> use
>> it as a gateway between two different networks/subnets.
>>
>> --A
>>
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Saunders
>> Sent: Tuesday, September 18, 2001 4:45 PM
>> To: [EMAIL PROTECTED]
>> Subject: kernel arp messages
>>
>>
>> Hello!
>> I'm hoping somebody can help me with this problem. I'm about at my
>> wit's end. The problem is that i'm receiving the following messages
>> constantly, at the console, in the syslog, and to root's terminal.
>>
>> Sep 18 15:01:54 router /kernel: arp: 209.74.92.1 is on xl0 but got reply
>> from 00
>> :00:a2:66:83:41 on ep0
>> Sep 18 15:01:54 router last message repeated 4 times
>> Sep 18 15:01:54 router /kernel: arp: 209.74.87.1 is on lo0 but got reply
>> from 00
>> :60:08:35:57:4e on xl0
>> Sep 18 15:01:55 router last message repeated 2 times
>> Sep 18 15:01:55 router /kernel: arp: 209.74.87.193 is on ep0 but got reply
>> from
>> 00:50:da:c7:e7:68 on xl0
>> Sep 18 15:01:55 router /kernel: arp: 209.74.87.1 is on lo0 but got reply
>> from 00
>> :60:08:35:57:4e on xl0
>>
>> I'm running a 3.4-RELEASE i386 machine with two network cards. The
>> machine acts as a router between my LAN and my provider's network. ep0 is
>> the NIC connected to my LAN and xl0 is my provider's network.
>>
>>
>> Here's my network configuration:
>>
>> bash# ifconfig ep0
>> ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>> inet 209.74.87.1 netmask 0xffffff00 broadcast 209.74.87.255
>> ether 00:60:08:35:57:4e
>> bash# ifconfig xl0
>> xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>> inet 209.74.92.209 netmask 0xffffff00 broadcast 209.74.92.255
>> ether 00:50:da:c7:e3:1a
>> media: 10baseT/UTP <half-duplex>
>>
>> my /etc/rc.conf looks like this:
>>
>> ifconfig_xl0="inet 209.74.92.209 netmask 255.255.255.0"
>> ifconfig_ep0="inet 209.74.87.1 netmask 255.255.255.0"
>> hostname="router.cland-minot.com"
>> gateway_enable="YES"
>> defaultrouter="209.74.92.1"
>>
>> I tried to enable arpproxy_all="YES" in /etc/rc.conf, but that's
>> not helping, I still got spammed by all the arp messages. With the new
>> IIS exploit causing such increased traffic flow, the arp messages are
>> making console useless by filling the screen as well as lagging the system
>> horribly by churning the disk so much (It's only a pentium 60). I can't
>> even log into the machine via ssh. The only way to get a shell on it is
>> to pull the network lines and use the console.
>>
>> So, in short, besides redirecting console and syslog to /dev/null,
>> what can I do to make these arp messages go away?
>>
>> Thanks!
>>
>> -Mike Saunders
>> [EMAIL PROTECTED]
>>
>> Network Administrator - cland-minot.com
>> [EMAIL PROTECTED]
>>
>>
>>
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-net" in the body of the message
>>
>>
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-net" in the body of the message
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-net" in the body of the message
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
