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

    Gateways - dpinger sendto error: 22

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 545 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.
    • ?
      A Former User
      last edited by

      Hello

      In the Gateways log there are constant entries with "sendto error: 22" and the status of the Gateway is accordingly "Offline, Packetloss".
      Unfortunately, we haven't found the reason for it yet.
      Since a recent configuration change that I have reverted shortly afterward, there are now also kernal errors in the general log: "arpresolve: can't allocate llinfo for 192.168.1.1 on igb1"
      Is there anything missing or wrong in the configuration as mentioned below, or is the reason of the errors more probably on the other side, i.e. at the target gateway?

      Current configuration:
      LAN IP: 192.168.0.1
      WAN static IP and WANGW: 62.2.x.x
      Virtual IP: 192.168.1.100
      Gateway: 192.168.1.1
      NAT Reflection mode for port forwards: Pure NAT
      Static Route: From Network 192.168.1.0/24 to Gateway 192.168.1.1 (Interface LAN)
      Firewall Rule: From 192.168.0.0/24 to 192.168.1.0/24 (all ports) through the Default Gateway - I tried with the Gateway 192.168.1.1 (the errors remained)
      Automatic Outbound NAT Rules: Interface WAN Source 192.168.1.0/24 & 192.168.0.0/24 and others, one entry with static port 500 for ISAKMP, one entry for all ports

      Further settings (irrelevant concerning the error):
      DNS Server: 8.8.8.8
      Alliases IP: 192.168.78.0/24 (used for a VPN-connection)
      VLAN IP: 10.20.0.1 (used for the WLAN)

      ? 1 Reply Last reply Reply Quote 0
      • ?
        A Former User @A Former User
        last edited by

        The Problem has just been solved with a reboot of the firewall.
        I hadn't considered that earlier.

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