Navigation

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

    Arp bug pfsense 2.5.0

    webGUI
    4
    12
    238
    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.
    • V
      VioletDragon last edited by

      Hi folks,

      Ive updated to 2.5.0 but ive noticed a bug in Arp Section its all duplicated on Mac Address and IPs per VLANs,

      Screenshot from 2021-02-20 14-06-52.png

      V 1 Reply Last reply Reply Quote 0
      • V
        VioletDragon @VioletDragon last edited by

        I cleared the Arp but its still broken, Hosts have IPs and the IPs are duplicated

        Screenshot from 2021-02-20 17-44-54.png

        johnpoz T 2 Replies Last reply Reply Quote 0
        • johnpoz
          johnpoz LAYER 8 Global Moderator @VioletDragon last edited by

          I am not seeing this - maybe something related to LAGG, which I do not have setup.

          V 1 Reply Last reply Reply Quote 0
          • V
            VioletDragon @johnpoz last edited by

            @johnpoz I am also having problems with DHCP randomly stopping, if i start DHCP then unbound does the same, i have noticed that the DHCP is constantly restarting from what i am seeing under the logs, i never had this problem is 2.4.5, Here is the log from DHCP as you can see its constantly restarting i need LAGG for my Ha Setup im thinking of going back to 2.4.5 because this is seriously broken

             Feb 20 17:57:21 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:57:20 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:56:18 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:56:17 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:55:16 	dhcpd 	35189 	DHCPACK on 192.168.1.31 to fc:ec:da:1c:a3:1d via lagg0
