Re: [Lxc-users] Running LXC on a pxelinux machine
Unfortunately I haven't managed to get any further :( I can still ping the LXC containers from other hosts on the network, and they can ping each other, but I cannot ping them from the pxelinux host machine. Comparing the network config between the pxelinux host and a non-pxelinux host I can see that the pxelinux host has an IP associated with eth0 while the non-pxelinux associates the IP with br0. I've tried various attempts to reassign the ip address on the pxelinux host to br0 but to no avail (attempts result in hanging the machine). Any more pointers would be a great help! Gus. On 04/05/11 13:23, Gus Power wrote: > Hi Guido, > >> Why STP is disabled? > > Good question! Info below: > >> route -n > route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 00 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo > 0.0.0.0 192.168.1.1 0.0.0.0 UG0 00 eth0 > >> brctl showstp br0 > br0 > bridge id8000.00183704c188 > designated root 8000.00183704c188 > root port 0path cost 0 > max age19.99 bridge max age19.99 > hello time 1.99 bridge hello time 1.99 > forward delay 0.00 bridge forward delay >0.00 > ageing time 299.95 > hello timer 0.38 tcn timer 0.00 > topology change timer 0.00 gc timer > 33.56 > flags > > > eth0 (1) > port id 8001stateforwarding > designated root 8000.00183704c188 path cost 4 > designated bridge8000.00183704c188 message age timer 0.00 > designated port 8001forward delay timer0.00 > designated cost 0hold timer 0.00 > flags > > vethNFweOZ (2) > port id 8002stateforwarding > designated root 8000.00183704c188 path cost 2 > designated bridge8000.00183704c188 message age timer 0.00 > designated port 8002forward delay timer0.00 > designated cost 0hold timer 0.00 > flags > > vethNeCrkd (4) > port id 8004stateforwarding > designated root 8000.00183704c188 path cost 2 > designated bridge8000.00183704c188 message age timer 0.00 > designated port 8004forward delay timer0.00 > designated cost 0hold timer 0.00 > flags > > vethU0zyYA (3) > port id 8003stateforwarding > designated root 8000.00183704c188 path cost 2 > designated bridge8000.00183704c188 message age timer 0.00 > designated port 8003forward delay timer0.00 > designated cost 0hold timer 0.00 > flags > >> brctl showmacs br0 > port no mac addris local? ageing timer > 1 00:00:48:0e:9a:16 no75.22 > 1 00:16:01:df:a7:36 no33.51 > 1 00:18:37:04:c0:36 no 3.40 > 1 00:18:37:04:c1:15 no56.37 > 1 00:18:37:04:c1:80 no45.16 > 1 00:18:37:04:c1:88 yes0.00 > 1 00:18:37:04:c1:a0 no43.84 > 1 00:18:37:04:c1:c5 no19.96 > 1 00:1d:73:4c:13:e8 no45.23 > 1 00:1e:c9:59:a4:83 no 3.39 > 1 00:1f:28:dc:ba:80 no19.52 > 1 00:1f:c6:bf:07:4d no 5.10 > 1 00:23:6c:84:ce:57 no33.66 > 1 08:00:27:dc:f1:ca no33.66 > 1 20:cf:30:4e:1a:fd no73.35 > 1 20:cf:30:5a:c9:e7 no42.16 > 1 2a:68:44:23:5b:3d no34.18 > 4 7a:0c:74:86:f6:f4 yes0.00 > 3 92:61:42:84:ec:5a yes0.00 > 2 96:73:0c:d0:71:f5 yes0.00 > 1 a2:f7:44:bf:9e:25 no67.64 > > > G > > On 04/05/11 09:24, Jäkel, Guido wrote: >> Dear Gus, >> brctl show >>> bridge name bridge id STP enabled interfaces >>> br0 8000.00183704c
Re: [Lxc-users] Running LXC on a pxelinux machine
Hi Guido, > Why STP is disabled? Good question! Info below: > route -n route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG0 00 eth0 > brctl showstp br0 br0 bridge id 8000.00183704c188 designated root8000.00183704c188 root port 0path cost 0 max age 19.99 bridge max age19.99 hello time1.99 bridge hello time 1.99 forward delay 0.00 bridge forward delay 0.00 ageing time 299.95 hello timer 0.38 tcn timer 0.00 topology change timer 0.00 gc timer 33.56 flags eth0 (1) port id8001stateforwarding designated root8000.00183704c188 path cost 4 designated bridge 8000.00183704c188 message age timer 0.00 designated port8001forward delay timer0.00 designated cost 0hold timer 0.00 flags vethNFweOZ (2) port id8002stateforwarding designated root8000.00183704c188 path cost 2 designated bridge 8000.00183704c188 message age timer 0.00 designated port8002forward delay timer0.00 designated cost 0hold timer 0.00 flags vethNeCrkd (4) port id8004stateforwarding designated root8000.00183704c188 path cost 2 designated bridge 8000.00183704c188 message age timer 0.00 designated port8004forward delay timer0.00 designated cost 0hold timer 0.00 flags vethU0zyYA (3) port id8003stateforwarding designated root8000.00183704c188 path cost 2 designated bridge 8000.00183704c188 message age timer 0.00 designated port8003forward delay timer0.00 designated cost 0hold timer 0.00 flags > brctl showmacs br0 port no mac addris local? ageing timer 1 00:00:48:0e:9a:16 no75.22 1 00:16:01:df:a7:36 no33.51 1 00:18:37:04:c0:36 no 3.40 1 00:18:37:04:c1:15 no56.37 1 00:18:37:04:c1:80 no45.16 1 00:18:37:04:c1:88 yes0.00 1 00:18:37:04:c1:a0 no43.84 1 00:18:37:04:c1:c5 no19.96 1 00:1d:73:4c:13:e8 no45.23 1 00:1e:c9:59:a4:83 no 3.39 1 00:1f:28:dc:ba:80 no19.52 1 00:1f:c6:bf:07:4d no 5.10 1 00:23:6c:84:ce:57 no33.66 1 08:00:27:dc:f1:ca no33.66 1 20:cf:30:4e:1a:fd no73.35 1 20:cf:30:5a:c9:e7 no42.16 1 2a:68:44:23:5b:3d no34.18 4 7a:0c:74:86:f6:f4 yes0.00 3 92:61:42:84:ec:5a yes0.00 2 96:73:0c:d0:71:f5 yes0.00 1 a2:f7:44:bf:9e:25 no67.64 G On 04/05/11 09:24, Jäkel, Guido wrote: > Dear Gus, > >>> brctl show >> bridge name bridge id STP enabled interfaces >> br0 8000.00183704c188 no eth0 >> vethNFweOZ >> vethU0zyYA > > Why STP is disabled? > What's the output of 'brctl showmacs br0' and ' brcltr showstp br0'? > What's the exact routing (output of 'route -n')? > > Guido -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Lxc-users mailing list Lxc-users
Re: [Lxc-users] Running LXC on a pxelinux machine
Dear Gus, > > brctl show > bridge name bridge id STP enabled interfaces > br0 8000.00183704c188 no eth0 > vethNFweOZ > vethU0zyYA Why STP is disabled? What's the output of 'brctl showmacs br0' and ' brcltr showstp br0'? What's the exact routing (output of 'route -n')? Guido -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Running LXC on a pxelinux machine
Hi Daniel, > Do you want to run containers on your diskless host ? Yes exactly. The lxc containers on the diskless host come up fine and can be reached from other hosts on the network. The issue I have is that the host itself cannot ping the containers that it is running. Some details: > ifconfig br0 Link encap:Ethernet HWaddr 00:18:37:04:c1:88 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:456233 errors:0 dropped:22914 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:23925950 (22.8 MiB) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr 00:18:37:04:c1:88 inet addr:192.168.1.213 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1405956 errors:0 dropped:40 overruns:0 frame:0 TX packets:541241 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1078882115 (1.0 GiB) TX bytes:64571866 (61.5 MiB) Interrupt:42 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3200 (3.1 KiB) TX bytes:3200 (3.1 KiB) vethNFweO Link encap:Ethernet HWaddr 96:73:0c:d0:71:f5 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:45090 errors:0 dropped:0 overruns:0 frame:0 TX packets:548911 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3814374 (3.6 MiB) TX bytes:163615712 (156.0 MiB) vethU0zyY Link encap:Ethernet HWaddr 92:61:42:84:ec:5a UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:339069 errors:0 dropped:0 overruns:0 frame:0 TX packets:686545 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:43984153 (41.9 MiB) TX bytes:648025709 (618.0 MiB) > brctl show bridge name bridge id STP enabled interfaces br0 8000.00183704c188 no eth0 vethNFweOZ vethU0zyYA > iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination > ebtables list Bridge table: filter Bridge chain: INPUT, entries: 0, policy: ACCEPT Bridge chain: FORWARD, entries: 0, policy: ACCEPT Bridge chain: OUTPUT, entries: 0, policy: ACCEPT The two containers (veth interfaces vethNFweOZ and vethU0zyYA) have IP addresses of 192.168.1.138 and 192.168.1.198 respectively and can be reached by other machines on the network. When I try to ping either of these containers from the host I get 'Destination Host Unreachable' and the dropped RX packet count goes up on the 'br0' interface. Some advice about how to correctly configure the routing would be great! Thanks for your help, Gus. On 05/04/11 16:13, Daniel Lezcano wrote: > On 04/05/2011 09:49 AM, Gus Power wrote: >> Hi, >> >> I've got a pxelinux boot configuration with a remote NFS root filesystem >> and was wondering if anyone out there has tried running lxc on such a >> configuration. I'm having difficulty getting the host machine to talk >> with the running lxc containers. >> >> I managed to get a local bridge interface up and running without hanging >> the host machine using the following: >> >> #Copy to /tmp tmpfs to avoid NFS hang >> cp /sbin/brctl /tmp >> cp /sbin/ifconfig /tmp >> >> /tmp/brctl >> /tmp/ifconfig >> /tmp/brctl addbr br0 >> /tmp/ifconfig br0 up >> /tmp/brctl setfd br0 0 >> /tmp/brctl stp br0 off >> /tmp/brctl addif br0 eth0 >> /tmp/ifconfig eth0 192.168.1.68 netmask 255.255.255.0 >> /tmp/brctl show >> >> > From there I can create lxc container instances; other machines on the >> network can talk to them but the host machine is unable to do so. I >> suspect I need to update the bridge tables (using ebtables) in some way. >> >> Any help greatly appreciated! > > Hi Gus, > > I am not sure to understand the use case. Can you elaborate ? > > Do you want to run containers on your diskless host ? > or > Do you want to have your diskless host to run inside a container ? > > I did recently a configuration with a tftp server running inside a > container and a pxe host to boot inside it. > It was working like a charm. Maybe it is what you are looking for ? -- WhatsUp Gold - Download Free Network Management Softwar
Re: [Lxc-users] Running LXC on a pxelinux machine
On 04/05/2011 09:49 AM, Gus Power wrote: > Hi, > > I've got a pxelinux boot configuration with a remote NFS root filesystem > and was wondering if anyone out there has tried running lxc on such a > configuration. I'm having difficulty getting the host machine to talk > with the running lxc containers. > > I managed to get a local bridge interface up and running without hanging > the host machine using the following: > > #Copy to /tmp tmpfs to avoid NFS hang > cp /sbin/brctl /tmp > cp /sbin/ifconfig /tmp > > /tmp/brctl > /tmp/ifconfig > /tmp/brctl addbr br0 > /tmp/ifconfig br0 up > /tmp/brctl setfd br0 0 > /tmp/brctl stp br0 off > /tmp/brctl addif br0 eth0 > /tmp/ifconfig eth0 192.168.1.68 netmask 255.255.255.0 > /tmp/brctl show > > > From there I can create lxc container instances; other machines on the > network can talk to them but the host machine is unable to do so. I > suspect I need to update the bridge tables (using ebtables) in some way. > > Any help greatly appreciated! Hi Gus, I am not sure to understand the use case. Can you elaborate ? Do you want to run containers on your diskless host ? or Do you want to have your diskless host to run inside a container ? I did recently a configuration with a tftp server running inside a container and a pxe host to boot inside it. It was working like a charm. Maybe it is what you are looking for ? -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] Running LXC on a pxelinux machine
Hi, I've got a pxelinux boot configuration with a remote NFS root filesystem and was wondering if anyone out there has tried running lxc on such a configuration. I'm having difficulty getting the host machine to talk with the running lxc containers. I managed to get a local bridge interface up and running without hanging the host machine using the following: #Copy to /tmp tmpfs to avoid NFS hang cp /sbin/brctl /tmp cp /sbin/ifconfig /tmp /tmp/brctl /tmp/ifconfig /tmp/brctl addbr br0 /tmp/ifconfig br0 up /tmp/brctl setfd br0 0 /tmp/brctl stp br0 off /tmp/brctl addif br0 eth0 /tmp/ifconfig eth0 192.168.1.68 netmask 255.255.255.0 /tmp/brctl show >From there I can create lxc container instances; other machines on the network can talk to them but the host machine is unable to do so. I suspect I need to update the bridge tables (using ebtables) in some way. Any help greatly appreciated! Thanks, Gus. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
