uhm...I think I just found a hilariously horrible bug, can anyone reproduce it?
-
so, I'm not a stranger to finding strange ways to break shit...but this one just caught me horribly off guard, and I'm sitting here both in bewilderment and entertainment... so, I just randomly managed to kill my entire networks internet, not a new feat, but the way in which this seemingly just happened IS new, and freaking hilarious... and I would like to see if someone can replicate this, because either I just had a stroke and woke up, or I just found a hilariously strange bug
so, I was trying to re-setup my vpn, surfshark if its important to know, and the way I connect to them is with an openvpn client config, that then uses policy based routing.
I THINK, the bug was me trying to name Surfshark for the interface name, not sure if I have used single caps at the beginning before or not, but in my attempts to figure out what broke my net, I renamed its description from "Surfshark" to "vpn" and then my internet fixed itself... so...not sure what the heck to make of this, but if this truely is a bug, I want to make a post about it to see if someone can replicate this, or if I just found another strange one off issue that nobody else can replicate (also not an uncommon feat for me for some reason...still dont know how or why I'm so skilled at this kind of issue/talented in finding ways to have things go wrong that nobody else can manage to do, but it is what it is)
-
What version are you seeing that in?
Can you repeat it?
What actually broke when you did that?
I assume you can still reach the gui since you were able to change it back. So LAN was working.
Traffic not policy routed over the VPN still worked?
Did you see any errors logged?
The actual interface name and gateway is all upper case anyway.
Steve
-
@stephenw10 latest update, normal traffic works, but for the life of me I cannot get my vpn fixed again, still trying to figure out why...all I did was pull out an ethernet card, it should NOT be this dang difficult to change pre-existing working rules and configs to use an alternate ethernet port, but here I am....somehow....
-
One step at a time is the way to go
What port are you changing? If it's using the same driver as another NIC in the system be aware the interface order may change.
Steve
-
@stephenw10 nevermind, unless someone can replicate this, I think I found the issue, and as much as I want to claim I still think its a bug, now I'm not so sure...seems that I was having sporatic connectivity, and that was leading it to ACT like it was not working, when it in fact was, just very very limited, and few and very far between in doing so....
so unless someone can replicate this, I do not think this is a bug anymore, or at least have enough doubt to not think its a bug still...not totally sure, but in any case I seem to have fixed the underlying problem I was having.
as for what port, yea, I'm aware, both cards, old and new, are intel IX driver based cards, both quad gigabit adapters, so I just had to change the interface everything was mapped to, but the prior issues led me to believe something else entirely was going on... but yea, same driver, I'm aware of that one, thank you! interface order did change, and I was trying to update things to the new interface, which had worked, up till I noticed my vpn issues...not sure what the bottom line issue was for that, but its fixed at least.
