= Openstack OVH Dedicated Server Networking = ![ ](https://www.redditstatic.com/desktop2x/img/renderTimingPixel.png) Hola a todos, he encargado un servidor dedicado y una subred /27 a OVH. Instalé Openstack (con los componentes más importantes) en él. He conectado la subred /27 al servidor y también puedo hacer ping a 5.5.5.128, que está asignada a la interfaz "eno1". (5.5.5. es solo un marcador de posición) El problema es que no se puede acceder a todas las demás direcciones IP porque probablemente una ruta sea incorrecta. Esa es la tabla de rutas de mi servidor: root@controller ruta Kernel IP tabla de enrutamiento Gateway de destino Genmask Flags Métrica Ref Use Iface default ovh-gateway-ip 0.0.0.0 UG 10brqf535e9d2-5d server-main-ip 0.0.0.0 255.255.255.0 U brqf535e9d2-5d 5.5.5.128 0.0.0.0 255.255.255.224 U brqf535e9d2-5d 192.168.122.0 0.0.0.0 255.255.255.0 U virbr0 La máscara de subred /24 para la IP principal del servidor es correcta. No sé por qué no es un /32 Desafortunadamente, la ruta a la red en la que quiero colocar las máquinas virtuales no funciona. No puedo alcanzar ninguna IP en él. Ni desde el exterior ni desde el propio controlador. Intenté configurar la IP de la puerta de enlace para "5.5.5.128/27"a la IP de la puerta de enlace de OVH (estoy usando para la ruta predeterminada), la IP principal de los servidores y también la 5.5.5.128, pero nada funciona. ¿Alguno de vosotros ha tenido el mismo problema o sabe la solución? ¡Gracias por tu ayuda! Editar: mi salida ifconfig: root@controller ifconfig brq70238470-59: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1450 ether 96:76:bc:b7:29:b5 txqueuelen 1000 (Ethernet) RX packets 103 bytes 4852 (4.8 KB) 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 brqf535e9d2-5d: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet main-ip netmask 255.255.255.0 broadcast xxx inet6 main-ipv6 prefixlen 56 scopeid 0x0 inet6 xx prefixlen 64 scopeid 0x20 ethertxqueuelen 1000 (Ethernet) RX packets 83655 bytes 3800864 (3.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 129123 bytes 8067301 (8.0 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 xx prefixlen 64 scopeid 0x20 ether d0:50:99:da:39:ac txqueuelen 1000 (Ethernet) RX packets 85212 bytes 5905226 (5.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 131955 bytes 8233407 (8.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 499119 bytes 146251170 (146.2 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 499119 bytes 146251170 (146.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap3166097e-73: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1450 ether 96:76:bc:b7:29:b5 txqueuelen 1000 (Ethernet) RX packets 12 bytes 2284 (2.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 102 bytes 6116 (6.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap4b8dc5a7-f5: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1500 ethertxqueuelen 1000 (Ethernet) RX packets 7 bytes 702 (702.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 91823 bytes 4385443 (4.3 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tapc2ba003a-21: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet6 fe80::fc16:3eff:fe03:28a3 prefixlen 64 scopeid 0x20 ether fe:16:3e:03:28:a3 txqueuelen 1000 (Ethernet) RX packets 102 bytes 6116 (6.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 15 bytes 2378 (2.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:de:85:70 txqueuelen 1000 (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 vxlan-53: flags=4163,BROADCAST,RUNNING,MULTICAST> mtu 1450 ether ea:e4:58:8e:bc:d8 txqueuelen 1000 (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 103 overruns 0 carrier 0 collisions 0 Its a bit strange, ifconfig doesnt show me my 5.5.5.128/27 here. # ip a12: brqf535e9d2-5d: ,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/etherbrd ff:ff:ff:ff:ff:ff inet main-ip/24 brd xxx.255 scope global brqf535e9d2-5d valid_lft forever preferred_lft forever inet 5.5.5.128/27 brd 5.5.5.159 scope global brqf535e9d2-5d valid_lft forever preferred_lft forever inet6 xxx/56 scope global valid_lft forever preferred_lft forever inet6 xxx/64 scope link valid_lft forever preferred_lft forever ![ ](httpswww.redditstatic.com/desktop2x/img/renderTimingPixel.png) Hi, Try to list all the interfaces and taps connected to the bridge brqf535e9d2-5d with the command "brctl show". You can see wich network namespace is connected to the tap interface doing "ip a" under link netns. Then try to stablish communication in the subnet from the network namespace. "ip netns exec [netns connected to the tap] ip a" This way you can see if you can stablish connection to instances running in compute nodes in the subnet 5.5.5.128/27 Hi, thanks for your reply. The brctl show returns me this: root@controller brctl show bridge name bridge id STP enabled interfaces brq70238470-59 8000.1ed5e9a9e7c0 no tap2a631157-e2 tap3166097e-73 tapc2ba003a-21 tapeefe5e6c-2d vxlan-53 brqf535e9d2-5d 8000.b65368642388 no eno1 tap4b8dc5a7-f5 tapa2486984-d4 virbr0 8000.525400de8570 yes Could you explain how and where I can find the "network namespace" You can see wich network namespace is connected to the tap interface doing "ip a" under link netns. I can't find it .128 looks like a network address. you should use 129-158 for host and one ip should be the gw == About Community == Members Online