Where are all the network-bridges coming from, ifconfig shows me?Dual NIC not workingCannot find device “eth0”. Failed to bring up eth0Pages loading too long on new router (Ubuntu 18.04)
Is Two-Weapon Fighting the only way for a Horizon Walker ranger to use the Distant Strike feature to attack two different creatures?
The default C drive is too small. How to make Windows boot from D drive
Broken 26'' wheel
Is it appropriate to rewrite and republish another author's useful but very badly written paper?
Advent calendar
Is there a Kähler manifold with no anti-holomophic involution?
Is self-awareness or consciousness actually a evolutionary disadvantage?
Resources for Learning Multiplication Facts
How can I get 2 characters to bond while standing alternate watches?
being overqualified as a barrier for getting a job
5yrs old being bossy... Is this too much or tolerable at this age?
Why does one mostly fall backward when slipping?
Planet where giant manned machines travel in convoy across surface, tracking some astronomical phenomenon
Can a public school in the USA force a 14yr old to create a Twitter account for a passing grade?
Are these homebrew metallic/chromatic pseudodragons the same CR as RAW pseudodragons?
Why do we need full-fledged workstations running massive OSes with massive software?
Is it principled to tip less if a pricey restaurant doesn't accept Visa or Mastercard?
Any reason not to use global lambdas?
This new puzzle type needs a name
Finishing pre-cooked prime rib, day-of?
Sometimes the updated rows are not locked within instead of update trigger
CodeReview question markdown downloader
Can you split resolutions and scrolling (horizontally) on an Amiga?
Summing Values in an "Association" with the same Keys
Where are all the network-bridges coming from, ifconfig shows me?
Dual NIC not workingCannot find device “eth0”. Failed to bring up eth0Pages loading too long on new router (Ubuntu 18.04)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
0
I'm using Ubuntu 18.04.3 LTS
As I'm a developer, I have Docker, docker-compose and Virtualbox and Vagrant installed
If I enter in a terminal:
$ ifconfig
I got a long list of network bridges.
br-2fdf26d8ad11: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.240.1 netmask 255.255.240.0 broadcast 192.168.255.255
br-3097f1941dd7: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.32.1 netmask 255.255.240.0 broadcast 192.168.47.255
br-604e362c8abb: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.28.0.1 netmask 255.255.0.0 broadcast 172.28.255.255
br-6bec4010864a: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.23.0.1 netmask 255.255.0.0 broadcast 172.23.255.255
br-729cfdd5c2dd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.48.1 netmask 255.255.240.0 broadcast 192.16628.63.255
br-72c49f160076: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
br-765c8f8c1edf: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
br-7b6ec7d56aec: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.31.0.1 netmask 255.255.0.0 broadcast 172.31.255.255
br-9392c09745cd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.27.0.1 netmask 255.255.0.0 broadcast 172.27.255.255
br-97685d1968fe: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.26.0.1 netmask 255.255.0.0 broadcast 172.26.255.255
br-9b033123127c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
br-bc2ff863085c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.96.1 netmask 255.255.240.0 broadcast 192.168.111.255
br-bcc4b1218247: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.30.0.1 netmask 255.255.0.0 broadcast 172.30.255.255
br-d7d1dd0718f3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.1 netmask 255.255.240.0 broadcast 192.168.95.255
br-dd4949ff923c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255
br-de108e80ee4d: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
br-e37000236cd8: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 255.255.240.0 broadcast 192.168.15.255
br-ec26f968abd4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
br-fa80bcc7af95: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.29.0.1 netmask 255.255.0.0 broadcast 172.29.255.255
enp0s31f6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.22.101.1 netmask 255.255.255.0 broadcast 172.22.101.255
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1492
inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.2.255
I'm not sure, where they all come from.
My problem is, that, if I want to use a public network (train, airports and so on), they normally run on 172.xx -> normally it's already used by a bridge, so I first have to bring it down and then delete it, as described in my blog
sudo ip link set br-bcc4b1218247 down
sudo brctl delbr br-bcc4b1218247
I also read, that if you use the Ubuntu Network Manager, they can all come back.
I was trying to understand, where they come from but I haven't understood it yet really.
networking 18.04 network-manager network-bridge
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
add a comment
|
0
I'm using Ubuntu 18.04.3 LTS
As I'm a developer, I have Docker, docker-compose and Virtualbox and Vagrant installed
If I enter in a terminal:
$ ifconfig
I got a long list of network bridges.
br-2fdf26d8ad11: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.240.1 netmask 255.255.240.0 broadcast 192.168.255.255
br-3097f1941dd7: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.32.1 netmask 255.255.240.0 broadcast 192.168.47.255
br-604e362c8abb: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.28.0.1 netmask 255.255.0.0 broadcast 172.28.255.255
br-6bec4010864a: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.23.0.1 netmask 255.255.0.0 broadcast 172.23.255.255
br-729cfdd5c2dd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.48.1 netmask 255.255.240.0 broadcast 192.16628.63.255
br-72c49f160076: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
br-765c8f8c1edf: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
br-7b6ec7d56aec: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.31.0.1 netmask 255.255.0.0 broadcast 172.31.255.255
br-9392c09745cd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.27.0.1 netmask 255.255.0.0 broadcast 172.27.255.255
br-97685d1968fe: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.26.0.1 netmask 255.255.0.0 broadcast 172.26.255.255
br-9b033123127c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
br-bc2ff863085c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.96.1 netmask 255.255.240.0 broadcast 192.168.111.255
br-bcc4b1218247: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.30.0.1 netmask 255.255.0.0 broadcast 172.30.255.255
br-d7d1dd0718f3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.1 netmask 255.255.240.0 broadcast 192.168.95.255
br-dd4949ff923c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255
br-de108e80ee4d: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
br-e37000236cd8: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 255.255.240.0 broadcast 192.168.15.255
br-ec26f968abd4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
br-fa80bcc7af95: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.29.0.1 netmask 255.255.0.0 broadcast 172.29.255.255
enp0s31f6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.22.101.1 netmask 255.255.255.0 broadcast 172.22.101.255
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1492
inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.2.255
I'm not sure, where they all come from.
My problem is, that, if I want to use a public network (train, airports and so on), they normally run on 172.xx -> normally it's already used by a bridge, so I first have to bring it down and then delete it, as described in my blog
sudo ip link set br-bcc4b1218247 down
sudo brctl delbr br-bcc4b1218247
I also read, that if you use the Ubuntu Network Manager, they can all come back.
I was trying to understand, where they come from but I haven't understood it yet really.
networking 18.04 network-manager network-bridge
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
1
Docker tends to make a lot of bridges sometimes if you let it. Those sound and look a lot like Docker-created bridges, but Vagrant could be at fault too
– Thomas Ward♦
Oct 1 at 22:38
are they needed? and: does it make sense to allow docker to make bridges? and how can i stop docker doing it?
– Joerg
Oct 1 at 22:41
1
Unfortunately, you can't really stop Docker or Vagrant from making bridges; the bridges are used to 'bridge' containers and virtual envs to your internet in a way that lets them have network connectivity. Both Docker and Vagrant tend to do this (VBox creates vboxnet interfaces that act as the bridges but once created doesn't create more), and there's really no way to truly shut the functionality off without recoding how the vagrant systems and docker containers are brought up within their compose / config files.
– Thomas Ward♦
Oct 1 at 23:42
add a comment
|
0
0
0
I'm using Ubuntu 18.04.3 LTS
As I'm a developer, I have Docker, docker-compose and Virtualbox and Vagrant installed
If I enter in a terminal:
$ ifconfig
I got a long list of network bridges.
br-2fdf26d8ad11: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.240.1 netmask 255.255.240.0 broadcast 192.168.255.255
br-3097f1941dd7: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.32.1 netmask 255.255.240.0 broadcast 192.168.47.255
br-604e362c8abb: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.28.0.1 netmask 255.255.0.0 broadcast 172.28.255.255
br-6bec4010864a: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.23.0.1 netmask 255.255.0.0 broadcast 172.23.255.255
br-729cfdd5c2dd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.48.1 netmask 255.255.240.0 broadcast 192.16628.63.255
br-72c49f160076: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
br-765c8f8c1edf: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
br-7b6ec7d56aec: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.31.0.1 netmask 255.255.0.0 broadcast 172.31.255.255
br-9392c09745cd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.27.0.1 netmask 255.255.0.0 broadcast 172.27.255.255
br-97685d1968fe: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.26.0.1 netmask 255.255.0.0 broadcast 172.26.255.255
br-9b033123127c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
br-bc2ff863085c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.96.1 netmask 255.255.240.0 broadcast 192.168.111.255
br-bcc4b1218247: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.30.0.1 netmask 255.255.0.0 broadcast 172.30.255.255
br-d7d1dd0718f3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.1 netmask 255.255.240.0 broadcast 192.168.95.255
br-dd4949ff923c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255
br-de108e80ee4d: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
br-e37000236cd8: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 255.255.240.0 broadcast 192.168.15.255
br-ec26f968abd4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
br-fa80bcc7af95: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.29.0.1 netmask 255.255.0.0 broadcast 172.29.255.255
enp0s31f6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.22.101.1 netmask 255.255.255.0 broadcast 172.22.101.255
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1492
inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.2.255
I'm not sure, where they all come from.
My problem is, that, if I want to use a public network (train, airports and so on), they normally run on 172.xx -> normally it's already used by a bridge, so I first have to bring it down and then delete it, as described in my blog
sudo ip link set br-bcc4b1218247 down
sudo brctl delbr br-bcc4b1218247
I also read, that if you use the Ubuntu Network Manager, they can all come back.
I was trying to understand, where they come from but I haven't understood it yet really.
networking 18.04 network-manager network-bridge
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
I'm using Ubuntu 18.04.3 LTS
As I'm a developer, I have Docker, docker-compose and Virtualbox and Vagrant installed
If I enter in a terminal:
$ ifconfig
I got a long list of network bridges.
br-2fdf26d8ad11: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.240.1 netmask 255.255.240.0 broadcast 192.168.255.255
br-3097f1941dd7: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.32.1 netmask 255.255.240.0 broadcast 192.168.47.255
br-604e362c8abb: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.28.0.1 netmask 255.255.0.0 broadcast 172.28.255.255
br-6bec4010864a: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.23.0.1 netmask 255.255.0.0 broadcast 172.23.255.255
br-729cfdd5c2dd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.48.1 netmask 255.255.240.0 broadcast 192.16628.63.255
br-72c49f160076: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
br-765c8f8c1edf: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
br-7b6ec7d56aec: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.31.0.1 netmask 255.255.0.0 broadcast 172.31.255.255
br-9392c09745cd: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.27.0.1 netmask 255.255.0.0 broadcast 172.27.255.255
br-97685d1968fe: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.26.0.1 netmask 255.255.0.0 broadcast 172.26.255.255
br-9b033123127c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
br-bc2ff863085c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.96.1 netmask 255.255.240.0 broadcast 192.168.111.255
br-bcc4b1218247: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.30.0.1 netmask 255.255.0.0 broadcast 172.30.255.255
br-d7d1dd0718f3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.1 netmask 255.255.240.0 broadcast 192.168.95.255
br-dd4949ff923c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255
br-de108e80ee4d: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
br-e37000236cd8: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 255.255.240.0 broadcast 192.168.15.255
br-ec26f968abd4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
br-fa80bcc7af95: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.29.0.1 netmask 255.255.0.0 broadcast 172.29.255.255
enp0s31f6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.22.101.1 netmask 255.255.255.0 broadcast 172.22.101.255
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1492
inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.2.255
I'm not sure, where they all come from.
My problem is, that, if I want to use a public network (train, airports and so on), they normally run on 172.xx -> normally it's already used by a bridge, so I first have to bring it down and then delete it, as described in my blog
sudo ip link set br-bcc4b1218247 down
sudo brctl delbr br-bcc4b1218247
I also read, that if you use the Ubuntu Network Manager, they can all come back.
I was trying to understand, where they come from but I haven't understood it yet really.
networking 18.04 network-manager network-bridge
networking 18.04 network-manager network-bridge
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
asked Oct 1 at 22:37
JoergJoerg
1013 bronze badges
1013 bronze badges
1
Docker tends to make a lot of bridges sometimes if you let it. Those sound and look a lot like Docker-created bridges, but Vagrant could be at fault too
– Thomas Ward♦
Oct 1 at 22:38
are they needed? and: does it make sense to allow docker to make bridges? and how can i stop docker doing it?
– Joerg
Oct 1 at 22:41
1
Unfortunately, you can't really stop Docker or Vagrant from making bridges; the bridges are used to 'bridge' containers and virtual envs to your internet in a way that lets them have network connectivity. Both Docker and Vagrant tend to do this (VBox creates vboxnet interfaces that act as the bridges but once created doesn't create more), and there's really no way to truly shut the functionality off without recoding how the vagrant systems and docker containers are brought up within their compose / config files.
– Thomas Ward♦
Oct 1 at 23:42
add a comment
|
1
Docker tends to make a lot of bridges sometimes if you let it. Those sound and look a lot like Docker-created bridges, but Vagrant could be at fault too
– Thomas Ward♦
Oct 1 at 22:38
are they needed? and: does it make sense to allow docker to make bridges? and how can i stop docker doing it?
– Joerg
Oct 1 at 22:41
1
Unfortunately, you can't really stop Docker or Vagrant from making bridges; the bridges are used to 'bridge' containers and virtual envs to your internet in a way that lets them have network connectivity. Both Docker and Vagrant tend to do this (VBox creates vboxnet interfaces that act as the bridges but once created doesn't create more), and there's really no way to truly shut the functionality off without recoding how the vagrant systems and docker containers are brought up within their compose / config files.
– Thomas Ward♦
Oct 1 at 23:42
1
1
Docker tends to make a lot of bridges sometimes if you let it. Those sound and look a lot like Docker-created bridges, but Vagrant could be at fault too
– Thomas Ward♦
Oct 1 at 22:38
Docker tends to make a lot of bridges sometimes if you let it. Those sound and look a lot like Docker-created bridges, but Vagrant could be at fault too
– Thomas Ward♦
Oct 1 at 22:38
are they needed? and: does it make sense to allow docker to make bridges? and how can i stop docker doing it?
– Joerg
Oct 1 at 22:41
are they needed? and: does it make sense to allow docker to make bridges? and how can i stop docker doing it?
– Joerg
Oct 1 at 22:41
1
1
Unfortunately, you can't really stop Docker or Vagrant from making bridges; the bridges are used to 'bridge' containers and virtual envs to your internet in a way that lets them have network connectivity. Both Docker and Vagrant tend to do this (VBox creates vboxnet interfaces that act as the bridges but once created doesn't create more), and there's really no way to truly shut the functionality off without recoding how the vagrant systems and docker containers are brought up within their compose / config files.
– Thomas Ward♦
Oct 1 at 23:42
Unfortunately, you can't really stop Docker or Vagrant from making bridges; the bridges are used to 'bridge' containers and virtual envs to your internet in a way that lets them have network connectivity. Both Docker and Vagrant tend to do this (VBox creates vboxnet interfaces that act as the bridges but once created doesn't create more), and there's really no way to truly shut the functionality off without recoding how the vagrant systems and docker containers are brought up within their compose / config files.
– Thomas Ward♦
Oct 1 at 23:42
add a comment
|
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1178015%2fwhere-are-all-the-network-bridges-coming-from-ifconfig-shows-me%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1178015%2fwhere-are-all-the-network-bridges-coming-from-ifconfig-shows-me%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Docker tends to make a lot of bridges sometimes if you let it. Those sound and look a lot like Docker-created bridges, but Vagrant could be at fault too
– Thomas Ward♦
Oct 1 at 22:38
are they needed? and: does it make sense to allow docker to make bridges? and how can i stop docker doing it?
– Joerg
Oct 1 at 22:41
1
Unfortunately, you can't really stop Docker or Vagrant from making bridges; the bridges are used to 'bridge' containers and virtual envs to your internet in a way that lets them have network connectivity. Both Docker and Vagrant tend to do this (VBox creates vboxnet interfaces that act as the bridges but once created doesn't create more), and there's really no way to truly shut the functionality off without recoding how the vagrant systems and docker containers are brought up within their compose / config files.
– Thomas Ward♦
Oct 1 at 23:42