Categories

• TNSR

  Discussions about TNSR

  TNSR Announcements TNSR Feedback Problems Installing or Upgrading TNSR Software
  401
  Topics
  1.4k
  Posts

  F

  Neat! Sounds like a useful update for TNSR users. Is there anything specific you'd like to know about the new features?

• pfSense® Software

  Discussions about pfSense Software, click a category below

  Messages from the pfSense Team General pfSense Questions Problems Installing or Upgrading pfSense Software Firewalling NAT HA/CARP/VIPs L2/Switching/VLANs Routing and Multi WAN Traffic Shaping DHCP and DNS IPv6 IPsec OpenVPN Captive Portal webGUI Wireless SNMP Documentation Development Gaming Virtualization Hardware Bounties Retired
  116.4k
  Topics
  729.3k
  Posts

  T

  Yes, the bug ticket is the linked one.

  I took packet captures while the issue was happening as well as after, when I just stopped the SIP traffic for a minute and started again. Probably that pause cleared the state in pfSense, because after that the local SIP client continued sending packets with exactly the same source / destination IP and port (black tcpdump screenshot in the ticket) and has been still working fine.

  I didn’t check the states but I am waiting for this to happen again and I will check the state as well

  pfSense+ version is: 24.03

• pfSense Packages

  Discussions about pfSense software packages

  Cache/Proxy IDS/IPS Traffic Monitoring pfBlockerNG UPS Tools ACME FRR Tailscale WireGuard
  19.5k
  Topics
  122.9k
  Posts

  R

  I seem to have a peculiar issue. My first peer connection comes up with no issue. I reboot the router and the connection comes back with no issues. No routing problems, no issues.

  My second peer on the other hand is giving me some issues. On the initial connection it works fine. If the tunnel dies due to inactivity and I resume connectivity it's fine. No routing problems, no issues.

  I only seem to have issues when I reboot this peer. Once it's rebooted and I generate interesting traffic it takes about 6 to 7 minutes before the handshake is completed. I perform a packet capture on the WAN interface of my PFSense router and I can see the peer trying to initiate the connection but I don't see responses back from the PFSense router. Until about 6 of 7 minutes. But if I restart the WireGuard service on the PFSense router the connection comes up immediately. Once it's up no issues.

  PFSense Hub Router
  Using PFSense Ver: 23.09.1
  Using WireGuard Ver: 0.2.1

  Peer 1
  OpenWRT Version 23.05, WireGuard kmod Version 5.15.134-1

  Peer 2
  OpenWRT Version 23.05.3, WireGuard kmod Version 5.15.150-1

