Page 1 of 1
Bridging with 2.2.2 ?
Posted: 20. Jul 2009, 21:19
by Sirdonkeypunch
ive done some trolling on the forums for a while trying to find my answer. i was running 3.0.0 on mandriva 2009.1 and well..... it actual virtualization worked great...... the networking however..... not so much. so after 5 days of messing up my host eth0 trying to bridge and tap and all that jazz, i learned from these forums that in 2.2.2 you can just select Bridged Network on the network interface portion of the virtual machine.... i was exstatic.....until it didnt work. i was running backtrack inside of the VM so i ran a sudo dhclient eth0 to get the net interface up and it just gives me
Code: Select all
f**k@PwnSauce:sudo dhclient eth0
[sudo] password for f**k:
There is already a pid file /var/run/dhclient.pid with pid 10772
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/08:00:27:e3:1c:c1
Sending on LPF/eth0/08:00:27:e3:1c:c1
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
so im thinking i need to tell the host (my mandriva 2009.1) that it should be awaiting a bridged connection somehow. going thru the forums i havent found anything of assistance, and ive been everywhere on google tracking down people with the same problem but its all outdated. uml-utilities and bridge-utils are installed from when i made my attempt at bridging with 3.0.0.
i knew it couldnt be as easy as just selecting "Bridged Connection" from the dropdown menu.....
Re: Bridging with 2.2.2 ?
Posted: 20. Jul 2009, 23:07
by Sasquatch
When using bridged networking, you have to select the proper Host NIC you want to use. It's not going to work if you select your Host wired NIC if you use Wireless. How do you expect water coming out of the tap, if it's not connected to the main water system. So check the config again.
Re: Bridging with 2.2.2 ?
Posted: 20. Jul 2009, 23:09
by Sirdonkeypunch
Sasquatch wrote:When using bridged networking, you have to select the proper Host NIC you want to use. It's not going to work if you select your Host wired NIC if you use Wireless. How do you expect water coming out of the tap, if it's not connected to the main water system. So check the config again.
eth0 is the network connection for the host......
its not like im using a wireless interface and trying to get it to communicate to a wired one.
so im still at odds with this.... and chapter 6 of the user manual offered no such solace
Re: Bridging with 2.2.2 ?
Posted: 20. Jul 2009, 23:10
by Sasquatch
Then at least give the full config of your network, both Host and Guest. Are you actually running a DHCP server on the physical network?
Re: Bridging with 2.2.2 ?
Posted: 20. Jul 2009, 23:44
by Sirdonkeypunch
Code: Select all
HOST :
[root@localhost jesus]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0B:DB:11:34:4A
inet addr:75.129.103.191 Bcast:255.255.255.255 Mask:255.255.252.0
inet6 addr: fe80::20b:dbff:fe11:344a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1582013 errors:0 dropped:0 overruns:0 frame:0
TX packets:197713 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:491035485 (468.2 MiB) TX bytes:17500489 (16.6 MiB)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1000 (1000.0 b) TX bytes:1000 (1000.0 b)
-----------------------------------------------------------------------------
/etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 24.247.15.53
nameserver 24.247.24.53
search gha.chartermi.net
now for the guest
Code: Select all
f**k@PwnSauce:~$ sudo dhclient eth0
[sudo] password for f**k:
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/08:00:27:e3:1c:c1
Sending on LPF/eth0/08:00:27:e3:1c:c1
Sending on Socket/fallback
DHCPREQUEST of 10.0.2.15 on eth0 to 255.255.255.255 port 67
DHCPREQUEST of 10.0.2.15 on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
Trying recorded lease 10.0.2.15
PING 10.0.2.2 (10.0.2.2) 56(84) bytes of data.
--- 10.0.2.2 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
No working leases in persistent database - sleeping.
f**k@PwnSauce:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:e3:1c:c1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:4545 errors:91 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:293998 (293.9 KB) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0xc020
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:112 (112.0 B) TX bytes:112 (112.0 B)
f**k@PwnSauce:~$ cat /etc/resolv.conf
domain gha.chartermi.net
search gha.chartermi.net
nameserver 24.247.24.53
nameserver 24.247.15.53
f**k@PwnSauce:~$
im not normally keen on setting up the dhcp server and stuff like that. hope this gives you enough info to work with, if not please let me know, i feel like im so close yet so far away from solving this problem thats taken up over 40 hours of my time. in any case i express to ya great gratitude and thanks. i look forward to reading the reply
Re: Bridging with 2.2.2 ?
Posted: 21. Jul 2009, 20:15
by Sasquatch
Ah, now I see. You want to use your direct internet connection as a bridge. That will never work, because your ISP only provides ONE IP address, because they are already short on them. There is no way to get this working the way you want, unless you put a router between the Host and the internet connection. You have to use NAT to get internet on the Guest, and if you need two way communication between the Host and Guest, add a second NIC with Host-Only. You do have full access to the Host with NAT, by using the IP 10.0.2.2.
Re: Bridging with 2.2.2 ?
Posted: 21. Jul 2009, 22:34
by Sirdonkeypunch
Sasquatch wrote:Ah, now I see. You want to use your direct internet connection as a bridge. That will never work, because your ISP only provides ONE IP address, because they are already short on them. There is no way to get this working the way you want, unless you put a router between the Host and the internet connection. You have to use NAT to get internet on the Guest, and if you need two way communication between the Host and Guest, add a second NIC with Host-Only. You do have full access to the Host with NAT, by using the IP 10.0.2.2.
ahh yes, this is what i figured was the problem, unfortunately i must wait till august first before a cohort will give me a cisco 24port switch.
will the switch be able to suffice or must it be a routing device?
Re: Bridging with 2.2.2 ?
Posted: 21. Jul 2009, 22:46
by Sasquatch
A switch is a dumb device that only throws packets through the right port, nothing more. It does nothing to provide internet access to more than one machine. It HAS to be a router, as you will be creating a NAT network. Check
http://en.wikipedia.org/wiki/Network_Ad ... ranslation for more information on that matter.