[ previous ] [ next ] [ threads ]
 
 From:  "Jonathan De Graeve" <Jonathan dot De dot Graeve at imelda dot be>
 To:  <peter at iwebsl dot com>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] arplookup error
 Date:  Sun, 26 Mar 2006 00:04:47 +0100
You have 3options:

1) like Chris said, leave it as is (different ip)
2) create a bridge
3) use unnumbered (maybe in combination with proxy arp ;) )

J.

> -----Oorspronkelijk bericht-----
> Van: Peter [mailto:peter at iwebsl dot com]
> Verzonden: zaterdag 25 maart 2006 23:30
> Aan: Jonathan De Graeve
> CC: m0n0wall at lists dot m0n0 dot ch
> Onderwerp: RE: [m0n0wall] arplookup error
> 
> My m0n0 is 192.168.1.254 and the Cisco is 192.168.0.1 if I change it to
> 192.168.1.1 is get the second error I mentioned.
> 
> Peter
> 
> On Sat, 25 Mar 2006 23:19:55 +0100, Jonathan De Graeve wrote:
> > It can, and there is a specific feature for it on cisco called ip
> > unnumbered
> >
> > You shouldn't give your cisco the same ip as the m0n0 lan
> >
> > J.
> >
> >> -----Oorspronkelijk bericht-----
> >> Van: Peter [mailto:peter at iwebsl dot com]
> >> Verzonden: zaterdag 25 maart 2006 22:35
> >> Aan: Chris Buechler
> >> CC: m0n0wall at lists dot m0n0 dot ch
> >> Onderwerp: Re: [m0n0wall] arplookup error
> >>
> >> Hi Chris
> >>
> >> Thanks for responding.
> >>
> >> The hookup is like this.
> >>
> >> coax cable WAN -> Cisco -> xover to M0n0 -> switch -> LAN PC's
> >>
> >> I have the m0n0 WAN interface set to the first public IP and the
> >> gateway
> >> IP. The Cisco router is supplying 3 outside IPs to m0n0 by
> >> default the
> >> Cisco router has a local IP 192.168.0.1 which is being broadcast
> >> to m0n0
> >> and I get this error:
> >> /kernel: arplookup 192.168.0.1 failed: host is not on local
> >> network
> >>
> >> If I program the Cisco router to the same subnet as m0n0 I get
> >> this error:
> >> /kernel: arp: 192.168.1.1 is on em0 but got reply from
> >> 00:13:10:51:a4:25
> >> on fxp0
> >>
> >> I don't know why or how the router can have a local IP and a
> >> outside IP on
> >> the same ethernet port.
> >>
> >> Peter
> >>
> >> On Sat, 25 Mar 2006 15:18:15 -0500, Chris Buechler wrote:
> >>> On 3/25/06, Peter <peter at iwebsl dot com> wrote:
> >>>
> >>>> Agreed, so the best option is to forget about the "not on
> >>>> local
> >>>> network" error and leave the router on its own subnet?
> >>>>
> >>>
> >>> Unless I'm missing something, your network looks like:
> >>>
> >>> Internet -- Cisco -- m0n0wall -- LAN
> >>>
> >>> correct?
> >>>
> >>> but you have both sides of the m0n0wall, as shown above, on the
> >>> same
> >>> broadcast domain.  You should really plug only m0n0wall into
> >>> your
> >>> LAN,
> >>> and connect the Cisco and m0n0wall with a crossover cable on
> >>> the WAN
> >>> side.
> >>>
> >>> -Chris
> >>>
> >>> ----------------------------------------------------------------
> >>> ----
> >>> -
> >>> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> >>> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> >>>
> >>  ------------------------------------------------
> >>  Peter, peter at iwebsl dot com on 3/25/2006
> >>
> >>
> >> ------------------------------------------------------------------
> >> ---
> >> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> >> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> >
> >
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> 
>   ------------------------------------------------
>   Peter, peter at iwebsl dot com on 3/25/2006
> 
>