Tag Info

Hot answers tagged

11

Preliminaries This following worked for me for Ubuntu 12.04. You should disable your computer's firewall as you test this so it won't interfere. The /etc/default/qemu-kvm file should be as originally installed. You will need to have bridge-utils qemu-kvm and libvirt-bin installed. Any users using virtual machines should be added to the libvirtd group. ...


10

The NAT connection needed to be selected with the hardware being: AMD PCNet FAST III (Am79C973, the default) This works with almost any OS (as mentioned on the Virtualbox help page). The Intel setting for some reason did not work. For Network setups with heavy router settings, you may have to use Bridged option with "PCNet FAST III" as the default.


8

If both interface are configured in /etc/network/interfaces you can use sudo ifup eth0 to bring eth0 up and sudo ifdown eth0 to take eth0 down


6

So you want something like this? +------------+ +---------------+ +--------+ Rest | DVD player |<-- wired -->| Ubuntu Bridge |<-- wifi -->| Router |<--> of the +------------+ +---------------+ +--------+ network You can do this easily with Firestarter. On your Ubuntu machine, install ...


6

I've been working on this issue for a while now. I am running 12.04 LXC 0.7.5 on the host and a mixture of 12.04 and 11.04 in the containers. I had zero success with editing: /run/networking/ifstate as it seems to not persist after a container is restarted. I solved the problem by commenting out the following line of the containers config file: ...


5

The following answer repeats much of the information in the Links below                                                          LXC Containers are a lightweight virtualization technology. They are more akin to an enhanced chroot than to full virtualization like Qemu or VMware, both because they do not emulate hardware and because containers share the same ...


5

Your ip should be on the br0, eth0 won't have an ip. Something like this : # 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 auto eth0 iface eth0 inet manual auto br0 ...


5

I think that daemonlogger will do want you want. It is capable of operating in two modes: sniffing packets and logging them directly to disk (files are automatically rolled over after 1GB of data), or in a "soft-tap" mode where it mirrors packets on another interface. It is is the repository, so sudo apt-get install daemonlogger will ...


4

I'm not sure about how to do this without clobbering NM, but it is possible to run automatically at boot and get IP addresses to assign easily (at least I have managed this with the same wireless card). This requires the packages hostapd and dnsmasq (not dnsmasq-base) /etc/hostapd/hostapd.conf: interface=wlan0 driver=nl80211 # This works on my TL-WN722N ...


4

Okay, this is how I got around the problem: 1. Remove Network Manager sudo apt-get remove network-manager note: read the end of this post for a disclaimer 2. Set up pptp on the command line We'll use a handy tool called pptpsetup that sets up all the needed config files for us. Run: sudo pptpsetup --create $your-connection --server se.rv.er.ip ...


3

Unfortunately, I keep answering my own questions aparently. But just to share with others.. Bridge + openvpn works BUT internal network only. AND has an odd bug that openvpn re-connects it self making multiple TAP devices (I use tap method). In the end i solved my problem this way: go back to the normal Network management - default system stuff. Add an ...


3

First, forget virbr0 -- that's added by libvirt and is irrelevant. For an "all-in-one" Openstack server with one NIC, there should be no need for another aliased virtual interface. As discussed in the Openstack guide, you should bridge br100 to your public IP address (eth0), and let Nova create instances and bridge them to br100. e.g. add the below to ...


3

You have to remove interfaces from the vbridge before it can be deleted. These commands should do it: killall hostapd brctl delif br0 eth0 brctl delif br0 wlan0 ifconfig br0 down brctl delbr br0 service networking restart


3

Lubuntu comes with Network-manager, which makes this very easy. Click on the network icon in your panel, and select Edit connections. In the dialog that appears, select the wired interface and click Edit. In the IPv4-settings pane in the new dialog, you can select Method: "Shared with other computers". Any internet connection will now be shared on your ...


3

Normally I use sudo ifdown eth0 && ifup eth1 sudo ifdown eth1 && ifup eth0 The 1st stops eth0 and starts eth1 and the second does it the other way around.


3

Yes, that is what you need to do. Sharing an internet connection using Network Manager will setup the sharer as a DHCP server, etc, which is not what you want. You can read how to do it here: http://manpages.ubuntu.com/manpages/lucid/en/man5/bridge-utils-interfaces.5.html