• pfSense International Support

  Discuss pfSense in other languages

  Chinese Deutsch Español Français Indonesian Italiano Russian Nederlands Norwegian Portuguese Polish Romanian Swedish Turkish
  42.2k
  Topics
  264.9k
  Posts

  P

  Hallo zusammen,

  unser WLAN in unserer Schule lief mit unserer pfsense lange Zeit sehr stabil. Dann kam ein Unwetter und seitdem läuft alles leider sehr schlecht. Die Telekom hat die Leitung mehrmals durchgemessen und nichts feststellen können.

  Getauscht habe ich bereits die Netzwerkkarten und alle Kabel. Ein neues Modem habe ich heute bestellt. Vielleicht kann mir aber jemand von euch weiterhelfen und mir sagen, ob ich evtl. auf dem Holzweg bin und die Hardware gar nicht das Problem ist.

  Auffällig: Am Anfang des Schultages gegen 08:00 treten die ersten Fehlermeldungen auf und nachmittags um 15:40 (5 Minuten vor Ende des Schultages) kommt die letzte Fehlermeldung rein - jeder Tag ist gleich.

  Hier mal die letzten Logs (die sich dann nur noch wiederholen):

  Danke und viele Grüße!

  Jun 6 15:40:07 xinetd 33765 Reconfigured: new=0 old=11 dropped=0 (services)
  Jun 6 15:40:07 xinetd 33765 readjusting service 19009-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19008-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19007-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19006-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19005-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19004-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19003-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19002-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19001-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 19000-tcp
  Jun 6 15:40:07 xinetd 33765 readjusting service 6969-udp
  Jun 6 15:40:07 xinetd 33765 Swapping defaults
  Jun 6 15:40:07 xinetd 33765 Starting reconfiguration
  Jun 6 15:40:07 php-fpm 97377 /rc.dyndns.update: phpDynDNS (domain.dyndns.biz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
  Jun 6 15:40:06 php-fpm 98200 1.1.1.2|84.154.69.160|WAN_PPPOE|26.63ms|7.977ms|16%|online|loss
  Jun 6 15:40:06 php-fpm 98200 /rc.filter_configure_sync: MONITOR: WAN_PPPOE is available now, adding to routing group zusammen
  Jun 6 15:40:05 check_reload_status 413 Reloading filter
  Jun 6 15:40:05 check_reload_status 413 Restarting OpenVPN tunnels/interfaces
  Jun 6 15:40:05 check_reload_status 413 Restarting IPsec tunnels
  Jun 6 15:40:05 check_reload_status 413 updating dyndns WAN_PPPOE
  Jun 6 15:40:05 rc.gateway_alarm 61778 >>> Gateway alarm: WAN_PPPOE (Addr:1.1.1.2 Alarm:0 RTT:26.786ms RTTsd:7.915ms Loss:16%)
  Jun 6 15:38:00 sshguard 3702 Now monitoring attacks.
  Jun 6 15:38:00 sshguard 49184 Exiting on signal.
  Jun 6 15:36:00 sshguard 49184 Now monitoring attacks.
  Jun 6 15:36:00 sshguard 91259 Exiting on signal.
  Jun 6 15:34:00 sshguard 91259 Now monitoring attacks.
  Jun 6 15:34:00 sshguard 35102 Exiting on signal.
  Jun 6 15:33:50 xinetd 33765 Reconfigured: new=0 old=11 dropped=0 (services)
  Jun 6 15:33:50 xinetd 33765 readjusting service 19009-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19008-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19007-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19006-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19005-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19004-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19003-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19002-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19001-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19000-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 6969-udp
  Jun 6 15:33:50 xinetd 33765 Swapping defaults
  Jun 6 15:33:50 xinetd 33765 Starting reconfiguration
  Jun 6 15:33:50 php-fpm 11843 /rc.dyndns.update: phpDynDNS (domain.dyndns.biz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
  Jun 6 15:33:50 xinetd 33765 Reconfigured: new=0 old=11 dropped=0 (services)
  Jun 6 15:33:50 xinetd 33765 readjusting service 19009-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19008-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19007-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19006-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19005-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19004-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19003-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19002-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19001-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 19000-tcp
  Jun 6 15:33:50 xinetd 33765 readjusting service 6969-udp
  Jun 6 15:33:50 xinetd 33765 Swapping defaults
  Jun 6 15:33:50 xinetd 33765 Starting reconfiguration
  Jun 6 15:33:49 php-fpm 383 1.1.1.2|84.154.69.160|WAN_PPPOE|24.281ms|8.83ms|28%|down|highloss
  Jun 6 15:33:49 php-fpm 383 /rc.filter_configure_sync: MONITOR: WAN_PPPOE has packet loss, omitting from routing group zusammen
  Jun 6 15:33:48 check_reload_status 413 Reloading filter
  Jun 6 15:33:48 check_reload_status 413 Restarting OpenVPN tunnels/interfaces
  Jun 6 15:33:48 check_reload_status 413 Restarting IPsec tunnels
  Jun 6 15:33:48 check_reload_status 413 updating dyndns WAN_PPPOE
  Jun 6 15:33:48 rc.gateway_alarm 51432 >>> Gateway alarm: WAN_PPPOE (Addr:1.1.1.2 Alarm:1 RTT:24.737ms RTTsd:9.392ms Loss:27%)
  Jun 6 15:33:48 check_reload_status 413 Reloading filter
  Jun 6 15:33:47 php-fpm 97377 /rc.start_packages: [squid] Starting a proxy monitor script
  Jun 6 15:33:46 php-fpm 97377 /rc.start_packages: [squid] Reloading for configuration sync...
  Jun 6 15:33:46 xinetd 33765 Reconfigured: new=0 old=11 dropped=0 (services)
  Jun 6 15:33:46 xinetd 33765 readjusting service 19009-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19008-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19007-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19006-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19005-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19004-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19003-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19002-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19001-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 19000-tcp
  Jun 6 15:33:46 xinetd 33765 readjusting service 6969-udp
  Jun 6 15:33:46 xinetd 33765 Swapping defaults
  Jun 6 15:33:46 xinetd 33765 Starting reconfiguration
  Jun 6 15:33:45 php-fpm 97377 /rc.start_packages: [squid] Stopping any running proxy monitors
  Jun 6 15:33:45 php-fpm 97377 /rc.start_packages: [squid] Removing freshclam cronjob.
  Jun 6 15:33:45 php-fpm 97377 /rc.start_packages: [squid] Antivirus features disabled.
  Jun 6 15:33:45 php-fpm 97377 /rc.start_packages: [squid] Adding cronjobs ...
  Jun 6 15:33:45 php-fpm 97377 /rc.start_packages: [squid] - squid_resync function call pr:1 bp: rpc:no
  Jun 6 15:33:45 php-fpm 97377 /rc.start_packages: Restarting/Starting all packages.
  Jun 6 15:33:44 check_reload_status 413 Reloading filter
  Jun 6 15:33:44 check_reload_status 413 Starting packages
  Jun 6 15:33:44 php-fpm 835 /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 84.154.75.254 -> 84.154.69.160 - Restarting packages.
  Jun 6 15:33:42 php-fpm 835 /rc.newwanip: Creating rrd update script
  Jun 6 15:33:42 php-fpm 835 /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
  Jun 6 15:33:41 php-fpm 835 /rc.newwanip: phpDynDNS (domain.dyndns.biz): (Success) IP Address Changed Successfully! (84.154.69.160)
  Jun 6 15:33:41 php-fpm 835 /rc.newwanip: phpDynDNS: updating cache file /conf/dyndns_wandyndns'domain.dyndns.biz'0.cache: 84.154.69.160
  Jun 6 15:33:38 php-fpm 835 1.1.1.2|84.154.69.160|WAN_PPPOE|19.676ms|0.003ms|0.0%|online|none
  Jun 6 15:33:38 php-fpm 835 /rc.newwanip: MONITOR: WAN_PPPOE is available now, adding to routing group zusammen
  Jun 6 15:33:38 php-fpm 835 /rc.newwanip: IP Address has changed, killing states on former IP Address 84.154.75.254.
  Jun 6 15:33:38 php-fpm 835 /rc.newwanip: Default gateway setting Interface WAN_PPPOE Gateway as default.
  Jun 6 15:33:38 php-fpm 835 /rc.newwanip: Removing static route for monitor 1.1.1.2 and adding a new route through 62.155.244.191
  Jun 6 15:33:38 xinetd 33765 Reconfigured: new=0 old=11 dropped=0 (services)
  Jun 6 15:33:38 xinetd 33765 readjusting service 19009-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19008-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19007-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19006-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19005-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19004-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19003-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19002-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19001-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 19000-tcp
  Jun 6 15:33:38 xinetd 33765 readjusting service 6969-udp
  Jun 6 15:33:38 xinetd 33765 Swapping defaults
  Jun 6 15:33:38 xinetd 33765 Starting reconfiguration
  Jun 6 15:33:37 php-fpm 835 1.1.1.2|84.154.75.254|WAN_PPPOE|24.75ms|5.877ms|34%|down|highloss
  Jun 6 15:33:37 php-fpm 835 /rc.newwanip: MONITOR: WAN_PPPOE has packet loss, omitting from routing group zusammen
  Jun 6 15:33:37 php-fpm 835 /rc.newwanip: rc.newwanip: on (IP address: 84.154.69.160) (interface: WAN[wan]) (real interface: pppoe6).
  Jun 6 15:33:37 php-fpm 835 /rc.newwanip: rc.newwanip: Info: starting on pppoe6.
  Jun 6 15:33:36 ppp 9098 [wan] IFACE: Add description "WAN"
  Jun 6 15:33:36 ppp 9098 [wan] IFACE: Rename interface ng0 to pppoe6
  Jun 6 15:33:36 ppp 9098 [wan] IFACE: Up event
  Jun 6 15:33:36 check_reload_status 413 rc.newwanip starting pppoe6
  Jun 6 15:33:35 check_reload_status 413 Rewriting resolv.conf
  Jun 6 15:33:35 ppp 9098 [wan] 84.154.69.160 -> 62.155.244.191
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: LayerUp
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: state change Ack-Sent --> Opened
  Jun 6 15:33:35 ppp 9098 [wan] SECDNS 217.237.148.70
  Jun 6 15:33:35 ppp 9098 [wan] PRIDNS 217.237.151.205
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 84.154.69.160
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: rec'd Configure Ack #63 (Ack-Sent)
  Jun 6 15:33:35 ppp 9098 [wan] SECDNS 217.237.148.70
  Jun 6 15:33:35 ppp 9098 [wan] PRIDNS 217.237.151.205
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 84.154.69.160
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: SendConfigReq #63
  Jun 6 15:33:35 ppp 9098 [wan] SECDNS 217.237.148.70
  Jun 6 15:33:35 ppp 9098 [wan] PRIDNS 217.237.151.205
  Jun 6 15:33:35 ppp 9098 [wan] 84.154.69.160 is OK
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 84.154.69.160
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: rec'd Configure Nak #62 (Ack-Sent)
  Jun 6 15:33:35 ppp 9098 [wan] SECDNS 0.0.0.0
  Jun 6 15:33:35 ppp 9098 [wan] PRIDNS 0.0.0.0
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 0.0.0.0
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: SendConfigReq #62
  Jun 6 15:33:35 ppp 9098 [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: rec'd Configure Reject #61 (Ack-Sent)
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: state change Req-Sent --> Ack-Sent
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 62.155.244.191
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: SendConfigAck #207
  Jun 6 15:33:35 ppp 9098 [wan] 62.155.244.191 is OK
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 62.155.244.191
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: rec'd Configure Request #207 (Req-Sent)
  Jun 6 15:33:35 ppp 9098 [wan] SECDNS 0.0.0.0
  Jun 6 15:33:35 ppp 9098 [wan] PRIDNS 0.0.0.0
  Jun 6 15:33:35 ppp 9098 [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
  Jun 6 15:33:35 ppp 9098 [wan] IPADDR 0.0.0.0
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: SendConfigReq #61
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: state change Starting --> Req-Sent
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: Up event
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: LayerStart
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: state change Initial --> Starting
  Jun 6 15:33:35 ppp 9098 [wan] IPCP: Open event
  Jun 6 15:33:35 ppp 9098 [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
  Jun 6 15:33:35 ppp 9098 [wan_link0] Link: Join bundle "wan"
  Jun 6 15:33:35 ppp 9098 [wan_link0] Link: Matched action 'bundle "wan" ""'
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: authorization successful
  Jun 6 15:33:35 ppp 9098 [wan_link0] MESG: SRU=30120#SRD=192134#
  Jun 6 15:33:35 ppp 9098 [wan_link0] PAP: rec'd ACK #1 len: 26
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: LayerUp
  Jun 6 15:33:35 ppp 9098 [wan_link0] PAP: sending REQUEST #1 len: 55
  Jun 6 15:33:35 ppp 9098 [wan_link0] PAP: using authname "002977604849551124542420#0001@t-online.de"
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: auth: peer wants PAP, I want nothing
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: state change Ack-Sent --> Opened
  Jun 6 15:33:35 ppp 9098 [wan_link0] MAGICNUM 0xe31ca250
  Jun 6 15:33:35 ppp 9098 [wan_link0] MRU 1492
  Jun 6 15:33:35 ppp 9098 [wan_link0] PROTOCOMP
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: rec'd Configure Ack #36 (Ack-Sent)
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: state change Req-Sent --> Ack-Sent
  Jun 6 15:33:35 ppp 9098 [wan_link0] MAGICNUM 0x3dcaf712
  Jun 6 15:33:35 ppp 9098 [wan_link0] AUTHPROTO PAP
  Jun 6 15:33:35 ppp 9098 [wan_link0] MRU 1492
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: SendConfigAck #194
  Jun 6 15:33:35 ppp 9098 [wan_link0] MAGICNUM 0x3dcaf712
  Jun 6 15:33:35 ppp 9098 [wan_link0] AUTHPROTO PAP
  Jun 6 15:33:35 ppp 9098 [wan_link0] MRU 1492
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: rec'd Configure Request #194 (Req-Sent)
  Jun 6 15:33:35 ppp 9098 [wan_link0] MAGICNUM 0xe31ca250
  Jun 6 15:33:35 ppp 9098 [wan_link0] MRU 1492
  Jun 6 15:33:35 ppp 9098 [wan_link0] PROTOCOMP
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: SendConfigReq #36
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: state change Starting --> Req-Sent
  Jun 6 15:33:35 ppp 9098 [wan_link0] LCP: Up event
  Jun 6 15:33:35 ppp 9098 [wan_link0] Link: UP event
  Jun 6 15:33:35 ppp 9098 [wan_link0] PPPoE: connection successful
  Jun 6 15:33:35 ppp 9098 PPPoE: rec'd ACNAME "MONJ02"
  Jun 6 15:33:34 ppp 9098 [wan_link0] PPPoE: Connecting to ''
  Jun 6 15:33:34 ppp 9098 [wan_link0] Link: reconnection attempt 1
  Jun 6 15:33:33 ppp 9098 [wan_link0] Link: reconnection attempt 1 in 1 seconds
  Jun 6 15:33:33 ppp 9098 [wan_link0] LCP: state change Stopping --> Starting
  Jun 6 15:33:33 ppp 9098 [wan_link0] LCP: Down event
  Jun 6 15:33:33 ppp 9098 [wan_link0] Link: DOWN event
  Jun 6 15:33:33 ppp 9098 [wan_link0] PPPoE: connection closed
  Jun 6 15:33:33 ppp 9098 [wan_link0] rec'd proto IP during terminate phase
  Jun 6 15:33:33 ppp 9098 [wan_link0] rec'd proto IP during terminate phase
  Jun 6 15:33:33 ppp 9098 [wan_link0] rec'd proto IP during terminate phase
  Jun 6 15:33:33 ppp 9098 [wan_link0] LCP: LayerDown
  Jun 6 15:33:33 ppp 9098 [wan_link0] LCP: SendTerminateAck #35
  Jun 6 15:33:33 ppp 9098 [wan] Bundle: Last link has gone, no links for bw-manage defined
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: state change Closing --> Initial
  Jun 6 15:33:33 ppp 9098 [wan] Bundle: No NCPs left. Closing links...
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: LayerFinish
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: Down event
  Jun 6 15:33:33 ppp 9098 [wan] IFACE: Set description "WAN"
  Jun 6 15:33:33 ppp 9098 [wan] IFACE: Rename interface pppoe6 to pppoe6
  Jun 6 15:33:33 ppp 9098 [wan] IFACE: Down event
  Jun 6 15:33:33 ppp 9098 [wan] IFACE: Removing IPv4 address from pppoe6 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
  Jun 6 15:33:33 check_reload_status 413 Rewriting resolv.conf
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: LayerDown
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: SendTerminateReq #60
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: state change Opened --> Closing
  Jun 6 15:33:33 ppp 9098 [wan] IPCP: Close event
  Jun 6 15:33:33 ppp 9098 [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
  Jun 6 15:33:33 ppp 9098 [wan_link0] Link: Leave bundle "wan"
  Jun 6 15:33:33 ppp 9098 [wan_link0] LCP: state change Opened --> Stopping
  Jun 6 15:33:33 ppp 9098 [wan_link0] LCP: rec'd Terminate Request #245 (Opened)
  Jun 6 15:31:06 php-fpm 384 1.1.1.2|84.154.75.254|WAN_PPPOE|31.536ms|13.706ms|20%|online|loss
  Jun 6 15:31:06 php-fpm 384 /rc.dyndns.update: MONITOR: WAN_PPPOE is available now, adding to routing group zusammen
  Jun 6 15:31:05 xinetd 33765 Reconfigured: new=0 old=11 dropped=0 (services)

• Official Netgate® Hardware

  Information about hardware available from Netgate

  2.3k
  Topics
  18.6k
  Posts

  S

  Hmm, that's weird. I've seen SFP ports behave oddly across a power cycle, especially with connecting module before vs after boot. But the ix driver was patched to still allow it to attach.

• Netgate Announcements

  Information about hardware available from Netgate

  42
  Topics
  180
  Posts

  J

  @grahamperrin said in pfSense® Software Embraces Change: A Strategic Migration to the Linux Kernel:

  Not this month; I'm reliably informed that frankenSense® and myrrhgration will be officially announced on Christmas eve.

  francoSense already exists. 😀

• Off-Topic & Non-Support Discussion

  Feel free to talk about anything and everything here

  Forum Feedback Community Job Board
  3.3k
  Topics
  18.2k
  Posts

  G

  @johnpoz @stephenw10

  It started about 2 months ago.
  My browser still said to me : this site has IPv6 avaible, I have IPv6 avaible, so let's do it. And then nothing ... so some fallback mechanism to IPv4 was kicking in after "500 milli sec delay" or so.
  It wasn't really disturbing.