View previous topic :: View next topic |
Author |
Message |
59729 Apprentice
Joined: 21 Jun 2004 Posts: 279
|
Posted: Sun Nov 23, 2014 6:53 pm Post subject: LXC tap, bridge mess |
|
|
This is confusing as ####, any pointers to get me started in the right direction again?
- Give guest it's own IP and access, later im going to add external WAN IF as physical, it will also act as a dns server and NAT routing so it needs be reachable from the network.
- The host still needs access to the same interface as I need to ssh to it among other things, there will also be other guests running services
Ive tried different things, this is what I have now and I can't ping the guest from host or network and I cant ping network host from guest
Quote: | bridge name bridge id STP enabled interfaces
br-router 8000.2278a72c2b8d no tap-router
***** routing and ifconfig output after the guest is started / veth was added and somehow it stopped connecting to br-router I think?
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 85.228.192.1 0.0.0.0 UG 4 0 0 enp0s20u3
85.228.192.0 0.0.0.0 255.255.240.0 U 4 0 0 enp0s20u3
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eno1
br-router: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 22:78:a7:2c:2b:8d txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::c23f:d5ff:fe62:2b3d prefixlen 64 scopeid 0x20<link>
ether c0:3f:d5:62:2b:3d txqueuelen 1000 (Ethernet)
RX packets 4659 bytes 447910 (437.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 712 bytes 98477 (96.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7c00000-f7c20000
tap-router: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500
ether 22:78:a7:2c:2b:8d txqueuelen 500 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vethB95CIO: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fcd6:b4ff:fe6a:c605 prefixlen 64 scopeid 0x20<link>
ether fe:d6:b4:6a:c6:05 txqueuelen 1000 (Ethernet)
RX packets 8 bytes 648 (648.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
From within guest
Quote: |
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::74e7:82ff:fef6:2c1e prefixlen 64 scopeid 0x20<link>
ether 76:e7:82:f6:2c:1e txqueuelen 1000 (Ethernet)
RX packets 8 bytes 648 (648.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 |
guest startup configuration
Quote: |
## Network
lxc.utsname = containerhostname
# veth
lxc.network.type=veth
lxc.network.flags=up
lxc.network.link=br-router
#lxc.network.hwaddr=
lxc.network.ipv4=192.168.0.2/24
# phys
#lxc.network.type=phys
#lxc.network.link= enp0s20u3
#lxc.network.flags=up
#lxc.network.hwaddr=dhcp
|
|
|
Back to top |
|
|
59729 Apprentice
Joined: 21 Jun 2004 Posts: 279
|
Posted: Sun Nov 23, 2014 11:56 pm Post subject: |
|
|
Seems the LXC ebuild is broken to some extent maybe that's why it's still "~", according to fragmented documentation dnsmasq should be pulled in as a dependency, a bridge lxbr01 should be created automaticly and a iptables MASQ rule for the bridge should be added automaticly, the rest should be automatic.
Im saying broken to some extent as there are no mention of this on the gentoo lxc wiki, might be that it's supposed to work like this in gentoo.
Hopefully this will help someone, thinking of going openvz instead depending on how difficult it is to fix as i'm still not sure what needs to be done. A whole day gone |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|