| 23 Jun 2026 |
matthewcroughan | result of that is 6: eogre@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65469 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether e6:69:2f:e1:80:8d brd ff:ff:ff:ff:ff:ff inet6 fe80::e469:2fff:fee1:808d/64 scope link proto kernel_ll valid_lft forever preferred_lft forever | 19:17:31 |
matthewcroughan | You want me to add an IP address to that interface eogre@NONE ? | 19:18:07 |
matthewcroughan | Why is it @NONE anyway? | 19:18:10 |
Nico | Yea, and now do the other site | 19:18:13 |
Nico | You can use fe80::e469:2fff:fee1:808d%eogre from the other side | 19:18:25 |
Nico | * You should be able to ping fe80::e469:2fff:fee1:808d%eogre from the other side | 19:18:32 |
matthewcroughan | oh link-local nice | 19:18:39 |
matthewcroughan | I can, that works | 19:18:50 |
matthewcroughan | So is that link-local stuff going over ygg? | 19:18:58 |
matthewcroughan | looks like it since the response time is 50ms | 19:19:10 |
Nico | yea, gre encapsulated. If you don't know how it looks like, I suggest opening wireshark and inspecting the headers | 19:19:26 |
matthewcroughan | interesting | 19:19:50 |
matthewcroughan | the link local ping stops working after adding eth0 and the gre to the bridge | 19:21:03 |
casey © | how about a ping to your default gateway | 19:21:17 |
matthewcroughan | the v4 default gateway? | 19:22:16 |
casey © | yes. | 19:22:31 |
matthewcroughan | I mean these are VMs, isn't that supposed to not wor | 19:22:39 |
matthewcroughan | * I mean these are VMs, isn't that supposed to not work? | 19:22:41 |
Nico | I assume: Once you create the bridge, eth0 (which is required for tun0 to work properly) is probally going down (because it has now br0 set as master), this way the ygg tunnel can no longer be established which results in the gre no longer working | 19:22:41 |
casey © | ^^ | 19:22:55 |
matthewcroughan | Ah shit | 19:23:03 |
Nico | Have you tried to implement casey's suggestion and move the ip to br0? | 19:23:04 |
matthewcroughan | When I do all this, it gains v6 addrs somehow | 19:23:24 |
matthewcroughan | 7: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 56:48:9d:c6:b9:8c brd ff:ff:ff:ff:ff:ff
inet6 fec0::ea9b:fdab:5a11:be17/64 scope site temporary dynamic
valid_lft 86249sec preferred_lft 14249sec
inet6 fec0::5448:9dff:fec6:b98c/64 scope site dynamic mngtmpaddr proto kernel_ra
valid_lft 86249sec preferred_lft 14249sec
inet6 fe80::5448:9dff:fec6:b98c/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
| 19:23:25 |
Nico | I guess you have RA's configured on your lan | 19:23:50 |
matthewcroughan | these are VMs, so nah :P | 19:24:01 |
matthewcroughan | doubt it | 19:24:03 |
matthewcroughan | not sure where those addrs are comoing from | 19:24:15 |
matthewcroughan | * not sure where those addrs are coming from | 19:24:17 |
Nico | I thought this was the real device? | 19:24:18 |