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

Re: [Xen-users] confused: How to put packetfilter into domU and isolate dom0 completely?



Hi,

> the fancy network-bridge script. My current problem is, eth0 is still
> visible from dom0 and I cannot get rid off it. Maybe I'm stopped by not
> understanding the peth0 and veth0 business here.
> Anyone can tell me roughly how to achieve a solution here?

You have a good explanation about virtual and physical network interfaces
in the wiki: http://wiki.xensource.com/xenwiki/XenNetworking

If I'm not wrong, in a network-bridge setup, peth0 interface is the
physical NIC (the original eth0) and eth0 is a virtual NIC.

The vethX interfaces are Dom0 virtual interfaces directly linked to the
vif0 .X interfaces.

The vifX.Y and pethX interfaces are assigned to bridges.

> give me the correct words to use in search engines? I've seen
> pciback.hide for the dom0 kernel, but how can I make certain that the
> filtering domU will get that card?

I have done this. First, you have to know the PCI ID of the NIC, you can
get this with the lspci command. Second, you have to tell the PCI ID to
the kernel, you can indicate this with the pciback.hide parameter. Third,
you assign the PCI ID to the VM with the pci parameter in the VM config
file.

The hidden NIC doesn't appears in Dom0, you won't see it with ifconfig,
and it will be available in the DomU that the NIC was assigned to.

I only have a problem with this, if I hide eth3 to Dom0 and assign it to a
DomU, I see the interface in the DomU as eth3 not as eth0... how can I
rename it? with the "ip link set name" command?

Bye.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.