Hi, The message "File exists" simply indicate that you already have a default route. Your default route points to another interface (eth1), therefore that's the interface you need to use instead of eth0.
I see that your interface is part of the 109.106.8.0/22 network, which happens to be a public Ukrainian network. In my previous mail I assumed you are in a private LAN (with plenty of addresses available to you), but if you are connected directly to a public network, and have the right to only 1 IP, then bridging your FreeDOS system is not the way to go, because it would require to have its own (public - in your situation) IP address. Making it work in such situation is much more tricky than a simple bridge, since you need to share your single (public) IP between two hosts (your real host, and the freedos virtual machine). This means you need to configure your Linux OS to act as a router for the virtual machine, and make it use a masquerade to hide the FreeDOS system behind your public IP. The whole thing is extensively described below: http://wiki.qemu.org/Documentation/Networking/NAT Of course if you have the right to use 2 public IPs in your network, then things become simple again (but I doubt your ISP allows that, esp. since the IPv4 pool is empty nowadays). You might want to consider an easier hypervizor, as you seem to be unfamiliar with networking concepts, setting up a DHCP server, DNS server, routing and NAT will be for sure a painful experience. I would recommend VirtualBox - it uses the same principles (bridging & NAT & routing etc), but hides the whole complexity away from the user. All you'd have to do then is check one checkbox 'NAT' in the networking preferences of your VM. About gpxe: I don't think it will be of any help to you. PXE is about booting a machine over the network - it's used mostly by thin clients, or for upgrades of some appliances (voip phones..). Of course one could use PXE to boot FreeDOS over the network, but I don't really think it's what you are up to. Mateusz On 06/20/2013 07:46 PM, sakura kinomoto wrote: > Mr. Mateusz Viste! > > Thank you very much for answer! > > I installed packages "uml-utilities" and "bridge-utils" > > do all as you say: > > when I type: > > root@109:/home/kitty# ip route add default via 192.168.0.1 > RTNETLINK answers: File exists > > I was not sure, but I type: > > root@109:/home/kitty# ifconfig add default via 192.168.0.1 > SIOCSIFADDR: No such device > add: ERROR while getting interface flags: No such device > via: Unknown host > ifconfig: `--help' gives usage information. > > > I am not sure, but I also try with different IP: > > > root@109:/home/kitty# ip route add default via 192.168.0.12 > RTNETLINK answers: File exists > > > .... > .... > (stubborn and persistent script :) > > root@109:/home/kitty# ip route add default via 192.168.0.254 > RTNETLINK answers: File exists > > root@109:/home/kitty# ip route add default via 192.168.0.255 > RTNETLINK answers: Invalid argument > > root@109:/home/kitty# ip route add default via 192.168.1.0 > RTNETLINK answers: No such process > > and qemu still have not network > > > ! but, after my messages, I was trying to run "gpxe" (utility to > linux-network booting). target - try to see Qemu ip-netmask-gateway.... > please, tell me, how this "gpxe" have possibility to connect network? here is > screenshot - http://http://imm.io/19OC4 > > > And, probably, you need more info: > > root@109:/home/kitty# cat /etc/udev/rules.d/70-persistent-net.rules > # This file was automatically generated by the /lib/udev/write_net_rules > # program, run by the persistent-net-generator.rules rules file. > # > # You can modify it, as long as you keep each rule on a single > # line, and change only the value of the NAME= key. > > # PCI device 0x10ec:0x8139 (8139too) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:11:2f:82:eb:62", ATTR{dev_id}=="0x0", ATTR{type}=="1", > KERNEL=="eth*", NAME="eth0" > > # PCI device 0x10ec:0x8029 (ne2k-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:00:21:f8:bf:21", ATTR{dev_id}=="0x0", ATTR{type}=="1", > KERNEL=="eth*", NAME="eth1" > root@109:/home/kitty# cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth1 > iface eth1 inet dhcp > root@109:/home/kitty# netstat -rn > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt Iface > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 > mybridge > 109.106.8.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 > 0.0.0.0 109.106.8.1 0.0.0.0 UG 0 0 0 eth1 > root@109:/home/kitty# > > > If it will be more simple way, for you, I can give you ssh-access in private > message? > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Freedos-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-user > ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
