Navigation

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

    Gibberish for hostname in logs since I put on 2.1.4

    General pfSense Questions
    2
    6
    1000
    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
      Moosecall last edited by

      all of my log entries are showing the following gibberish instead of the hostname

      CPE00e06f126c0f-CM8c04ff1ae6a4 lighttpd[77441]: (connections.c.137) (warning) close: 17 Connection reset by peer

      I tried changing the hostname to something else and back but still the same.  The hostname does seem to show up properly in an SSH session however.

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • M
        Moosecall last edited by

        So this morning I SSH into the firewall and now the prompt is messed up as well

        [2.1.4-RELEASE][admin@CPE00e06f126c0f-CM8c04ff1ae6a4]/root(1):

        editing the hostname under the general setup tab fixed it, but logs still messed up.

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

          Perhaps it's being set by DHCP?

          clog /var/log/dhcpd.log  | grep -i hostname
          

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • M
            Moosecall last edited by

            Looks like it is DHCP

            [2.1.4-RELEASE][admin@CPE00e06f126c0f-CM8c04ff1ae6a4]/root(1): clog /var/log/dhcpd.log  | grep -i hostname
            Jul  6 05:41:13 lucius dhclient: New Hostname (re0): CPE00e06f126c0f-CM8c04ff1ae6a4
            Jul  7 05:41:13 lucius dhclient: New Hostname (re0): CPE00e06f126c0f-CM8c04ff1ae6a4

            re0 is my WAN so that is probably the hostname being assigned by my ISP, I guess something changed in 2.1.4 that impacted this?  Better question is how to make pfsense ignore that hostname and just use the one I give it.  If it matters I am running a 6rd tunnel to my ISP on the WAN as well.

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

              garga put in a fix for this last night, you can use the System Patches package to apply the patch to correct the behavior.

              https://github.com/pfsense/pfsense/commit/7b15d22967a9f9fefe7b8b11fa2d68c762c55219

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • M
                Moosecall last edited by

                That did the trick, thank you.

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