-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public IP firewalls wrong IPv6 #1191
Comments
Can you give the output of |
This is the output of
And this is
|
strange... I can ping all these IPs, the more , they're in the same segment/prefix, so I can't figure out what's happening to you unless I have access to the vms themselves |
deploying a veth pair on the node which imitates the VM network setup works fine to ping the db, so as @delandtj said we'd need access to the vm itself to figure out what is happening. SSH keys are on our user profiles, please add them |
Seems at some point the firwalling rules got messed up and use an yggdrasil IP instead of the predicted SLAAC IP. this causes all ip6 from public IPs to be dropped ip6 saddr . ether saddr != { 300:596a:6375:dea:3c1f:efff:fe86:7d4c . 3e:1f:ef:86:7d:4c } counter packets 10475 bytes 781820 drop the 300:: ip is an yggdrasil ip which is currently not set, and should be something like |
Signed-off-by: Lee Smet <lee.smet@hotmail.com>
Supposed fix is merged, newly deployed vm's with public IP's should work now (once the update is propagated in about 15 mins) |
Closing because issue is not happening anymore. |
I can ping this ZDB from the worker node but it doesn't work on the master. Another ZDB is pingable from both.
![Screenshot from 2021-02-17 15-24-33](https://user-images.githubusercontent.com/13040543/108213211-71201500-7137-11eb-8906-504c33cad22f.png)
Master wid: 30564
Worker wid: 30565
The text was updated successfully, but these errors were encountered: