I just left an arpsend job running in cron every 5 minutes.
I tried that too, called it "garpd" But it didn't really help and
eventually I stopped doing it.
I've also had something like this happen when the firewall (wrongly)
had an alias that was the same as the IP of a virtual node.
Yeah
On Sat, Feb 20, 2010 at 09:24:09AM -0800, Gregor at HostGIS wrote:
>> It sounds like the switches they're attached to don't have the right
>> arp information.
>
> Kinda what I thought, but why?
Actually yeah, when I read your other messages in the thread and realized
it was only on some hosts, thi
Are you using the veth or vnet drivers? If it's vnet, I don't have a
clue. I depend on IPv6 for a lot of things and vnet is not IPv6
veth
Though it's IPv4, not 6. And it's very vanilla: static IPs in all VEs,
no DHCP or SMB services at all.
Often it's very transitive. Bridges tend to
"st
It sounds like the switches they're attached to don't have the right
arp information.
Kinda what I thought, but why?
Make sure proxy_arp is enabled, the sysctl is something like:
net.ipv4.conf.eth1.proxy_arp = 1
Yep:
net.ipv4.conf.lo.proxy_arp = 0
net.ipv4.conf.all.proxy_arp = 0
net.ipv4.co
On Fri, Feb 19, 2010 at 08:51:23PM -0800, Gregor at HostGIS wrote:
> Any ideas as to what could have caused this "outage" in the first place,
> and why sending a ping would have fixed it?
It sounds like the switches they're attached to don't have the right
arp information.
Make sure proxy_arp i
On Fri, 2010-02-19 at 20:51 -0800, Gregor at HostGIS wrote:
> Well, guys, here's a weird one. I fixed it, but you won't believe how.
> I used "vzctl enter" to enter the VE, then "route -n" to see its
> gateway. Then ping the gateway, and it worked; skipped 1-2 pings, but
> the pings came back a
Any ideas as to what could have caused this "outage" in the first place,
and why sending a ping would have fixed it?
I can supply some further info, which may be useful.
* The bonding driver is in use, slaving eth0 and eth1 into bond0.
* There are 2 switches. eth0 goes into one and eth1 into t
Well, guys, here's a weird one. I fixed it, but you won't believe how.
I used "vzctl enter" to enter the VE, then "route -n" to see its
gateway. Then ping the gateway, and it worked; skipped 1-2 pings, but
the pings came back and the VEs were once again visible on the Internet.
Weird, huh?
T