Feb 20 17:55:16 	dhcpd 	35189 	DHCPREQUEST for 192.168.1.31 from fc:ec:da:1c:a3:1d via lagg0
Feb 20 17:55:14 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:55:13 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:55:12 	dhcpd 	35189 	DHCPACK on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:12 	dhcpd 	35189 	DHCPREQUEST for 192.168.50.100 (192.168.50.254) from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:12 	dhcpd 	35189 	reuse_lease: lease age 11 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:55:12 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:12 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:12 	dhcpd 	35189 	reuse_lease: lease age 11 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:55:08 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:08 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:08 	dhcpd 	35189 	reuse_lease: lease age 7 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:55:04 	dhcpd 	35189 	DHCPACK on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:04 	dhcpd 	35189 	DHCPREQUEST for 192.168.50.100 (192.168.50.254) from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:04 	dhcpd 	35189 	reuse_lease: lease age 3 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:55:01 	dhcpleases 	8497 	Sending HUP signal to dns daemon(79151)
Feb 20 17:55:01 	dhcpd 	35189 	DHCPACK on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:01 	dhcpd 	35189 	DHCPREQUEST for 192.168.50.100 (192.168.50.254) from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:00 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:55:00 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:54:56 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:54:56 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:54:54 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:54:54 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:54:09 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:54:08 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:53:04 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:53:03 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:52:01 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:52:00 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:50:57 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:50:56 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:49:53 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:49:52 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:48:49 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:48:48 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:47:44 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:47:43 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:46:41 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:46:40 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:45:36 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:45:35 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:44:32 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:44:31 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:43:27 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:43:26 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:42:39 	dhcpd 	35189 	DHCPACK on 192.168.1.5 to 1e:45:25:44:39:a4 via lagg0
Feb 20 17:42:39 	dhcpd 	35189 	DHCPREQUEST for 192.168.1.5 from 1e:45:25:44:39:a4 via lagg0
Feb 20 17:42:23 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:42:22 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:41:20 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:41:19 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:40:17 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:40:16 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:39:13 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:39:12 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:39:09 	dhcpleases 	8497 	Sending HUP signal to dns daemon(79151)
Feb 20 17:39:09 	dhcpleases 	8497 	Sending HUP signal to dns daemon(79151)
Feb 20 17:39:09 	dhcpd 	35189 	DHCPACK on 192.168.80.112 to 00:1e:67:8b:cb:d2 (DCMI) via lagg0.80
Feb 20 17:39:09 	dhcpd 	35189 	Wrote 100 leases to leases file.
Feb 20 17:39:09 	dhcpd 	35189 	Wrote 0 new dynamic host decls to leases file.
Feb 20 17:39:09 	dhcpd 	35189 	Wrote 0 deleted host decls to leases file.
Feb 20 17:39:09 	dhcpd 	35189 	Wrote 0 class decls to leases file.
Feb 20 17:39:09 	dhcpd 	35189 	DHCPREQUEST for 192.168.80.112 from 00:1e:67:8b:cb:d2 (DCMI) via lagg0.80
Feb 20 17:38:32 	dhcpd 	35189 	DHCPACK on 192.168.100.1 to b8:27:eb:6f:f5:37 via lagg0.100
Feb 20 17:38:32 	dhcpd 	35189 	DHCPREQUEST for 192.168.100.1 from b8:27:eb:6f:f5:37 via lagg0.100
Feb 20 17:38:30 	dhcpd 	35189 	DHCPACK on 192.168.80.4 to dc:a6:32:3d:d2:56 via lagg0.80
Feb 20 17:38:30 	dhcpd 	35189 	DHCPREQUEST for 192.168.80.4 from dc:a6:32:3d:d2:56 via lagg0.80
Feb 20 17:38:10 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:38:09 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:37:06 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:37:05 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:36:03 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:36:02 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:34:58 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:34:57 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:33:53 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:33:52 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:32:49 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:32:48 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:31:44 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:31:43 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:31:29 	dhcpd 	35189 	DHCPACK on 192.168.1.1 to 00:17:08:7d:2e:9b via lagg0
Feb 20 17:31:29 	dhcpd 	35189 	DHCPREQUEST for 192.168.1.1 from 00:17:08:7d:2e:9b via lagg0
Feb 20 17:31:29 	dhcpd 	35189 	uid lease 192.168.1.194 for client 00:17:08:7d:2e:9b is duplicate on 192.168.1.0/24
Feb 20 17:30:40 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:30:39 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:29:37 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:29:36 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:28:32 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:28:31 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:27:28 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:27:27 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:26:24 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:26:23 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:25:53 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:53 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:53 	dhcpd 	35189 	reuse_lease: lease age 3304 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:25:37 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:37 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:37 	dhcpd 	35189 	reuse_lease: lease age 3288 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:25:29 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:29 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:29 	dhcpd 	35189 	reuse_lease: lease age 3280 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:25:24 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:24 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:24 	dhcpd 	35189 	reuse_lease: lease age 3275 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:25:21 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:25:20 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:25:19 	dhcpd 	35189 	DHCPOFFER on 192.168.50.100 to c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:19 	dhcpd 	35189 	DHCPDISCOVER from c0:8c:71:7e:93:82 via lagg0.50
Feb 20 17:25:19 	dhcpd 	35189 	reuse_lease: lease age 3270 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.50.100
Feb 20 17:24:17 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:24:16 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:24:04 	dhcpleases 	8497 	Sending HUP signal to dns daemon(79151)
Feb 20 17:24:04 	dhcpd 	35189 	DHCPACK on 192.168.101.108 to 28:33:34:e1:0b:7f (HONOR_20_Lite-19d70ea088e) via lagg0.101
Feb 20 17:24:04 	dhcpd 	35189 	DHCPREQUEST for 192.168.101.108 from 28:33:34:e1:0b:7f (HONOR_20_Lite-19d70ea088e) via lagg0.101
Feb 20 17:23:12 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:23:11 	dhcpd 	35189 	DHCPDISCOVER from f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
Feb 20 17:22:09 	dhcpd 	35189 	DHCPOFFER on 192.168.80.113 to f6:d2:f7:db:12:f5 (tvheadendsrv) via lagg0.80
            1 Reply Last reply Reply Quote 0
            • T
              tomashk @VioletDragon last edited by tomashk

              @violetdragon
              I have similar problem in arp table. It happens only for addresses which currently are static but some time ago were assigned by DHCP.

              I looked in the code of diag_arp.inc and it looks that function system_get_dhcpleases (called in prepare_ARP_table) is returning double entries for one mac:

              • old - with "type" == "dynamic", "act" == "expired" and "online" == "offline"
              • new - with "type" == "static", "act" == "static" and "online" == "online"

              As an experiment I made this patch (based on v2.5.0 git tag) and at least host name column looks good but I don't have enough knowledge to tell if this is correct solution. But maybe it will point somebody to proper fix.

              diff --git a/src/etc/inc/web/diag_arp.inc b/src/etc/inc/web/diag_arp.inc
