On Tue, Mar 15, 2005 at 11:14:11PM +0100, Juan RP wrote: > > Hi, I have a domU running perfectly now, but the network still does not > work, so I have a few questions: > > o Does the dom0 kernel needs ipfilter/pf and bridge for this? (something > more?) > > I'm using this line in the nbsd file to create domUs: > > vif = [ 'mac=aa:00:00:50:02:f0, bridge=10.0.0.254 netmask 255.255.255.0' ] > > and my dom0 now has created the interface: > > xvif9.0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu > 1500 > address: aa:00:00:51:02:f0 > inet 10.0.0.254 netmask 0xffffff00 broadcast 10.0.0.255 > inet6 fe80::a800:ff:fe51:2f0%xvif9.0 prefixlen 64 scopeid 0x4 > > I'm using DHCP in dom0, my gateway is 192.168.1.1, DNS is assigned via DHCP, > so my next > question is: what values do I have to use in domU to have the network working? > (I want to mount some NFS shares). sysctl -w net.inet.ip.forwarding=1 should be plenty enough. After that, it really depends on the topology of your network. FWIW, this afternoon when I could take a try at booting a domU, I used a modified vif-bridge script to do bridging by doing this: vif = [ 'mac=lalala, bridge=bridge:bridge0:fxp0' ] The meaning of the bridge parameter is the following: first it starts with bridge to distinguish between plain ifconfig case and bridge case, then it bridges the vif interface with fxp0 on bridge0, creating it if necessary. I'll send it tomorrow if you want. BTW, xentools20 package needs some work (and should include such a script). Also, it really needs to default to 127.0.0.1 for the relevant daemonized parts, I've patched mine for that. I'll have a closer look at this during the next few days. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "When I find the controls, I'll go where I like, I'll know where I want to be, but maybe for now I'll stay right here on a silent sea." KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
Attachment:
pgplEIn8LHjdB.pgp
Description: PGP signature