Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    04[NET] error writing to socket: Permission denied

    Scheduled Pinned Locked Moved IPsec
    1 Posts 1 Posters 155 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      marcfunk
      last edited by

      Hello all!

      We have 3 brand new Base 4200 and config IP-Sec between all Bases.

      Base #1 = 192.168.40.254
      Base #2 = 192.168.50.254
      Base #3 = 192.168.110.254

      Alle bases have a FritzBox as modem with port forwarding for ESP, UDP 500 and UDP 4500.

      Base #1 and Base #2 can connect each other,
      Base #1 and Base #3 cannot connect.
      Base #2 and Base #3 cannon connect.

      In der System Log at Base #3 there is following logged:

      Nov 3 12:43:25 	charon 	68723 	10[IKE] <con1|1> retransmit 1 of request with message ID 0
      Nov 3 12:43:25 	charon 	68723 	10[NET] <con1|1> sending packet: from 192.168.xx.xx[500] to 109.xx.xx.xx[500] (500 bytes)
      Nov 3 12:43:25 	charon 	68723 	04[NET] error writing to socket: Permission denied
      Nov 3 12:43:26 	charon 	68723 	14[CFG] vici client 30 disconnected
      Nov 3 12:43:30 	charon 	68723 	14[CFG] vici client 32 connected
      Nov 3 12:43:30 	charon 	68723 	10[CFG] vici client 32 registered for: list-sa
      Nov 3 12:43:30 	charon 	68723 	14[CFG] vici client 32 requests: list-sas
      Nov 3 12:43:30 	charon 	68723 	10[CFG] vici client 32 disconnected
      Nov 3 12:43:33 	charon 	68723 	14[IKE] <con1|1> retransmit 2 of request with message ID 0
      Nov 3 12:43:33 	charon 	68723 	14[NET] <con1|1> sending packet: from 192.168.xx.xx[500] to 109.xx.xx.xx[500] (500 bytes)
      Nov 3 12:43:33 	charon 	68723 	04[NET] error writing to socket: Permission denied  
      

      I have reset the Base #3 and config it completely new. Also i have renew the config of ipsec tun on both sides. But he still write "error writing to socket".
      In the past there was errors like this, but there wasn't really a solution.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.