netns | Simple network namespace handling for go | Continuous Deployment library

I presume docker command "docker run --rm -it -p 80:80 image ID"

Map port 80 on the local machine to port 80 in the container.

Please in the Internet browser key http://localhost: you build port 80 (EXPOSE 80)

if is in dockerfile add ENV ASPNETCORE_URLS=http://+:80

Please in the Internet browser key http://0.0.0.0:80/

Reference:https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/docker/building-net-docker-images?view=aspnetcore-6.0

L3fwd-acl works with IP packets only, for all non IP packets it drops. Hence with TAP PMD I had to follow the changes as

1. Disable any NIC PCIe device using --no-pci
2. Use new commands as sudo ./build/l3fwd-acl --file-prefix=mytest -l 2-4 --vdev=net_tap0 --vdev=net_tap1 --no-pci -- -P -p 3 --config="(0,0,4),(1,0,3)" --rule_ipv4=ipv4-sample.db --rule-ipv6=ipv6-sample.db --eth-dest=0, --eth-dest=1,
3. edit ip-sample.db file with the entries to be assigned for dtap0 and dtap1.
4. refer section 24.1.3 to identify the format and for default drop rule
5. start the application and use the following netns commands.

Both unshare --net=/somefile and ip netns add somename create a new network namespace and bind-mount it to somewhere. The only difference is that unshare bind-mounts it to whatever file you specify, and ip bind-mounts it to a new file in /var/run/netns/. In other words, if you used /var/run/netns/mynetns1 in place of /root/mynetns1, then you could later interact with it with ip.

If you install with istio enabled you also need to install the istio gateway.

I've tested your flow and it didn't work, and then did work after installing the following istio gateway.

For those of you running into a similar issue with your IPv6 only Kubernetes clusters heres what I have investigated found so far.

Background: It seems that this is a generic issue relating to IPv6 and CRI. I was running containerd in my setup and containerd versions 1.5.0-1.5.2 added two PRs (don't use socat for port forwarding and use happy-eyeballs for port-forwarding) which fixed a number of issues in IPv6 port-forwarding.

Potential fix: Further to pulling in containerd version 1.5.2 (as part of Ubuntu 20.04 LTS) I was also getting the error IPv4: dial tcp4 127.0.0.1:15021: connect: connection refused IPv6 dial tcp6: address localhost: no suitable address found when port-forwarding. This is caused by a DNS issue when resolving localhost. Hence I added localhost to resolve as ::1 in the host machine with the following command.

It looks like the bind mount was the issue. I was mounting to /bin/usr, which was somehow causing the error.

Since the observed total packet length is way greater than that of a typical jumbo frame (MTU 9k), it's apparent that the receiver side employs either Large Receive Offload (LRO) or Generic Receive Offload (GRO) thus reassembling smaller packets into larger ones on the network interface driver level. This might explain why the packet socket in question sees already reassembled (large) packets.

In this specific case, ethtool -k output indicates clearly that LRO is always disabled whilst GRO is indeed active and can be adjusted. As per the discussion in comments, disabling GRO indeed bears fruit.

The image depends on what version meteor you use.

Check this table: http://meteor-up.com/docs.html#meteor-support

I'm using the zodern/meteor:root with meteor 2.2.1

Well this error could just a random error in my VM for no reason so this could be ignored