Trying to set up a bridged connection from the web GUI alone is proving to be a daunting task.
The newly created device, name eth0, shows up under the Network tab, but is nowhere to be found in the container itself.
Screen Shot 2013-07-08 at 10.25.20.png
root@dzerzhinsky:/# ifconfig
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:623 errors:0 dropped:0 overruns:0 frame:0
TX packets:623 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:126157 (123.2 KiB) TX bytes:126157 (123.2 KiB)
root@dzerzhinsky:/# cat /etc/network/interfaces
# Auto generated lo interface
auto lo
iface lo inet loopback
Word to the wise :)
The newly created device, name eth0, shows up under the Network tab, but is nowhere to be found in the container itself.
Screen Shot 2013-07-08 at 10.25.20.png
root@dzerzhinsky:/# ifconfig
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:623 errors:0 dropped:0 overruns:0 frame:0
TX packets:623 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:126157 (123.2 KiB) TX bytes:126157 (123.2 KiB)
root@dzerzhinsky:/# cat /etc/network/interfaces
# Auto generated lo interface
auto lo
iface lo inet loopback
Word to the wise :)