kopeio / networking Goto Github PK

View Code? Open in Web Editor NEW

43.0 43.0 3.0 25.13 MB

Networking for kubernetes

Makefile 4.62% Go 93.72% Shell 0.73% Dockerfile 0.94%

networking's People

Contributors

Stargazers

Watchers

Forkers

robertojrojas justinsb aelmehdi

networking's Issues

Autoscaling churn causes unbound ARP table growth

Studying the behavior of networking-agent (1.0.20180319 and 1.0.20181028) shows that the agent adds IP routes and permanent IP neighbor (ARP) entries for new Kubernetes nodes coming up. When nodes get destroyed (e.g. manual EC2 instance termination or autoscaler scale-down), the networking-agent only cleans up the IP route and leaves an orphaned ARP entry in place.

We can see this in code also:

networking/pkg/routing/netutil/neigh_table.go

Line 72 in dc70349

// We don't remove neighbour entries

The problem is that this causes ARP tables to grow without bounds in long-lived clusters with machine churn due to cluster autoscaling.

What is the rationale for leaving stale ARP entries around?

Thanks!

CC @justinsb

We should support mixed-mode networking

Would be cool to use layer2 in the same subnet, and then encapsulation across subnets

What is the default transport mode?

I built a cluster using kops in AWS across multiple availability zones with the topology option set to private. I'm 99% sure I set the networking option to kopeio-vxlan, but my cluster config yaml just states kopeio. Is the vxlan transport mode the default in this case? If not, can I switch to the vxlan transport mode without rebuilding the cluster?

I only ask because I've been seeing a ton of pod liveness/readiness probe issues, and I also "feel" like networking between my services running in the cluster is not optimal. I say this because I'm seeing a lot of timeouts between services, but my custom service-level metrics are not showing signs of the actual service code running slow.

Set critical pod annotations

Be sure we set critical pod annotations, also remove our CPU limits

cf kubernetes/kubernetes#51135 (comment)

Set MTU

Make sure that we are setting MTU.

Kubelet now gets a --network-plugin-mtu=9001 flag (for example). I don't think we are doing the same thing.

Spurious traffic spikes

Hi, I've noticed instances in a kopeio-vxlan cluster have huge traffic spikes.

These spikes happen on all instances, but only on one at a time. Those spikes happen even in the off-hours when there is little load on the cluster.

I've utilized AWS Flow Logs and found out that the traffic is mostly UDP communication on port 4789.

AWS Flow Logs (snippet)

https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/flow-logs.html#flow-log-records

2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.92.19 172.22.58.146 50581 4789 17 2 306 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.53.246 35299 4789 17 4 880 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.88.236 172.22.58.146 30320 4789 17 1 113 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.88.236 22788 4789 17 2 472 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.51.161 172.22.58.146 34569 4789 17 2 246 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 36722 4789 17 1 123 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.42.162 44133 4789 17 1 246 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.94.84 172.22.58.146 47298 4789 17 1 127 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.51.161 50672 4789 17 4 964 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 15213 4789 17 2 226 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.94.84 172.22.58.146 20798 4789 17 1 153 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.94.84 34996 4789 17 5 962 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.51.161 172.22.58.146 53635 4789 17 1 143 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.82.116 62378 4789 17 4 766 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 36226 4789 17 1 131 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.68.149 12349 4789 17 1 234 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 29725 4789 17 2 286 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.88.236 23663 4789 17 5 817 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.82.116 60431 4789 17 6 1333 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.51.161 172.22.58.146 26500 4789 17 1 123 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.82.116 56256 4789 17 2 460 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.88.236 64589 4789 17 2 333 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.68.149 172.22.58.146 57261 4789 17 1 113 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.51.161 28766 4789 17 2 466 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.92.19 172.22.58.146 40694 4789 17 2 286 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.51.161 23762 4789 17 2 454 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.88.236 37026 4789 17 3 692 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.82.116 172.22.58.146 52841 4789 17 1 137 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.53.246 65099 4789 17 1 236 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.51.161 172.22.58.146 57332 4789 17 1 123 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.92.19 30321 4789 17 2 379 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.51.161 172.22.58.146 36580 4789 17 2 306 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 12584 4789 17 1 131 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.88.236 57435 4789 17 1 141 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.68.149 172.22.58.146 12106 4789 17 1 153 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.53.246 61754 4789 17 1 141 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.42.162 32393 4789 17 3 672 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.88.236 36683 4789 17 1 127 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.94.84 172.22.58.146 30920 4789 17 3 399 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.92.19 32764 4789 17 1 246 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 13423 4789 17 1 137 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.53.246 38424 4789 17 1 143 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.42.162 50440 4789 17 1 244 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 11241 4789 17 2 286 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.42.162 56891 4789 17 2 472 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.94.84 172.22.58.146 61648 4789 17 1 143 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.58.146 172.22.94.84 41497 4789 17 3 522 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.68.149 172.22.58.146 13206 4789 17 1 123 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.92.19 172.22.58.146 47245 4789 17 3 413 1523930450 1523930510 ACCEPT OK
2018-04-17T02:00:50.000Z 2 831119889470 eni-81db8fd5 172.22.42.162 172.22.58.146 55720 4789 17 1 141 1523930450 1523930510 ACCEPT OK