index 58b7a6a7eb..0eab914a8c 100644
--- a/src/etc/inc/web/diag_arp.inc
+++ b/src/etc/inc/web/diag_arp.inc
@@ -59,8 +59,11 @@ function prepare_ARP_table($json = false) {
 	$dhcpip = array();
 
 	foreach ($leases['lease'] as $value) {
-		$dhcpmac[$value['mac']] = $value['hostname'];
-		$dhcpip[$value['ip']] = $value['hostname'];
+		if ($value["act"] != "expired")
+		{
+			$dhcpmac[$value['mac']] = $value['hostname'];
+			$dhcpip[$value['ip']] = $value['hostname'];
+		}
 	}
 
 	$arp_table = system_get_arp_table();

              It can be tested with Patches package.

              V 1 Reply Last reply Reply Quote 1
              • V
                VioletDragon @tomashk last edited by

                @tomashk Hi, thanks for your reply, as it seems its cosmetic something to ask tho did you do a direct upgrade from 2.4.5 to 2.5.0 or did you do a fresh install?

                Thanks.

                Jack.

                T 1 Reply Last reply Reply Quote 0
                • T
                  tomashk @VioletDragon last edited by

                  @violetdragon said in Arp bug pfsense 2.5.0:

                  @tomashk Hi, thanks for your reply, as it seems its cosmetic something to ask tho did you do a direct upgrade from 2.4.5 to 2.5.0 or did you do a fresh install?

                  Thanks.

                  Jack.

                  I upgraded. I do fresh install only if upgrade breaks something for me.

                  V 1 Reply Last reply Reply Quote 0
                  • V
                    VioletDragon @tomashk last edited by

                    @tomashk Ok cool as it seems this bug maybe showing up on a upgrade, i did a reinstall on a test box and this bug is not there.

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      tomashk @VioletDragon last edited by tomashk

                      @violetdragon said in Arp bug pfsense 2.5.0:

                      @tomashk Ok cool as it seems this bug maybe showing up on a upgrade, i did a reinstall on a test box and this bug is not there.

                      I read somewhere that it might be fixed also by going to Status -> DHCP Leases and using Clear all DHCP Leases. The problem that I found in the code looks like situation when expired leases are not ignored when finding host names. But as I'm looking at this code for the first time you can think about it as just educated guess :)

                      V 1 Reply Last reply Reply Quote 1
                      • V
                        VioletDragon @tomashk last edited by

                        @tomashk I will try that, i would do a fresh install of 2.5.0 but not as easy as that due to SSL Certs for Web and Mail Servers so. I could probably just re-generate them but dont like messing with things that is working.

                        1 Reply Last reply Reply Quote 0
                        • jimp
                          jimp Rebel Alliance Developer Netgate last edited by

                          Can you open a bug report on https://redmine.pfsense.org with the details of this issue? Put a link back to this forum thread on the entry when creating it.

                          T 1 Reply Last reply Reply Quote 0
                          • T
                            tomashk @jimp last edited by tomashk

                            @jimp ok, will do in a few minutes

                            Edit:
                            Created - https://redmine.pfsense.org/issues/11510

                            1 Reply Last reply Reply Quote 1
                            • First post
                              Last post

                            Products

                            • Platform Overview
                            • TNSR
                            • pfSense Plus
                            • Appliances

                            Services

                            • Training
                            • Professional Services

                            Support

                            • Subscription Plans
                            • Contact Support
                            • Product Lifecycle
                            • Documentation

                            News

                            • Media Coverage
                            • Press
                            • Events

                            Resources

                            • Blog
                            • FAQ
                            • Find a Partner
                            • Resource Library
                            • Security Information

                            Company

                            • About Us
                            • Careers
                            • Partners
                            • Contact Us
                            • Legal
                            Our Mission

                            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                            Subscribe to our Newsletter

                            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                            © 2021 Rubicon Communications, LLC | Privacy Policy