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

    [SOLVED] pfSense SG-1000 lan-interface missing IP with snapshot 20171007

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    24 Posts 7 Posters 4.2k 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.
    • GrimsonG
      Grimson Banned
      last edited by

      Keep your hands away from x86 CE build 2.4.0.r.20171008.0625 IPv4 is broken in it you can't even assign an IPv4 address to an interface with it.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Yes, you won't be able to see that until the factory repos are updated.

        Thanks for the feedback on 2.4.0.r.20171008.0625  :-\

        Steve

        1 Reply Last reply Reply Quote 0
        • GrimsonG
          Grimson Banned
          last edited by

          Build 2.4.0.r.20171008.0640 seems to be working fine now.

          Edit: It seems this build has problems with traffic shaping, I'm using HFSC queues but Status -> Queues can't find any statistics. Ping seems to suffer under traffic so it seems the queues aren't working at all.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Yes I just installed .640 and it seemed to run OK. I am certainly able to assign IPs to interfaces.

            If you run:

            pfctl -f /tmp/rules.debug

            Does it return clean or with any errors?

            Steve

            1 Reply Last reply Reply Quote 0
            • GrimsonG
              Grimson Banned
              last edited by

              Sorry, I already went back to build 2.4.0.r.20171006.1536 as I need traffic shaping to keep my rather slow DSL connection in a decent state (see my edit above).

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Ok, no problem.

                I ran the shaping wizard and setup queues using both PRIQ and HSFC and they came up as expected.

                If you see it again try to grab whatever data you can get. Reload the ruleset manually as shown above. Open a bug report.

                Steve

                1 Reply Last reply Reply Quote 0
                • K
                  kpa
                  last edited by

                  Logging is broken on 2.4.0-RC-amd64-20171008-0640. This is a clean install on ZFS with the configuration restored after first boot:

                  
Starting syslog...done.
Oct  8 18:26:24  syslogd: /var/log/routing.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/ntpd.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/gateways.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/resolver.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/dhcpd.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/filter.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/nginx.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/dhcpd.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/system.log: Operation not supported by device

                  The system works otherwise but no logs are shown in the webgui.

                  I have already tried reset logs but no difference.

                  1 Reply Last reply Reply Quote 0
                  • K
                    kpa
                    last edited by

                    Another full reinstall, this time using the config rescue option. No difference, syslogd still spits out the same errors.

                    1 Reply Last reply Reply Quote 0
                    • L
                      lololo
                      last edited by

                      @kpa:

                      Another full reinstall, this time using the config rescue option. No difference, syslogd still spits out the same errors.

                      Same problem… clean install on a vm
                      Have you found a solution?

                      1 Reply Last reply Reply Quote 0
                      • K
                        kpa
                        last edited by

                        @lololo:

                        @kpa:

                        Another full reinstall, this time using the config rescue option. No difference, syslogd still spits out the same errors.

                        Same problem… clean install on a vm
                        Have you found a solution?

                        Upgrade to the 2.4 release version and reset your log files.

                        1 Reply Last reply Reply Quote 0
                        • B
                          bastolino
                          last edited by

                          Hi Guys
                          Thank you for that fix - I honestly thought I made a brick  :o

                          Best wishes
                          Bastolino

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