Hi Peter,
i'm having exactly the same problem, but without NAT configuration. Just
a simple host on network 192.168.170.xxx
that when tries to reach an host on 192.168.181.xxx: it gives the same error
arplookup 192.168.181.253 failed: host is not on local network
The funny thing is that IP connection works anyway. The problem is
present only when trying to reach network
192.168.181.xxx, which is absolutely not on local network.
The problem started with freebsd 5.3 and today, with 7, it is still present.
Daniel
Peter Jeremy ha scritto:
I'm occasionally seeing pairs of messages like the following on
my NAT host:
arplookup 192.168.181.114 failed: host is not on local network
arpresolve: can't allocate route for 192.168.181.114
In my particular configuration, there are dual subnets between the NAT
and target host. My initial assumption was that the request was
arriving on the other subnet and I added if_xname to the arplookup
printf() - but that shows that interface matches the IP address.
I've looked back through the mailing lists but the previous reports
of this problem don't match my scenario.
I've seen this with FreeBSD 5.3, 6.2 and 7.0.
The (in)frequency of the problem makes me wonder if it's actually a
resource exhaustion problem.
Has anyone got any suggestions?
--
WBR,
Cordiali Saluti,
Daniel Ponticello, VP of Engineering
Network Coordination Centre of Skytek
---
- For further information about our services:
- Please visit our website at http://www.Skytek.it
---
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