kopeio-networking-agent logs

Nothing out of ordinary

Apr 16 23:47:35 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 21:47:35.584112    2898 nodecontroller.go:64] doing node watch from 4269759
Apr 17 00:39:45 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 22:39:45.098862    2898 nodecontroller.go:77] node watch channel closed
Apr 17 00:39:45 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 22:39:45.107867    2898 nodecontroller.go:64] doing node watch from 4280988
Apr 17 01:13:24 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 23:13:24.906653    2898 nodecontroller.go:77] node watch channel closed
Apr 17 01:13:24 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 23:13:24.914303    2898 nodecontroller.go:64] doing node watch from 4288294
Apr 17 01:57:40 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 23:57:40.330856    2898 nodecontroller.go:77] node watch channel closed
Apr 17 01:57:40 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0416 23:57:40.340110    2898 nodecontroller.go:64] doing node watch from 4297699
Apr 17 02:53:29 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 00:53:29.095999    2898 nodecontroller.go:77] node watch channel closed
Apr 17 02:53:29 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 00:53:29.105905    2898 nodecontroller.go:64] doing node watch from 4309962
Apr 17 03:25:37 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 01:25:37.059477    2898 nodecontroller.go:77] node watch channel closed
Apr 17 03:25:37 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 01:25:37.075891    2898 nodecontroller.go:64] doing node watch from 4316955
Apr 17 03:58:54 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 01:58:54.094724    2898 nodecontroller.go:77] node watch channel closed
Apr 17 03:58:54 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 01:58:54.105373    2898 nodecontroller.go:64] doing node watch from 4324102
Apr 17 04:58:24 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 02:58:23.927393    2898 nodecontroller.go:77] node watch channel closed
Apr 17 04:58:24 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 02:58:23.935893    2898 nodecontroller.go:64] doing node watch from 4336877
Apr 17 05:41:58 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 03:41:58.226786    2898 nodecontroller.go:77] node watch channel closed
Apr 17 05:41:58 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 03:41:58.237629    2898 nodecontroller.go:64] doing node watch from 4346186
Apr 17 06:20:12 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 04:20:12.095181    2898 nodecontroller.go:77] node watch channel closed
Apr 17 06:20:12 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 04:20:12.103680    2898 nodecontroller.go:64] doing node watch from 4354468
Apr 17 07:14:16 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 05:14:16.016425    2898 nodecontroller.go:77] node watch channel closed
Apr 17 07:14:16 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 05:14:16.028355    2898 nodecontroller.go:64] doing node watch from 4365977
Apr 17 07:44:47 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 05:44:47.353619    2898 nodecontroller.go:77] node watch channel closed
Apr 17 07:44:47 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 05:44:47.369939    2898 nodecontroller.go:64] doing node watch from 4372487
Apr 17 08:16:03 kube-system [networking-agent]kopeio-networking-agent-fmh8q: I0417 06:16:03.699499    2898 nodecontroller.go:77] node watch channel closed

Honestly I'm not quite sure how to proceed debugging this. Would you say this is a kopeio issue? If so, what other logs could be relevant?

Update:
This is a complete log from the single minute the spike happened: https://gist.github.com/Mikulas/078839b5a453acdeff889910f9341fcf. It's not ordered properly because CloudWatch seems to only have 1 second granularity.
It seems like there is a cycle between 172.22.88.236 and 172.22.58.146, which keep sending packets of decreasing size to each other.

Unexpected error

W1129 01:54:04.716054    3871 netlink_monitor.go:49] error deserializing netlink monitor message: Link not found
W1129 01:54:04.716075    3871 netlink_monitor.go:49] error deserializing netlink monitor message: Link not found
W1129 01:54:04.716093    3871 netlink_monitor.go:49] error deserializing netlink monitor message: Link not found

Strange networking weirdness, Consistent network timeouts, odd errors

Logs

