I have a working connection from my laptop to work.
The laptop is kubuntu.
I can connect from home and my phone, connect to internet, rdp and network shares.
And all other wifi’s I have connect to.
But from 1 network, I just get rejected. It is a simple home network, just like the one I have at my own home.
I only get “Connection lost” from the rdp client.
I found on myip.com that this connection have an ipv6 address, and thought “this must be it, I need to abandon ipfire”. But my own home also have ipv6, and here it works.
This lets me have hope to stay on ipfire, but also leave me with no clue how to get further.
One thing worth checking is whether that network is IPv6-only. Most places that use IPv6 still offer IPv4 as well, but if this one doesn’t, your connection won’t work with IPFire.
Sometimes, when I try to connect with WireGuard, no connection is established. I have to remotely access the IPFire console (I have a rule on port 444) and disable/enable the WireGuard client that isn’t connecting. After that, it works until the next time, when I have to do the same thing.
I will try this next time I have the issue, but if it’s a server side issue it shouldn’t work if I just switch to a connection via my phone. Should it?
No, nothing works. I can only get it working again by doing what I mentioned. I checked to see if there was a log, but it doesn’t have its own. I thought to myself… selfishly, I’m sure some other user is complaining.
If you tell me where to look, I’ll check it next time I’m here.
IPFire really loses it’s spark with ipv6. Please, add support for ipv6 to IPFire. I know it’s a herculean task but it must be done sooner rather than later because later may well be too late to matter.
I’m sure everyone agrees with you. Including the developers, but the resources must be available. I stay as long as I can and donate every now and then.
BTW: I had a thought that I need to test next time I have the issue and will return. If I’m correct it may not be ipv6 related at all
Well, without having any data, I don’t think it’s related to IPv6, since, as I mentioned, in my case, it’s temporarily resolved by disabling and re-enabling the client. It’s as if the connection gets stuck.
What I don’t know is what to look for when this happens.