|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] peth0 received packet on own address
Ian Pratt wrote:
We shouldn't be doing all of those things (peth0) on the
guest OSs - we had gone to some pains to make sure the MAC
was unique across the system - have we regressed in that due
to the -xen kernel or some other reason?
It's the internal vifX.X interfaces that have the fe:ff:... addresses.
There really is no business for any of these interfaces to be sourcing
packets at all.
Is there an option to the 'ip' tool when bringing the interface up to
prevent the ipv6 router solicitation?
The ip tool mostly configures the settings on the
card, and most of these are network protocol functions
which merely get initiated once the interface comes
up - they are mostly controlled by sysctl kernel
parameters. So, for instance, setting
/proc/sys/net/ipv6/conf/$interface/autoconf = 0
will turn off most of that. However, the /proc
entry for the device is only created when we
register the device, and the MLD and routing
functions get initiated only when we designate
the interface state as UP. Somewhere in between
performing those two steps, we should turn off
those sysctl vars.
Will test that today..
thanks,
Nivedita
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|