[ previous ] [ next ] [ threads ]
 
 From:  Peter <peter at iwebsl dot com>
 To:  "m0n0wall at lists dot m0n0 dot ch" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] arplookup error
 Date:  Sat, 25 Mar 2006 12:41:41 -0500
Agreed, so the best option is to forget about the "not on local network" error and leave the router
on its own subnet?

Peter


On Sat, 25 Mar 2006 18:36:04 +0100, Jonathan De Graeve wrote:
> This behaviour is normal since both m0n0 interfaces are on the same
> physical lan (which they shouldn't!)
>
> J.
>
>> -----Oorspronkelijk bericht-----
>> Van: Christoph Hanle [mailto:christoph dot hanle at leinpfad dot de]
>> Verzonden: vrijdag 24 maart 2006 6:53
>> Aan: m0n0wall at lists dot m0n0 dot ch
>> Onderwerp: Re: [m0n0wall] arplookup error
>>
>> I moved my router to the same subnet as the lan and unchecked
>> block
>> private networks as suggested but now I have a new error.
>> /kernel: arp: 192.168.1.1 is on em0 but got reply from
>> 00:13:10:51:a4:25
>> on fxp0
>>
>> I'm thinking that the previous error is less serious. Any
>> suggestions?
>>
>>
>> Peter schrieb:
>>> Hi List
>>> Up until yesterday I have been using m0n0 for a couple years
>>> with a
>> cable modem with DNCP on the wan interface. Yesterday my ISP
>> upgraded me
>> to a Cisco router with static IP's. All of the setting changes
>> seemed to
>> go ok and from what I can tell all is working as it should.
>> However I'm
>> now seeing these error in my m0n0 log.
>>
>>> Mar 24 00:08:04         /kernel: arplookup 192.168.0.1 failed:
>>> host is
>> not on local network
>>> Mar 23 23:58:09         /kernel: arplookup 192.168.0.1 failed:
>>> host is
>> not on local network
>>> Mar 23 23:43:06         /kernel: arplookup 192.168.0.1 failed:
>>> host is
>> not on local network
>>> Mar 23 23:32:21         /kernel: arpresolve: can't allocate
>>> llinfo for
>> 192.168.0.1rt
>>
>>> My router has a local IP of 192.168.0.1 while my m0n0 is on
>>> 192.168.1.1
>> and I'm pretty sure what is happening is the router is trying to
>> communicate to m0n0.
>>
>>> Is there a setting I need to make to fix this, is this a BIG
>>> problem or
>> a non issue?
>> arplookup has the answer: 192.168.0.1 and 192.168.1.1 are not in
>> the
>> same network.
>> use 192.168.1.1 and 192.168.1.2 or 192.168.0.1 and 192.168.0.2
>> bye
>> Christoph
>>
>>> Regards,
>>> Peter
>>>   ------------------------------------------------
>>>   Peter, peter at iwebsl dot com on 3/23/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
>>>
>>
>> --
>> last words:
>> "let's make the backup tomorrow"
>>
>> ------------------------------------------------------------------
>> ---
>> 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