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

DHCP Static Mapping - "Edit" brings up empty form

Scheduled Pinned Locked Moved DHCP and DNS
9 Posts 4 Posters 463 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.
  • J
    jhg-goow
    last edited by jhg-goow Dec 29, 2022, 11:53 PM Dec 29, 2022, 11:49 PM

    Community Edition 2.6.0-RELEASE (amd64)

    Clicking the "edit" (pencil) icon in a static mapping brings up an empty static mapping form. I would expect the form would be pre-populated with the data for that static mapping:

    pfsense01.png

    pfsense02.png

    Am I doing something wrong?

    J 1 Reply Last reply Dec 30, 2022, 12:00 AM Reply Quote 0
    • J
      johnpoz LAYER 8 Global Moderator @jhg-goow
      last edited by johnpoz Dec 30, 2022, 12:03 AM Dec 30, 2022, 12:00 AM

      @jhg-goow I would think something to do with your browser, cache maybe..

      when you click it what actual url are you getting? For example if I open one to edit the url is

      edit.jpg

      edit: BTW you using faststone for your images?

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.7.2, 24.11

      J 1 Reply Last reply Dec 30, 2022, 12:09 AM Reply Quote 0
      • J
        jhg-goow @johnpoz
        last edited by jhg-goow Dec 30, 2022, 12:10 AM Dec 30, 2022, 12:09 AM

        @johnpoz Hmmm.... it fails in Firefox but not in Edge.

        I see the same URL in both browsers, but in Firefox the entry fields are empty.

        Examining the source HTMLfor the page, I see that pfSense sent different HTML. In Firefox, the input field for the MAC Address is

        <input class="form-control" name="mac" id="mac" type="text" placeholder="xx:xx:xx:xx:xx:xx">
        

        while in Edge, the same HTML is

        	<input class="form-control" name="mac" id="mac" type="text" value="a4:bb:6d:e3:46:da" placeholder="xx:xx:xx:xx:xx:xx">
        

        For some reason, it's sending different HTML, probably depending on the user-agent string. AFAIK, that couldn't be related to caching, and appears to be originating at the server, not in the client.

        J 1 Reply Last reply Dec 30, 2022, 12:13 AM Reply Quote 0
        • J
          johnpoz LAYER 8 Global Moderator @jhg-goow
          last edited by Dec 30, 2022, 12:13 AM

          @jhg-goow well I am using firefox so I doubt it a firefox thing specifically..

          I'm on 108.0.1 but I have never seen any issues with firefox and the pfsense gui.

          I would for good measure just delete you firefox cache - what could it hurt..

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.7.2, 24.11

          J 2 Replies Last reply Dec 30, 2022, 12:25 AM Reply Quote 0
          • J
            jhg-goow @johnpoz
            last edited by Dec 30, 2022, 12:25 AM

            @johnpoz Clearing cache in Firefox does not help.

            I saved the rendered HTML from both browsers and compared them in WinMerge... there are only three salient differences, comprising the three missing value= attributes.

            (There are a couple of other diffs, one being the CSRF token and the edit index reflecting that I accidentally chose a different entry to edit in MSEdge). Otherwise the HTMLs are identical).

            I've attached a zip with both files.

            pfsense-samples.zip

            1 Reply Last reply Reply Quote 0
            • J
              jhg-goow @johnpoz
              last edited by jhg-goow Dec 30, 2022, 12:41 AM Dec 30, 2022, 12:39 AM

              @johnpoz Also, looking at the network traces in the browser's debuggers, I see that the values are actually present in the response to the first GET in MSEdge, but missing at the same point in Firefox.

              Here are the .har files for the initial request and response
              pfsense-har.zip

              As a workaround I'll use MSEdge for now.

              G 1 Reply Last reply Dec 30, 2022, 9:14 AM Reply Quote 0
              • G
                Gertjan @jhg-goow
                last edited by Dec 30, 2022, 9:14 AM

                @jhg-goow

                Another workaround : install a fresh copy of Firefox on another device.
                Use it, and see that it works for you.
                It does for me.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                1 Reply Last reply Reply Quote 0
                • B
                  Bob.Dig LAYER 8
                  last edited by Bob.Dig Dec 30, 2022, 11:56 AM Dec 30, 2022, 11:43 AM

                  Or another one, use Private Browsing without any add-ons. With that trick you still can use all your existing credentials saved in FF.

                  Although, one thing I am missing with pfSense in this regard is, that if you click on "Add static mapping", there is no IP-Address in the corresponding field. I know that pfSense doesn't allow you to use an IP from the "range", although this behavior is arguable. None the less I would find it helpful to have an IP-Address there, even if it says: "you can't have it", when you try to safe it...

                  J 1 Reply Last reply Dec 30, 2022, 8:19 PM Reply Quote 0
                  • J
                    jhg-goow @Bob.Dig
                    last edited by Dec 30, 2022, 8:19 PM

                    @bob-dig @johnpoz I tried starting in Firefox Safe Mode with all add-ons disabled... same problem

                    However, creating an entirely new profile restored the correct behavior. So it's something in my default profile, but I can't imagine what would cause FF to remove the value= attribute from an input tag.

                    Thanks for the help.

                    1 Reply Last reply Reply Quote 0
                    9 out of 9
                    • First post
                      9/9
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                      This community forum collects and processes your personal information.
                      consent.not_received