2

The guest-Ubuntu configuration shouldn't need to change. At all. A guest OS is given a virtual network connection based on what the host machine makes available. The only changes that need to happen are to the VM settings so it knows to bridge to your wireless connection instead of the previously wired connection. Shut down the guest Load the Virtualbox ...


2

Most trouble occurs because of the Broadcom drivers in HP Laptops at least. If you have a broadcom network controller Check if your card is compatible with b43(link 1). If it is, awesome, keep reading. The default Broadcom sta driver (wl) will not support access point mode. So install b43 taking precautionary measure to be online by any means necessary. Turn ...


2

When you are logged in: Go to Network menu in the panel. Navigate to "Edit connections". When that window opens, select "Auto eth0", and press "Edit" (This assumes that you are connected to the Internet on some other port, for example wlan0 using wireless). A new window will open. Navigate to the tab titled "IPv4 Settings", and change the Method to "Shared ...


2

These are the two scripts I use to create a bridge for qemu-kvm. First, let the host become a IP router. Script ip-router.sh: #!/bin/bash internetinterface="eth0" username=`whoami` if [ "x$username" != "xroot" ] ; then echo echo "You must be root in order to run this script..." echo exit fi if [ "x$1" != "x" ] ; then ...


2

I've had the same problem. Also the vnc packages is also never installed. It seems to me that the charms is not fully functioning, or i may be missing something... However i made it work by setting up the networking my self. Created a bridge 'br100' and made sure the interface linked to the bridge was set for promiscuous mode. This has to be done on ...


2

In the end I ended up just creating an interface and forwarding packets over it with some iptables rules, which seems to be working for me. This does NOT use the 'bridge' option that all the tutorials seem to suggest so I don't know if there is a fatal flaw? auto lo iface lo inet loopback auto xenbr0 iface xenbr0 inet static bridge_ports none ...


2

NetworkManager tries to manage eth0 because eth0 is not configured in /etc/network/interfaces. To cause NetworkManager not to touch eth0, add the following stanza to /etc/network/interfaces. iface eth0 inet manual If you aren't using NetworkManager then you can safely remove network-manager. By the way, there's an easier way to configure bridges in ...


2

If you want to bridge connections you need bridge-utils. Create a virtual bridge: root@bridge:~> brctl addbr br0 Add interfaces: root@bridge:~> brctl addif br0 eth0 root@bridge:~> brctl addif br0 eth1 Bounce them: root@bridge:~> ifconfig eth0 down root@bridge:~> ifconfig eth1 down root@bridge:~> ifconfig eth0 up root@bridge:~> ...


2

You are right something is trying to point lxcbr0. Use lxcbr0 in these files /etc/default/lxc /etc/lxc/default.conf /etc/network/interfaces I tried br0 it give me the same error. After changing existing bridge to lxcbr0 that I worked fine.


1

If you're using VMware all you need to do is assign these virtual machines to a virtual LAN that has not connection with VMware itself nor the host machine. This is called "LAN segments" and it's easy to find under the Network Interface settings of each machine. All you have to do is create a new LAN segment for the first machine, then add the other ones ...


1

Any type 2 hypervisor will be already having virtual networks of multiple types (bridged, host only, internal network). Bridged: VM will be attached to your physical NIC as your host do, and will acquire IP from DHCP -if enabled. Host only: VM can only communicate with HOST and not beyond that (Option should have been enabled when you were installing ...


1

br0?!!! seems to me like you created a bridged connection on the host OS (Ubuntu), Which not the correct way. (misleading similar names?) Instead go VirtualBox, Select your Guest machine: Settings → Network Check Enable Network Adapter, Set attached to Bridged Adapter, Select Name of your network interface connected to same network of other client. ...


1

I was able to solve this issue from the VMware side without the use of routers/bridges. I basically had to attach the internal NIC of each pfSense, to NIC2 from each host, to create one joined broadcast domain that spanned the 2 hosts.


1

Manual methods are unlikely to work correctly if Network Manager is installed and running. If it is installed, it is advisable to set the details there: http://i.stack.imgur.com/j4OPN.png If you have removed Network Manager, your interfaces file will also need a gateway and DNS nameservers: auto lo iface lo inet loopback auto eth0 iface eth0 inet static ...



Only top voted, non community-wiki answers of a minimum length are eligible