L2TP: Control connection 0x803859310 destroyed
-
Nothing has been done on the radius server and the latest version of freeradius is being used. I don't think there will be a situation there.
-
-
Have you tried https://redmine.pfsense.org/issues/10710 patch?
Are there any changes on your clients?
Why aren't you using IKEv2 for your clients?
Are you able to connect from other pfSense appliance?
You can install pfSense VM and check L2TP connection as meAlso try to use FreeRADIUS pkg for testing
-
@viktor_g Hello Viktor
I trying this methods and not running. Sorry.
-
I started to tamper with the problem and I could not understand what to do with this method. I understand that I just need to delete the secret key. Is it correct? If it is true, it does not work, unfortunately.
-
@erselbey You need to apply Patch ID 58b9baeef7281ba19fafdc790344d4c3d03e1541 first, see https://docs.netgate.com/pfsense/en/latest/development/system-patches.html, then delete Secret key
You can also test it with another pfSense appliance as L2TP client
-
Even though I applied the patch, it still doesn't work. Radius server is running smoothly.
-
@erselbey still unable to reproduce
try to disable accounting,
try to create L2TP VPN server on the latest 2.5 snapshot -
@viktor_g This still did not solve my problem and. Version 2.5.0 does not seem to have a future.
-
@erselbey need more information
What are your L2TP clients? Configuration/firewall? Behind NAT?
Have you tested it with pfSense L2TP client?
RADIUS server version/configuration? -
@viktor_g It would be appropriate if I said I did all of what they said. I've tested everything imaginable, but the 2.4.5 version still has a problem. Even the patch didn't work. Isn't there a video about this?
-
@viktor_g macOS IPSec L2TP kullanıyorum ikev1
Freeradius 3.0
Pfsens’in önünde her hangi bir engel yok. Aynı ayarlara configürasyon yedeğinden geri döndüm ve bu güncellemeden sonra ciddi sıkıntı çıkartmaya başladı bana. -
@erselbey Please show IPsec configuration
-
@viktor_g of course
-
@erselbey Looks good
Please test it with another client, i.e. Windows, Linux or pfSense
Seems like client issue -
@viktor_g I don't think this is related to client.
-
@erselbey said in L2TP: Control connection 0x803859310 destroyed:
@viktor_g I don't think this is related to client.
You should test it with other clients
-
@viktor_g I tried it on windows and ubuntu and it didn't work.
-
I solved the problem. After installing the patch, I added Pre Shared Key on the IPsec side and the problem was resolved.
https://forum.netgate.com/topic/154841/l2tp-issue-since-last-update
