Thanks for all the replies gentlemen!  I'll try to clear some things up
here:

On Tue, 18 Sep 2001, Lars Eggert wrote:

> Date: Tue, 18 Sep 2001 17:31:24 -0800
> From: Lars Eggert <[EMAIL PROTECTED]>
> To: Mike Saunders <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: RE: kernel arp messages
> 
> > 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
> 
> And this is *really* ugly! Are you proxy-arping? Someone is advertising
> one of your local IP addresses.

Actually Lars,
        If you notice the MAC, it's the same as:
 
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

So 209.74.87.1 is on ep0 which is on lo0 but gets caught at xl0, according
to this machine.

So maybe a picture will help

                        |
                        |
                        |
                   209.74.92/24
                        |
                      (xl0)
                  FreeBSD Router
                      (ep0)
                        |
                   209.74.87/24
                        |
                     switches

This is what I believe to be the current set up.  Now that I read the
email mentioning the loop, it's possible that somebody has thrown in a hub
connecting both networks.  I know there's one in the closet.  I'll have to
go and check.

        Ideally, all I'm trying to do is route one class C into my
provider's network.  I just want a router, it happens to be running
FreeBSD instead of IOS.

I'll have to go take a look at the cabling setups though.  Thanks for the
tips everybody.

-Mike
[EMAIL PROTECTED]


> 
> Again, I think a picture of your setup would help. It sounds like you're
> simply trying to set up a FreeBSD router between to networks, this should
> not be so complicated.
> 
> Lars
> --
> Lars Eggert <[EMAIL PROTECTED]>               Information Sciences Institute
> http://www.isi.edu/larse/              University of Southern California
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to