1

I'm running Debian Wheezy with Gnome-Shell. My current network interface configuration is this:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

# Bridge setup
# allow-hotplug br0
auto br0 
iface br0 inet static
  address 192.168.0.1
  netmask 255.255.255.0
  bridge_ports none
  bridge_stp off 
  bridge_fd 0
  bridge_maxwait 0

I'm using br0 for virtualisation.

My problem is now that I'm losing the support of Network-Manager for eth0. So I can't use the OpenVPN plugin anymore to quickly connect to my VPN.

Has anyone done such a setup and knows how to configure this proper?

2 Answers 2

1

A couple of things,

  1. you didn't bind your bridge to a device
  2. Your still attempting to use you Ethernet device normally

try this: -

# vim /etc/network/interfaces

#The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual      # set pass through and use br0 for networking

# Bridge setup
allow-hotplug br0
auto br0 
iface br0 inet static
  address 192.168.0.1
  netmask 255.255.255.0
  network 192.168.0.0
  broadcast 192.168.0.255
  gateway 192.168.0.254    # make sure this gateway address is correct
  bridge_ports eth0        # bind to device here
  bridge_stp off 
  bridge_fd 0
  bridge_maxwait 0
3
  • That's true. I forgot to mention that I would still like to be able to run dhcp on my eth0. It's a laptop and it would be pain if I go into another office and has to configure manually eth0 Aug 16, 2013 at 9:12
  • 1
    Thats fine, you can do this by setting br0 to be 'dhcp' and remark out address, netmask, network, broadcast and gateway. to run bridge you will need to leave eth0 as a pass through (bridged device) and usebr0 as your active network device. Aug 19, 2013 at 6:04
  • I just noticed i had "allow-hotplug br0" as remarked out, now fixed. Aug 19, 2013 at 6:07
0

This is a known bug that still affects Ubuntu 14.04, but is fixed in 14.10. See: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201

Debian is upstream from Ubuntu, and I assume (but am not certain) that this issue would be in upstream of network-manager too.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .