search for: vifu

> Hi. what creates veth0 and vifu.0, when? what''s the > underlying architecture behind them? Just trying to > understand the internals. netback/loopback.c creates them. It''s effectively a point to point link, allowing domain 0 to connect on to the bridge in the same manner that other domains do. (befor...

...is myself, but now as far as I can tell, > > veth0 (renamed to eth0 in the v recent releases) is the virtual nic > > for dom0 which corresponds to the virtual eth0 nics in the > domU''s (the > > physical nic itself has been renamed to peth0). > > > > The vifU.N''s are the dom0 links to the virtual nics ethN in > domU, and > > aren''t to be treated as proper network interfaces in thier > own right. > > If you assign an IP address to, say, vif1.0 and attempt to > communicate > > with eth0 in dom1, you can p...

> > When you run xend it runs network-bridge which creates the bridge, > > renames eth0->peth0 and veth0->eth0 and brings the new eth0 back up. > > kewl, thx Ian. i see network-route doesnt do this. i think > thats a good thing. do you forsee that changing? I expect that in most routed configurations people use their own network script rather than using the

Hi to the ML. I''m new to VLAN configuration, and combining it to XEN is a bit difficult. I want to use VLAN because it''s possible to "arping" from a domU to an other, and VLAN looks like; the only solution to prevent that. May be I''m wrong if someone got a solution, I may be interrested. I''ve also tryed ebtables, but nothing to prevent arp