I0607 14:03:30.155777    1860 netlink_monitor.go:117] NETLINK: ip neigh replace 100.96.3.22 lladdr 00:53:64:60:03:00 dev vxlanX
I0607 14:03:33.554475    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-106-8.ec2.internal
I0607 14:03:33.699194    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-75-144.ec2.internal
I0607 14:03:35.101809    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-102-12.ec2.internal
I0607 14:03:35.339752    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-90-141.ec2.internal
I0607 14:03:37.560420    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-49-121.ec2.internal
I0607 14:03:38.518182    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-53-142.ec2.internal
I0607 14:03:43.579890    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-106-8.ec2.internal
I0607 14:03:43.717349    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-75-144.ec2.internal
I0607 14:03:45.126226    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-102-12.ec2.internal
I0607 14:03:45.361902    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-90-141.ec2.internal
I0607 14:03:47.243740    1860 vxlanrouting.go:273] mapped ip 100.96.3.0 -> mac 00:53:64:60:03:00
W0607 14:03:47.243773    1860 netlink_monitor.go:114] HACK mapping assuming /24 PodCIDR, 96 as second: 100.96.3.5 -> 00:53:64:60:03:00
I0607 14:03:47.243781    1860 netlink_monitor.go:117] NETLINK: ip neigh replace 100.96.3.5 lladdr 00:53:64:60:03:00 dev vxlanX
I0607 14:03:47.243887    1860 vxlanrouting.go:273] mapped ip 100.96.3.0 -> mac 00:53:64:60:03:00
W0607 14:03:47.243900    1860 netlink_monitor.go:114] HACK mapping assuming /24 PodCIDR, 96 as second: 100.96.3.9 -> 00:53:64:60:03:00
I0607 14:03:47.243907    1860 netlink_monitor.go:117] NETLINK: ip neigh replace 100.96.3.9 lladdr 00:53:64:60:03:00 dev vxlanX
I0607 14:03:47.579844    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-49-121.ec2.internal
I0607 14:03:48.536596    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-53-142.ec2.internal
I0607 14:03:51.274338    1860 vxlanrouting.go:273] mapped ip 100.96.8.0 -> mac 00:53:64:60:08:00
W0607 14:03:51.274374    1860 netlink_monitor.go:114] HACK mapping assuming /24 PodCIDR, 96 as second: 100.96.8.27 -> 00:53:64:60:08:00
I0607 14:03:51.274383    1860 netlink_monitor.go:117] NETLINK: ip neigh replace 100.96.8.27 lladdr 00:53:64:60:08:00 dev vxlanX
I0607 14:03:53.602062    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-106-8.ec2.internal
I0607 14:03:53.736832    1860 nodecontroller.go:83] node changed: MODIFIED ip-10-1-75-144.ec2.internal
I0607 14:03:53.995736    1860 vxlanrouting.go:273] mapped ip 100.96.3.0 -> mac 00:53:64:60:03:00
W0607 14:03:53.995770    1860 netlink_monitor.go:114] HACK mapping assuming /24 PodCIDR, 96 as second: 100.96.3.16 -> 00:53:64:60:03:00
I0607 14:03:53.995779    1860 netlink_monitor.go:117] NETLINK: ip neigh replace 100.96.3.16 lladdr 00:53:64:60:03:00 dev vxlanX

Top of log after pod restart:

I0607 16:03:12.374239   32517 main.go:76] Using build: https://github.com/kopeio/networking - 0.5
E0607 16:03:12.571753   32517 main.go:146] assuming overlay is 100.96.0.0/12
W0607 16:03:12.571875   32517 vxlanrouting.go:45] MTU hard-coded to underlying interface eth0 MTU - 100 = 8901
I0607 16:03:12.572065   32517 nodecontroller.go:33] starting node controller
I0607 16:03:12.572166   32517 providercontroller.go:35] starting node controller
I0607 16:03:12.572188   32517 providercontroller.go:39] shutting down node controller
I0607 16:03:12.572277   32517 providercontroller.go:47] node map not yet ready
I0607 16:03:13.572406   32517 providercontroller.go:47] node map not yet ready
I0607 16:03:13.976523   32517 nodes.go:101] Node "ip-10-1-102-12.ec2.internal" changed
I0607 16:03:13.976552   32517 nodes.go:101] Node "ip-10-1-106-8.ec2.internal" changed
I0607 16:03:13.976559   32517 nodes.go:101] Node "ip-10-1-49-121.ec2.internal" changed
I0607 16:03:13.976564   32517 nodes.go:101] Node "ip-10-1-53-142.ec2.internal" changed
I0607 16:03:13.976568   32517 nodes.go:101] Node "ip-10-1-75-144.ec2.internal" changed
I0607 16:03:13.976572   32517 nodes.go:101] Node "ip-10-1-90-141.ec2.internal" changed
I0607 16:03:14.572859   32517 providercontroller.go:50] node map is ready
I0607 16:03:14.572904   32517 vxlanrouting.go:273] mapped ip 100.96.8.0 -> mac 00:53:64:60:08:00
W0607 16:03:14.573050   32517 vxlanrouting.go:94] Unable to create link; will reuse existing link: file exists
I0607 16:03:14.573303   32517 link_addresses.go:26] Actual address entry: {"IP":"100.96.8.0","Mask":"//AAAA==","Label":"vxlan1","Flags":128,"Scope":0,"Peer":{"IP":"100.96.8.0","Mask":"//AAAA=="},"Broadcast":""}
I0607 16:03:14.573329   32517 link_addresses.go:26] Actual address entry: {"IP":"fe80::253:64ff:fe60:800","Mask":"//////////8AAAAAAAAAAA==","Label":"","Flags":128,"Scope":253,"Peer":{"IP":"fe80::253:64ff:fe60:800","Mask":"//////////8AAAAAAAAAAA=="},"Broadcast":""}
I0607 16:03:14.573348   32517 link_addresses.go:38] Expected address entry: {"IP":"100.96.8.0","Mask":"//AAAA==","Label":"vxlan1","Flags":128,"Scope":0,"Peer":null,"Broadcast":""}
I0607 16:03:14.573362   32517 link_addresses.go:80] NETLINK: ip addr del fe80::253:64ff:fe60:800/64 dev link vxlan1
I0607 16:03:14.573445   32517 vxlanrouting.go:134] NETLINK: ip link set vxlan1 up
I0607 16:03:14.573516   32517 vxlanrouting.go:273] mapped ip 100.96.3.0 -> mac 00:53:64:60:03:00
I0607 16:03:14.573528   32517 vxlanrouting.go:273] mapped ip 100.96.1.0 -> mac 00:53:64:60:01:00
I0607 16:03:14.573535   32517 vxlanrouting.go:273] mapped ip 100.96.6.0 -> mac 00:53:64:60:06:00
I0607 16:03:14.573542   32517 vxlanrouting.go:273] mapped ip 100.96.7.0 -> mac 00:53:64:60:07:00
I0607 16:03:14.573549   32517 vxlanrouting.go:273] mapped ip 100.96.0.0 -> mac 00:53:64:60:00:00
I0607 16:03:14.573562   32517 neigh_table.go:25] NETLINK: ip neigh show dev vxlan1
W0607 16:03:14.573668   32517 neigh_table.go:31] TODO: using strings as layer2 key is inefficient
I0607 16:03:14.573718   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":1,"Type":1,"Flags":0,"IP":"100.96.3.18","HardwareAddr":null}
I0607 16:03:14.573736   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":32,"Type":1,"Flags":0,"IP":"100.96.3.28","HardwareAddr":null}
I0607 16:03:14.573755   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":4,"Type":1,"Flags":0,"IP":"100.96.7.0","HardwareAddr":"AFNkYAcA"}
I0607 16:03:14.573771   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":2,"Type":1,"Flags":0,"IP":"100.96.3.22","HardwareAddr":"AFNkYAMA"}
I0607 16:03:14.573787   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":4,"Type":1,"Flags":0,"IP":"100.96.6.0","HardwareAddr":"AFNkYAYA"}
I0607 16:03:14.573805   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":1,"Type":1,"Flags":0,"IP":"100.96.7.24","HardwareAddr":null}
I0607 16:03:14.573821   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":2,"Type":1,"Flags":0,"IP":"100.96.1.0","HardwareAddr":"AFNkYAEA"}
I0607 16:03:14.573836   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":8,"Type":1,"Flags":0,"IP":"100.96.3.16","HardwareAddr":"AFNkYAMA"}
I0607 16:03:14.573853   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":32,"Type":1,"Flags":0,"IP":"100.96.6.9","HardwareAddr":null}
I0607 16:03:14.573868   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":2,"Type":1,"Flags":0,"IP":"100.96.7.32","HardwareAddr":"AFNkYAcA"}
I0607 16:03:14.573878   32517 neigh_table.go:41] Actual layer2 entry: {"LinkIndex":4,"Family":2,"State":16,"Type":1,"Flags":0,"IP":"100.96.7.8","HardwareAddr":"AFNkYAcA"}

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.