Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: dom0 broadcasts



On Thu, Feb 07, 2008 at 02:41:15PM +1100, Sarton O'Brien wrote:
> Keeping it as simple as possible ...
> 
> Broadcast ping from a domu:
> symbiote# ping 192.168.x.255
> PING 192.168.x.255 (192.168.x.255): 56 data bytes
> 64 bytes from 192.168.x.9: icmp_seq=0 ttl=255 time=0.042 ms
> 64 bytes from 192.168.x.8: icmp_seq=0 DUP! ttl=255 time=0.642 ms
> 64 bytes from 192.168.x.7: icmp_seq=0 DUP! ttl=255 time=0.838 ms
> 64 bytes from 192.168.x.6: icmp_seq=0 DUP! ttl=255 time=1.038 ms
> 
> Broadcast ping from dom0:
> gogeta# ping 192.168.x.255
> PING 192.168.x.255 (192.168.x.255): 56 data bytes
> 64 bytes from 192.168.x.10: icmp_seq=0 ttl=255 time=0.076 ms
> 64 bytes from 192.168.x.8: icmp_seq=0 DUP! ttl=255 time=0.924 ms
> 64 bytes from 192.168.x.9: icmp_seq=0 DUP! ttl=255 time=1.002 ms
> 64 bytes from 192.168.x.7: icmp_seq=0 DUP! ttl=255 time=1.085 ms
> 64 bytes from 192.168.x.6: icmp_seq=0 DUP! ttl=255 time=1.168 ms
> 
> With x.10 being the IP address of dom0.
> 
> Why doesn't dom0 respond to a broadcast from a domu?
> 
> TIA for _any_ information :)

I suspect a bridge issue. Do you have ipfiler enabled in dom0 ?
What does a tcpdump on dom0 (on various involved interfaces) show ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--



Home | Main Index | Thread Index | Old Index