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

    Sys Logs toont errors na clean install

    Scheduled Pinned Locked Moved
    Nederlands
    2
    3
    1.5k
    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.
    • A
      Arild
      last edited by

      Hoi,
      na een aanval op mijn unraid server hier thuis heb ik besloten om mij te verdiepen in pfsense. Ik had een amd e350m1 bordje liggen, heb op ebay een 4port intel nic gekocht en de laatste versie (2.3.2_1) van pfsense geïnstalleerd.

      De situatie: kabel van buiten => router Telenet (Belgie) => 16port 1Gbit switch => pfsense box => rasp-pi2

      Na een clean install en het doorlopen van de pfsense wizard via de webui kreeg ik het volgende te zien in de system logs:

      Status/System Logs/System/Genera:l

      Nov 16 19:40:03	xinetd	15254	Starting reconfiguration
Nov 16 19:40:03	xinetd	15254	Swapping defaults
Nov 16 19:40:03	xinetd	15254	readjusting service 6969-udp
Nov 16 19:40:03	xinetd	15254	Reconfigured: new=0 old=1 dropped=0 (services)
Nov 16 20:40:03	php-fpm	55433	/rc.newwanipv6: rc.newwanipv6: Info: starting on em0.
Nov 16 20:40:03	php-fpm	55433	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2a02:1810:bc27:a200:214:5eff:fee9:65) (interface: wan) (real interface: em0).
Nov 16 20:40:05	php-fpm	55433	/rc.newwanipv6: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em1' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.3.4 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Config file: /etc/dhcpd.conf Database file: /var/db/dhcpd.leases PID file: /var/run/dhcpd.pid Wrote 21 leases to leases file. Listening on BPF/em1/00:14:5e:e9:00:64/192.168.1.0/24 Sending on BPF/em1/00:14:5e:e9:00:64/192.168.1.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on
Nov 16 20:40:07	php-fpm	55433	/rc.newwanipv6: ROUTING: setting default route to 192.168.8.1
Nov 16 20:40:07	php-fpm	55433	/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::5e35:3bff:feb3:bfb3%em0
Nov 16 20:40:07	php-fpm	55433	/rc.newwanipv6: Removing static route for monitor fe80::5e35:3bff:feb3:bfb3 and adding a new route through fe80::5e35:3bff:feb3:bfb3%em0
Nov 16 20:40:08	check_reload_status		Reloading filter
Nov 16 19:40:09	xinetd	15254	Starting reconfiguration
Nov 16 19:40:09	xinetd	15254	Swapping defaults
Nov 16 19:40:09	xinetd	15254	readjusting service 6969-udp
Nov 16 19:40:09	xinetd	15254	Reconfigured: new=0 old=1 dropped=0 (services)
Nov 16 20:40:09	php-fpm	69301	/rc.newwanipv6: rc.newwanipv6: Info: starting on em0.
Nov 16 20:40:09	php-fpm	69301	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2a02:1810:bc27:a200:214:5eff:fee9:65) (interface: wan) (real interface: em0).

      Status/System Logs/System/Gateways:

      Nov 16 20:41:08	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:08	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:14	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:14	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:20	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:20	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:26	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:26	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:32	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:32	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:38	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:38	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:44	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:44	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:51	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:51	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "
Nov 16 20:41:57	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.8.1 bind_addr 192.168.8.226 identifier "WAN_DHCP "
Nov 16 20:41:57	dpinger		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::5e35:3bff:feb3:bfb3%em0 bind_addr fe80::214:5eff:fee9:65%em0 identifier "WAN_DHCP6 "

      Status/System Logs/System/Routing:

      Nov 16 19:42:38	radvd	44764	no auto-selected prefix on interface em1, disabling advertisements
Nov 16 19:42:38	radvd	44764	resuming normal operation
Nov 16 19:42:39	radvd	44764	attempting to reread config file
Nov 16 19:42:39	radvd	44764	no auto-selected prefix on interface em1, disabling advertisements
Nov 16 19:42:39	radvd	44764	resuming normal operation
Nov 16 19:42:44	radvd	44764	attempting to reread config file
Nov 16 19:42:44	radvd	44764	no auto-selected prefix on interface em1, disabling advertisements
Nov 16 19:42:44	radvd	44764	resuming normal operation
Nov 16 19:42:45	radvd	44764	attempting to reread config file
Nov 16 19:42:45	radvd	44764	no auto-selected prefix on interface em1, disabling advertisements
Nov 16 19:42:45	radvd	44764	resuming normal operation
Nov 16 19:42:50	radvd	44764	attempting to reread config file
Nov 16 19:42:50	radvd	44764	no auto-selected prefix on interface em1, disabling advertisements
Nov 16 19:42:50	radvd	44764	resuming normal operation
Nov 16 19:42:51	radvd	44764	attempting to reread config file
Nov 16 19:42:51	radvd	44764	no auto-selected prefix on interface em1, disabling advertisements
Nov 16 19:42:51	radvd	44764	resuming normal operation

      Ik heb het forum (en google) doorlopen en las dit topic: https://forum.pfsense.org/index.php?topic=110043.0 maar helaas…
      De kabels vervangen hielp ook niet. Kan iemand mij in de juiste richting duwen aub?

      Alvast bedankt.

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

        Gebruik je de ipv6 met een reden? (Zelf Telenet hier, mijn modem doet nog geen ipv6 dus helaas geen ervaring die ik daarover kan delen… wel via HE tunnel)

        Indien niet bewust een keuze, zou ik 1st proberen het ding in ipv4 te zetten (IIRC doet de telenet modem dual stack...)
        -> System\Advanced\Networking -> uncheck "Allow IPv6", en "Prefer IPv4 over IPv6"
        -> WAN interface: IPv4 op dhcp, IPv6 none.

        4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
        1x PC Engines APU2C4, 1x PC Engines APU1C4

        1 Reply Last reply Reply Quote 0
        • A
          Arild
          last edited by

          Bedankt voor uw reply. Heb idd ipv6 'uitgezet'. Ik krijg geen meldingen meer in de logs. Het internet gaat ook weer normaal.

          Ondertussen de test-opstelling verhuisd naar zijn vaste plaats  :)

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