Jon Radel wrote:
to see what you can catch.
First of all, thanks for taking time to help me on this.
[EMAIL PROTECTED] ~]# tcpdump -vvv -n -l -e arp
tcpdump: listening on nfe0, link-type EN10MB (Ethernet), capture size 96
bytes
08:58:46.337968 00:1d:60:36:34:a6 ff:ff:ff:ff:ff:ff,
Christian Walther wrote:
I don't want to point you into the wrong direction, but is it possible
that this arp entry is actually a sign of an ARP spoofing attempt?
http://en.wikipedia.org/wiki/ARP_spoofing
I suspect that, but I just want to know if might be something else.
Do you run a
Christer Solskogen wrote:
[EMAIL PROTECTED] ~]# tcpdump -vvv -n -l -e arp
tcpdump: listening on nfe0, link-type EN10MB (Ethernet), capture size 96
bytes
08:58:46.337968 00:1d:60:36:34:a6 ff:ff:ff:ff:ff:ff, ethertype ARP
(0x0806), length 60: arp who-has 192.168.0.3 tell 192.168.0.12
Derek Ragona wrote:
Yes aliases should have a netmask of 255.255.255.255
Still no go.
192.168.0.255 is showing up in arp -a and netstat -rn. (and the
arplookup 0.0.0.0 failed: host is not on local network in
/var/log/messages)
nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST
At 06:22 AM 5/14/2008, Christer Solskogen wrote:
Derek Ragona wrote:
Yes aliases should have a netmask of 255.255.255.255
Still no go.
192.168.0.255 is showing up in arp -a and netstat -rn. (and the
arplookup 0.0.0.0 failed: host is not on local network in /var/log/messages)
nfe0: flags
Derek Ragona wrote:
I would do a traceroute from all your hosts there. When you do keep an
eye out for the arp error message. This should help find the host
causing these errors and then look at that systems configuration.
Also do you have more than one ethernet interface in the system
Christer Solskogen wrote:
Derek Ragona wrote:
I would do a traceroute from all your hosts there. When you do keep
an eye out for the arp error message. This should help find the host
causing these errors and then look at that systems configuration.
Also do you have more than one ethernet
, ethertype ARP
(0x0806), length 42: arp reply 216.143.151.11 is-at 00:16:76:cf:e4:b3
with resulting message in debug.log:
May 14 22:45:06 left kernel: arplookup 0.0.0.0 failed: host is not on
local netw
ork
May 14 22:45:07 left last message repeated 2 times
So I'm actually going to update my
At 04:50 PM 5/14/2008, Christer Solskogen wrote:
Derek Ragona wrote:
I would do a traceroute from all your hosts there. When you do keep an
eye out for the arp error message. This should help find the host
causing these errors and then look at that systems configuration.
Also do you have
Derek Ragona wrote:
Sounds like you have 0.0.0.0 configured on an ethernet interface. I
would check all your systems, and be sure it isn't used.
I checked, and there is no interface with that ip address. But thanks
for the advice.
OpenBSD box - where 0.0.0.0 is resolving to.
rl0:
Christer Solskogen wrote:
Derek Ragona wrote:
Sounds like you have 0.0.0.0 configured on an ethernet interface. I
would check all your systems, and be sure it isn't used.
I checked, and there is no interface with that ip address. But thanks
for the advice.
OpenBSD box - where 0.0.0.0
At 12:55 PM 5/12/2008, Christer Solskogen wrote:
Christer Solskogen wrote:
Derek Ragona wrote:
Sounds like you have 0.0.0.0 configured on an ethernet interface. I
would check all your systems, and be sure it isn't used.
I checked, and there is no interface with that ip address. But thanks
Derek Ragona wrote:
You may want to do traceroutes from the systems that do find the 0.0.0.0
interface. I would bet you have a default route and/or netmask sending
the traffic. You will get those arp messages if you run two different
interfaces on the same system, on the same subnet (not to
At 03:44 PM 5/12/2008, Christer Solskogen wrote:
Derek Ragona wrote:
You may want to do traceroutes from the systems that do find the 0.0.0.0
interface. I would bet you have a default route and/or netmask sending
the traffic. You will get those arp messages if you run two different
Hi!
I have been seeing a lot of warnings in syslog the last week. Do anyone
have a tip for where to begin searching for the sinner?
arplookup 0.0.0.0 failed: host is not on local network
arplookup 0.0.0.0 failed: host is not on local network
arplookup 0.0.0.0 failed: host is not on local
At 03:39 PM 5/11/2008, Christer Solskogen wrote:
Hi!
I have been seeing a lot of warnings in syslog the last week. Do anyone
have a tip for where to begin searching for the sinner?
arplookup 0.0.0.0 failed: host is not on local network
arplookup 0.0.0.0 failed: host is not on local network
how do i host custom game on warcraft 3
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taharni Duggan wrote:
how do i host custom game on warcraft 3
You aren't on the same subnet as your other machine. You need to
configure your network for all machines properly.
BTW, this isn't a warcraft 3 support group and your information you
Hi list,
today in the daily security report (periodic) of a i386 machine there
is this message repeated about 30 times:
+arplookup 0.0.0.0 failed: host is not on local network
The machine is the router (ipnat) and firewall (ipfilter) for a small
home network.
It runs postfix, sshd and nfsd
Pietro Cerutti wrote:
Hi list,
today in the daily security report (periodic) of a i386 machine there
is this message repeated about 30 times:
+arplookup 0.0.0.0 failed: host is not on local network
From rfc 3330:
0.0.0.0/8 - Addresses in this block refer to source hosts on this
network
a private
IP to the machine.
In /var/log/messages, the logs of the new DHCP lease are followed from
the ones of arplookup:
Mar 10 15:19:24 gahr dhclient: New IP Address (rl0): 192.168.100.10
Mar 10 15:19:24 gahr dhclient: New Subnet Mask (rl0): 255.255.255.0
Mar 10 15:19:24 gahr dhclient: New Broadcast
ok what doing you tell me how doing setting the ip address and fail
network local network
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL
Matt Juszczak [EMAIL PROTECTED] writes:
Does anyone know what arplookup comes to syslog as? (info, warning, etc.)
I get A LOT of:
arplookup xxx.xxx.xxx.xxx failed: host is not on local network
arplookup xxx.xxx.xxx.xxx failed: host is not on local network
arplookup xxx.xxx.xxx.xxx failed
Does anyone know what arplookup comes to syslog as? (info, warning, etc.)
I get A LOT of:
arplookup xxx.xxx.xxx.xxx failed: host is not on local network
arplookup xxx.xxx.xxx.xxx failed: host is not on local network
arplookup xxx.xxx.xxx.xxx failed: host is not on local network
arplookup
Hello,
The following message has been often repeating in my messages log:
Jun 6 19:24:38 server kernel: arplookup here is an ip addr failed:
host is not on local network
I know what arp is, and I understand this message, but I don't know what
causes it, but it annoys me, and I'd like
On Jun 6, 2005, at 1:59 PM, Kövesdán Gábor wrote:
The following message has been often repeating in my messages log:
Jun 6 19:24:38 server kernel: arplookup here is an ip addr
failed: host is not on local network
I know what arp is, and I understand this message, but I don't know
what
Kövesdán Gábor wrote:
Jun 6 19:24:38 server kernel: arplookup here is an ip addr failed:
host is not on local network
I know what arp is, and I understand this message, but I don't know
what causes it, but it annoys me, and I'd like to remove it from my
log, since it doesn't make any
Hi folks,
anybody know about the message below?
Abandoning IP Address 200.x.x.x: pinged before offer
No buffer space available arplookup 0.0.0.0 failed: host is not on load
network
Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8a
Syncing disks, buffers remaining.1347
Subject: No buffer space available arplookup 0.0.0.0 failed:
host is not
onload network
Hi folks,
anybody know about the message below?
Abandoning IP Address 200.x.x.x: pinged before offer
No buffer space available arplookup 0.0.0.0 failed: host is not on load
network
Fatal trap 12
I've got a system running 5.3-p6, and am getting this error every 20
minutes or so:
kernel: arplookup 69.61.54.33 failed: host is not on local network
I get that the host isn't on the network, but I don't have any idea
where the message is coming from. It's in /var/log/messages, shows up
about
Pat Maddox wrote:
I've got a system running 5.3-p6, and am getting this error every 20
minutes or so:
kernel: arplookup 69.61.54.33 failed: host is not on local network
I get that the host isn't on the network, but I don't have any idea
where the message is coming from. It's in /var/log/messages
wrote:
I've got a system running 5.3-p6, and am getting this error every 20
minutes or so:
kernel: arplookup 69.61.54.33 failed: host is not on local network
I get that the host isn't on the network, but I don't have any idea
where the message is coming from. It's in /var/log/messages
Pat Maddox wrote:
On Apr 4, 2005 5:48 AM, Andrew P. [EMAIL PROTECTED] wrote:
Pat Maddox wrote:
I've got a system running 5.3-p6, and am getting this error every 20
minutes or so:
kernel: arplookup 69.61.54.33 failed: host is not on local network
I get that the host isn't on the network, but I
Mark Edwards [EMAIL PROTECTED] writes:
On Mar 1, 2005, at 12:53 PM, Lowell Gilbert wrote:
Looking on the net, I found the following suggestion, which does
cure
the errors:
/sbin/route add -net 192.168.1.254 -netmask 255.255.255.0
-interface 1
My question is, is that the proper
I've just put my server on a new connection that requires DHCP, even
for a fixed IP. Anyway, the DHCP server gives a fixed public internet
IP to my server, but it communicates on 192.168.1.254, which angers
FreeBSD (4.11). I get a lot of the following:
arplookup 192.168.1.254 failed: host
:
arplookup 192.168.1.254 failed: host is not on local network
Which makes sense, because as far as FreeBSD is concerned, interface
ep1 is on the internet not on a LAN.
Exactly.
Looking on the net, I found the following suggestion, which does cure
the errors:
/sbin/route add -net
FreeBSD (4.11). I get a lot of the following:
arplookup 192.168.1.254 failed: host is not on local network
Which makes sense, because as far as FreeBSD is concerned, interface
ep1 is on the internet not on a LAN.
Exactly.
Looking on the net, I found the following suggestion, which does cure
, but it communicates on 192.168.1.254, which angers
FreeBSD (4.11). I get a lot of the following:
arplookup 192.168.1.254 failed: host is not on local network
Which makes sense, because as far as FreeBSD is concerned, interface
ep1 is on the internet not on a LAN.
Exactly
On Mar 1, 2005, at 12:53 PM, Lowell Gilbert wrote:
Looking on the net, I found the following suggestion, which does
cure
the errors:
/sbin/route add -net 192.168.1.254 -netmask 255.255.255.0
-interface 1
My question is, is that the proper way to deal with this?
It's not bad. I would use -host
On Sunday 05 December 2004 23:39, Tim wrote:
Greets,
I get a bunch of the following messages in my logs and on my
console screen:
kernel: arplookup 192.168.1.1 failed: host is not on local network
I've posted the same question to netbsd-users recently. Start tcpdump
-i your_external_if
Greets,
I get a bunch of the following messages in my logs and on my console
screen:
kernel: arplookup 192.168.1.1 failed: host is not on local network
I use this machine as a gateway between my ISP and my internal lan, with
192.168.0.* IPs. How do I find out what is trying to find
hi, is there anyway i can stop receiving these errors
Jul 10 10:00:40 web /kernel: arplookup 63.171.211.198 failed: host is not on
local network
Jul 10 10:02:37 web last message repeated 82 times
--
thx
john
___
[EMAIL PROTECTED] mailing list
http
David Fuchs wrote:
Ok, riddle me this:
/kernel: arplookup WWW.XXX.YYY.10 failed: host is not on local network
[ ... ] Static routes have been added to
force all communication *between* these two hosts to use the secondary
interfaces:
WWW.XXX.YYY.25's static route:
route add WWW.XXX.YYY.10
Ok, riddle me this:
/kernel: arplookup WWW.XXX.YYY.10 failed: host is not on local network
I've been seeing these messages in the messages log, so I've done some
additional tests and am now hunting for answers.
The curious part is, the host technically *is* on the local network.
It's a /24
On Wed, May 12, 2004 at 08:20:07AM +0800, John Lee wrote:
May 11 17:07:03 www /kernel: arplookup 63.223.76.1 failed: host is not on
local network
May 11 17:07:09 www /kernel: arplookup 63.171.211.198 failed: host is not on
local network
May 11 17:07:10 www /kernel: arplookup 63.167.125.251
Hi,
I keep getting flooded by these messages in /var/log/messages
anyway to stop my system from doing arplookup's.
Getting annoyed.
Am i being hacked or queried?
May 11 17:07:03 www /kernel: arplookup 63.223.76.1 failed: host is not on
local network
May 11 17:07:09 www /kernel: arplookup
Hello,
Our router has two networks assigned to it from our
provider, the NIC card on my server has IP addresses
assigned from both blocks of IP's.
Everything works great, however this message keeps
showing up in my log files:
Jan 23 13:51:46 rmd-cw0 /kernel: arplookup
12.xxx.xxx.xxx failed
On Thu, Nov 27, 2003 at 12:55:19AM -0500, Dragoncrest wrote:
[Warnings about ethernet addresses]
I'd like to know this too. I have a FreeBSD 4.8-RELEASE box that exhibits
the
same symptoms. The addresses it complains about belong to a colo box on our
network and a cisco router.
I'd like to know this too. I have a FreeBSD 4.8-RELEASE box that exhibits the
same symptoms. The addresses it complains about belong to a colo box on our
network and a cisco router.
That's a big Ditto for me too. I got the same problem on one of
my bsd workstations up at work too, but
I doesn't seem to show up on a regular base.
This is an example from a log file :
Nov 24 12:16:45 nira /kernel: arplookup 100.93.140.1 failed: host is not on
local network
Nov 24 12:17:40 nira /kernel: arplookup 100.93.140.1 failed: host is not on
local network
Nov 24 12:21:18 nira /kernel
Sorin Chiorean wrote:
I doesn't seem to show up on a regular base.
This is an example from a log file :
Nov 24 12:16:45 nira /kernel: arplookup 100.93.140.1 failed: host is not
on local network
Nov 24 12:17:40 nira /kernel: arplookup 100.93.140.1 failed: host is not
on local network
Nov 24
Sorin Chiorean wrote:
I doesn't seem to show up on a regular base.
This is an example from a log file :
Nov 24 12:16:45 nira /kernel: arplookup 100.93.140.1 failed: host is not
on local network
I've seen this when the IP number is not in the network defined by the
IP number and netmask
Sorin Chiorean [EMAIL PROTECTED] writes:
I installed a new FreeBSD 4.9 box and is running as a Firewall/NAT device
for a small network.
I am getting this error twice per day :
/kernel: arplookup 100.93.140.1 failed: host is not on local network
Everything works ok without any problems
Hi,
I installed a new FreeBSD 4.9 box and is running as a Firewall/NAT device
for a small network.
I am getting this error twice per day :
/kernel: arplookup 100.93.140.1 failed: host is not on local network
Everything works ok without any problems for all our workstations behind
this Firewall/NAT
on using an IP address of 192.168.1.0, but via DHCP it hands vx0
one of the IP addresses in the /29 that I have from my ADSL provider.
In dmesg I often see: arplookup 192.168.0.1 failed: host is not on local
network
Now obviously 192.168.0.1 isn't on the same network as xl0's 192.168.1.1
since xl0
In [EMAIL PROTECTED],
op de datum 2003-10-24 om 16:09, Bill Moran schreef:
arp:
Frequently I get this message on the first console:
arplookup 213.84.240.105 failed: host is not on local network
This means your network is configured strangely, although a lot of ISPs
seem to think
Peter Terpstra wrote:
In [EMAIL PROTECTED],
op de datum 2003-10-24 om 16:09, Bill Moran schreef:
arp:
Frequently I get this message on the first console:
arplookup 213.84.240.105 failed: host is not on local network
This means your network is configured strangely, although a lot of ISPs
seem
is always in /boot/kernel, so it's not really mentioned.
arp:
Frequently I get this message on the first console:
arplookup 213.84.240.105 failed: host is not on local network
This means your network is configured strangely, although a lot of ISPs
seem to think this is the way to do it.
I searched
-15m1kxku /kernel: arplookup xx.xx.xx.xx failed:
host is
not on local network
note: xx.xx.xx.xx looks like an ip on the same subnet as my box, ie.,
the first two octets are similar.
i can boot into freebsd, looks like i'm still receiving a network
connection, however - certain things now don't work
i rebooted my dual boot (with winxp), dhcp, 4.8-REL_ENG machine today,
and noticed for the first time some strange behavior.
i can boot successfully, but i notice recurring messages in
/var/log/messages, which read
Jul 5 21:04:23 hostname-15m1kxku /kernel: arplookup xx.xx.xx.xx failed
Hi all,
This question appears to have been asked before on several occasions, but I
haven't been able to find a fix using the information provided. I keep
getting the following in my log files:
/kernel: arplookup a.b.118.64 failed: host is not on local network
My system is sitting on a.b
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Sent: Wednesday, July 02, 2003 8:23 PM
To: [EMAIL PROTECTED]
Subject: kernel: arplookup error
Hi all,
This question appears to have been asked before on several occasions,
but I
haven't been able to find a fix using the information
:23 PM
To: [EMAIL PROTECTED]
Subject: kernel: arplookup error
Hi all,
This question appears to have been asked before on several occasions,
but I
haven't been able to find a fix using the information provided. I keep
getting the following in my log files:
/kernel: arplookup a.b.118.64 failed: host
Hi everyone, I'm getting some arplookup errors here which I think is the
cause of my name server not transferring zone files over to the slave
server.
Here is my scenario:
67.153.114.xx - gateway / nat / firewall / dhcpd server / dns server
(master for internal lan and slave for external
Darryl Hoar [EMAIL PROTECTED] writes:
thanks for the help.
I have verified that it is a test point on a piece of gear
on their internal network. So now, I only need to
ignore the arps.
If my external Nic (DSL side) is DHCP, how in freebsd
would I define an alias (10.1.1.1) for it ? I
Greetings,
I have posted several questions regarding an arplookup failure
message I have been receiving. I have google'd until my
eyes are falling out, and have found nothing that explains
how to FIX the problem.
I am running 4.7-stable on a box. It is my firewall, nat box.
ep0 is connected
On Fri, 14 Mar 2003 11:33:08 -0600
Darryl Hoar [EMAIL PROTECTED] wrote:
Greetings,
I have posted several questions regarding an arplookup failure
message I have been receiving. I have google'd until my
eyes are falling out, and have found nothing that explains
how to FIX the problem.
I
broadcast 24.225.23.255
ether 00:60:08:03:21:09
media: Ethernet 10baseT/UTP
-Darryl
On Fri, 14 Mar 2003 11:33:08 -0600
Darryl Hoar [EMAIL PROTECTED] wrote:
Greetings,
I have posted several questions regarding an arplookup failure
message I have been receiving. I have google'd
On Fri, 14 Mar 2003 11:43:11 -0600
Stephen Hilton [EMAIL PROTECTED] wrote:
On Fri, 14 Mar 2003 11:33:08 -0600
Darryl Hoar [EMAIL PROTECTED] wrote:
Greetings,
I have posted several questions regarding an arplookup failure
message I have been receiving. I have google'd until my
eyes
questions regarding an arplookup failure
message I have been receiving. I have google'd until my
eyes are falling out, and have found nothing that explains
how to FIX the problem.
I am running 4.7-stable on a box. It is my firewall, nat box.
ep0 is connected to my ISP's dsl. ep1
traceroute just gives
1. * * * *
2. * * * *
etc till you kill it. But ping works.
-Original Message-
From: Stephen Hilton [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2003 12:20 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Arplookup - what gives ?
On Fri, 14 Mar
, not including the firewall box.
I am getting
/kernel arplookup failure: 10.1.1.1 not on local network.
my ISP assigns a real IP to my ep0 interface usings dhcp.
what is causing this and how do I stop it ? I have added a
rule to block 10.x.x.x in, but it has not stopped the messages
Greetings,
I have a box with 4.7 installed on it. It is a firewall, and does
NAT.
I have the following appearing over and over on the console,
and in dmesg.
arplookup failure: 10.1.1.1 not on local network.
My internal LAN uses the 192.168.x.x private ip addressing.
My external interface
the following appearing over and over on the console,
and in dmesg.
arplookup failure: 10.1.1.1 not on local network.
My internal LAN uses the 192.168.x.x private ip addressing.
My external interface connects to my providers DSL using
DHCP. DHCP assigns an honest to goodness real IP address.
I can ping
on the console,
and in dmesg.
arplookup failure: 10.1.1.1 not on local network.
My internal LAN uses the 192.168.x.x private ip addressing.
My external interface connects to my providers DSL using
DHCP. DHCP assigns an honest to goodness real IP address.
I can ping 10.1.1.1. If I ifconfig ep0 down
On Sun, Feb 16, 2003 at 06:47:47PM +0100, Marc Schneiders wrote:
Date: Sun, 16 Feb 2003 18:47:47 +0100 (CET)
From: Marc Schneiders [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: arplookup going mad
I have posted a question about this earlier, without getting an
answer. Then the problem
Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is
not on local network
Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for
13.16.2.97rt
I had this back in the summer time, and it was due to having an IP
address aliased on one of my nics in a block
On Mon, 17 Feb 2003, at 16:43 [=GMT-0500], IAccounts wrote:
Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is
not on local network
Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for
13.16.2.97rt
I had this back in the summer time, and it was due
/kernel: arplookup 213.196.2.97 failed: host is
not on local network
Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for
13.16.2.97rt
Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is
not on local network
Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo
I recently added some aliases to my ipconfig and now I'm getting these
system messages? Should I be concerned? (FreeBSD 4.6)
Feb 3 02:24:23 freedom /kernel: arplookup XXX.XXX.XX.XX failed: host is
not on local
network
Feb 3 00:17:35 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed:
1
mailing list said:
I recently added some aliases to my ipconfig and now I'm getting these
system messages? Should I be concerned? (FreeBSD 4.6)
snip
ifconfig_de0=inet XXX.168.0.219 netmask 255.255.255.0
ifconfig_tl0=inet XXX.82.15.219 netmask 255.255.255.240
snip
]
Cc: [EMAIL PROTECTED]
Subject: Re: arplookup messages? now what have I done?
mailing list said:
I recently added some aliases to my ipconfig and now I'm
getting these
system messages? Should I be concerned? (FreeBSD 4.6)
snip
ifconfig_de0=inet XXX.168.0.219 netmask
mailing list\ said:
Hi Michael,
My network topology skills are limited... does this mean the following:
- my default gateway is on a 255.255.255.240 subnet
- so is my devices real address
- there is another device listed there (de0), no problems (internal)
So, if I change the aliased
Hmmm, I'm confused
If you want to have your aliases attached to the tl0
interface, you need to use addresses in that range. So,
something like:
ifconfig_tl0_alias3=inet XXX.82.15.210 netmask 0x
That's what I have, and I'm getting those funny arplookup error
messages
On Tue, Feb 04, 2003 at 08:15:04AM +0100, Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2003-02-01 18:55:23 -0800:
On Sat, Feb 01, 2003 at 05:20:53PM -0500, Stephen D. Kingrea wrote:
tcpdump tells me that incoming smtp requests are generating these
messages at the same time as recieving
turns out that the file /etc/mail/local-host-names was not properly
configured.
damn! it is so galling when one misses the simplest things!
stephen
On Sat, 1 Feb 2003, Nathan Kinkade wrote:
On Sat, Feb 01, 2003 at 05:20:53PM -0500, Stephen D. Kingrea wrote:
tcpdump tells me that incoming
# [EMAIL PROTECTED] / 2003-02-01 18:55:23 -0800:
On Sat, Feb 01, 2003 at 05:20:53PM -0500, Stephen D. Kingrea wrote:
tcpdump tells me that incoming smtp requests are generating these
messages at the same time as recieving mail. i am pretty sure that
either sendmail or ipfw rules is the
:26 PM
Subject: Re: arplookup 0.0.0.0
is there a way to suppress the message itself? i seem to be getting it
quite often, and really just started after configuring and activating
sendmail. i suspect that there is a possible misconfiguration involving
sendmail itself, but mail seems
On Sat, Feb 01, 2003 at 05:20:53PM -0500, Stephen D. Kingrea wrote:
tcpdump tells me that incoming smtp requests are generating these
messages at the same time as recieving mail. i am pretty sure that
either sendmail or ipfw rules is the cause...
any good tutorials out there on interpreting
hope one of youse can help with this...
i am suddenly and inexplicably getting the message:
www /kernel: arpresolve: can't allocate llinfo for 0.0.0.0rt
www /kernel: arplookup 0.0.0.0 failed: host is not on local network
nothing seems affected, that is to say that everything works as
advertised
I've 2 DNS servers that are in different subnet. My freeBSD4.6.2 server is
master and the other one is slave. Slave server connects to My freeBSD
server for DNS updates but always FreeBSD gives the message:
/kernel: arplookup x.x.x.x failed: host is not on local network
How can I prevent
Hello.
Any idea what can cause this?
Oct 14 16:48:29 agape /kernel: arplookup 206.30.56.1 failed: host is not on
local network
I'm running FreeBSD 4.6.2 with native sendmail upgraded from 4.4.x. It's an
SMP machine.
I'm absolutely stumped. We've got a lot of virtual hosts with IP aliases
to throw arplookup failures? Any ideas
for a solution?
Thanks!
On Tuesday 15 October 2002 09:24, Matthias Trevarthan wrote:
Hello.
Any idea what can cause this?
Oct 14 16:48:29 agape /kernel: arplookup 206.30.56.1 failed: host is not on
local network
I'm running FreeBSD 4.6.2 with native
-0500, Chris Byrnes wrote:
My /var/log/messages is being filled, non-stop, by these errors
looped:
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed:
host is not on local network
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed:
host is not on local
:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed:
host is not on local network
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed:
host is not on local network
After doing some reading, I've already issued, sysctl -w
net.link.ether.inet.log_arp_wrong_iface=0
Chris Byrnes wrote:
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed: host is
not on local network
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed: host is
not on local network
After doing some reading, I've already issued, sysctl -w
Crist J. Clark [EMAIL PROTECTED] probably said:
This is a netmask problem, but not really the one that other people
have described. This is how it usually works. Your troubled machine
above, servername, receives an ARP who-has from another machine on
the LAN called clientname. However, the IP
I get these errors generated on a machine which has the correct
netmask, no static routes, no incorrect routes of any kind.
During a migration there are multiple IP networks on the same physical
switched network, if I connect to one of the machines in the other
network on the same wire,
98 matches
Mail list logo
