search

NetSys / bess

BESS: Berkeley Extensible Software Switch
Other
313 stars 156 forks source link

Docker-Host Connection Example will fail. #1001

Open JorheMartinez opened 4 years ago

JorheMartinez commented 4 years ago

Good evening. Im Jorge I have been trying to start this example: https://github.com/NetSys/bess/wiki/Hooking-up-BESS-Ports#connecting-vms-and-containers-with-bess-vports and I have found the following issues trying to connect.

This is my configuration: dpdk-devbind.py --status: Network devices using DPDK-compatible driver

0000:02:02.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' drv=igb_uio unused=uio_pci_generic 0000:02:03.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' drv=igb_uio unused=uio_pci_generic

Network devices using kernel driver

0000:02:01.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' if=ens33 drv=e1000 unused=igb_uio,uio_pci_generic Active

One interface for each one of the interfaces, using igb_uio.

The script is as follows: container_if = VPort(ifname='eth_vport_test', docker='vport_test', ip_addrs=['10.255.99.2/24']) host_if = VPort(ifname='eth_host', ip_addrs=['10.255.99.1/24'])

PortInc(port=host_if) -> PortOut(port=container_if) PortInc(port=container_if) -> PortOut(port=host_if)

When running it inside the daemon, it seems to work on the docker side: root@54ae2c38e5cb:/# ifconfig eth_vport_test: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.255.99.2 netmask 255.255.255.0 broadcast 0.0.0.0 ether 06:07:b2:37:71:5a txqueuelen 0 (Ethernet) RX packets 66 bytes 10647 (10.6 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 9 bytes 378 (378.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 23 bytes 2576 (2.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 23 bytes 2576 (2.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

But not in the Host (Ubuntu 18.04) side: eth_host: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 96:62:1a:ec:3f:85 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 8203 (8.2 KB) TX errors 0 dropped 61 overruns 0 carrier 0 collisions 0

although the interface is created, no ip address have been assigned to it,and therefore PING tries will fail.

Any clue on what is happening and how to solve it? Thank you very much in advance. Jorge Martinez

vithalsm commented 1 year ago

Any clue on this issue please? It still persists..