Navigation

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

    Odd error?

    2.0-RC Snapshot Feedback and Problems - RETIRED
    2
    3
    1404
    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.
    • johnpoz
      johnpoz LAYER 8 Global Moderator last edited by

      odd

      Mar 20 20:55:09 inetd[36719]: 19000/tcp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19000/tcp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19000/udp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19000/udp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19001/tcp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19001/tcp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19002/tcp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19002/tcp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19002/udp: bind: Address already in use
      Mar 20 20:55:09 inetd[36719]: 19002/udp: bind: Address already in use
      Mar 20 20:45:09 inetd[36719]: 19000/tcp: bind: Address already in use
      Mar 20 20:45:09 inetd[36719]: 19000/tcp: bind: Address already in use
      Mar 20 20:45:09 inetd[36719]: 19000/udp: bind: Address already in use

      Have to look into what is causing this?

      But I have also had to turn off dhcp and dhcpv6 because having weird problems… at first thought it was just ipv6 issues, but now I have a currentcost envi bridge, and it was having issues getting dhcp.  So I turned of all dhcp and dropped back to using my windows server dhcp server... I would really rather use the pfsense box for dhcp both ipv4 and v6, but with all the errors Im seeing in the log - have to drop back to using windows dhcp server.

      I see this.

      Mar 20 13:20:02 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:20:02 dhcpd: DHCPREQUEST for 192.168.1.240 (192.168.1.253) from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:20:02 dhcpd: DHCPOFFER on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:20:02 dhcpd: DHCPDISCOVER from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:50 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:50 dhcpd: DHCPREQUEST for 192.168.1.240 (192.168.1.253) from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:50 dhcpd: DHCPOFFER on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:50 dhcpd: DHCPDISCOVER from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:38 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:38 dhcpd: DHCPREQUEST for 192.168.1.240 (192.168.1.253) from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:38 dhcpd: DHCPOFFER on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:38 dhcpd: DHCPDISCOVER from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:26 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:26 dhcpd: DHCPREQUEST for 192.168.1.240 (192.168.1.253) from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:26 dhcpd: DHCPOFFER on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:26 dhcpd: DHCPDISCOVER from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:13 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:13 dhcpd: DHCPREQUEST for 192.168.1.240 (192.168.1.253) from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:13 dhcpd: DHCPOFFER on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:13 dhcpd: DHCPDISCOVER from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:01 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:01 dhcpd: DHCPREQUEST for 192.168.1.240 (192.168.1.253) from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:01 dhcpd: DHCPOFFER on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:19:01 dhcpd: DHCPDISCOVER from 7f:bf:a9:aa:29:5b via re0
      Mar 20 13:18:49 dhcpd: DHCPACK on 192.168.1.240 to 7f:bf:a9:aa:29:5b via re0

      Currently running
      2.0-RC1-IPv6 (i386)
      built on Fri Mar 18 21:32:32 EDT 2011

      I need to update sure, and run a gitsync - not sure if issues are ipv6 related - but was seeing problems with this ipv4 dhcp even after disabled dhcpv6.  Just don't have time to play with it at the moment so just turned off dhcp and running it off windows box for now that is not having any issues with the clients.

      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 23.01 | Lab VMs CE 2.6, 2.7

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

        The inetd issue is from NAT reflection and was probably fixed by this commit:
        https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/650b573bd8a435449178385a2d132f7f0002d309

        The DHCP part is likely unrelated but hard to say. If you try again on a current snapshot you'd probably get better results.

        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
        • johnpoz
          johnpoz LAYER 8 Global Moderator last edited by

          I'll try the latest snap this weekend and turn the dhcp stuff back on and see if still having had problems.

          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 23.01 | Lab VMs CE 2.6, 2.7

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