You can change the log format in 2.6/22.01 to use RFC 5424 instead: https://docs.netgate.com/pfsense/en/latest/monitoring/logs/settings.html#global-log-settings The filter log format is described here: https://docs.netgate.com/pfsense/en/latest/monitoring/logs/raw-filter-format.html Steve

@johnpoz 'twas not an issue on the HE site. Just had to set 1492 there since I am using PPPoE. and yes, I can and now have forced it on my end. Just more than a little surprised to see a default of 1280?!!! And YES @stephenw10 , I could ping the far end of the tunnel way beyond the MTU. Crazy. And now, I can ping the far end of the tunnel with 8 bytes more than the outside world. Here: Near, Far, GoogleBad, GoogleGood ;) [2.6.0-RELEASE][root@jasmine.ds.org]/root: ping6 -nms 1452 2001:470:39:3c7::2 PING6(1500=40+8+1452 bytes) 2001:470:39:3c7::2 --> 2001:470:39:3c7::2 1460 bytes from 2001:470:39:3c7::2, icmp_seq=0 hlim=64 time=0.180 ms ^C --- 2001:470:39:3c7::2 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.148/0.163/0.180/0.013 ms [2.6.0-RELEASE][root@jasmine.ds.org]/root: ping6 -nms 1452 2001:470:39:3c7::1 PING6(1500=40+8+1452 bytes) 2001:470:39:3c7::2 --> 2001:470:39:3c7::1 1460 bytes from 2001:470:39:3c7::1, icmp_seq=0 hlim=64 time=5.750 ms ^C [2.6.0-RELEASE][root@jasmine.ds.org]/root: ping6 -nms 1452 google.com PING6(1500=40+8+1452 bytes) 2001:470:39:3c7::2 --> 2607:f8b0:400f:802::200e ^C --- google.com ping6 statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss [2.6.0-RELEASE][root@jasmine.ds.org]/root: ping6 -nms 1444 google.com PING6(1492=40+8+1444 bytes) 2001:470:39:3c7::2 --> 2607:f8b0:400f:802::200e 76 bytes from 2607:f8b0:400f:802::200e, icmp_seq=0 hlim=119 time=6.146 ms

@stephenw10 no rotation sorry it's 22.01 which is the last version. It's a Netgate 6100. I'm new with Netgate and pfsense + ; i've always used pfsense CE with amd64/pc archi. Maybe causing by importing CE xml config into Netgate pf plus ?

@stephenw10 I don't know enough about the integration (I haven't had time to read through the code), but I have seen xml-rpc mentioned

Fixed, thanks! https://github.com/pfsense/pfsense/commit/6e4620d2b322735f6514b1ef8a0686e9ef56d17e

@jimp Perfect, very thanks !

pfsense has a 'recipe' for this type of setup. https://docs.netgate.com/pfsense/en/latest/recipes/external-wireless-router.html?highlight=wireless%20router By the way, if you plug Mercury the WAN port into pfsense LAN port, pfsense logs will show the IP address/traffic of only the Mercury. This is because wireless clients are behind Mercury FW/NAT. By using both LAN ports (LAN to LAN port) you bypass the internal Mercury software/apps which at this point is essentially a just switch with WiFi. Hope this helps.

@johnpoz Thank you for the information. Just as you said, it was because they were not enabled.

@pzanga were you ever able to get PPPOE setup in PFSense behind the Arris NVG443G with Frontier? I have been trying for days to get this working with no luck! I even tried a call to support where i was told to basically give up cause they do not support it. I dont want to give up as i still think this is possible i just think im missing something. Any guidance on your setup would be a huge help.

@stephenw10 Removed IP4 preference and confirmed working. Also did a tracert pkg01-atx.netgate.com - 20 hops on IPv6 vs 13 for IPv4 - thought IPv6 routing was supposed be slicker! Tracing route to pkg01-atx.netgate.com [2610:160:11:18::209] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2001:4d48:ad5c:fe10::254 2 9 ms 8 ms 8 ms 2001:4d48:feed:97::138 3 10 ms 10 ms * 2001:4d48:feed:97::1 4 9 ms * 10 ms 2001:4d48:feed:99::a 5 15 ms 15 ms 15 ms 2001:4d48:ace::43 6 15 ms 15 ms 15 ms ams-ix-1.enta.net [2001:7f8:1::a500:8468:1] 7 15 ms 19 ms 22 ms er1.ams1.nl.above.net [2001:7f8:1::a500:6461:1] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 126 ms * 126 ms ae5.cs1.lhr11.uk.eth.zayo.com [2001:438:ffff::407d:1d7e] 12 * * * Request timed out. 13 * * * Request timed out. 14 134 ms 130 ms * 2001:438:ffff::407d:1c9e 15 126 ms 126 ms 126 ms ae8.mpr1.aus1.us.zip.zayo.com [2001:438:ffff::407d:1b1e] 16 123 ms 123 ms 123 ms 2001:438:ffff::407d:20c6 17 124 ms 124 ms 124 ms 2610:160::ffff:4014:e59e 18 123 ms 123 ms 123 ms 2610:160:11:1::6 19 124 ms 123 ms 123 ms 2610:160:11:1000::6 20 124 ms 123 ms 123 ms 2610:160:11:18::209

Thanks to all! I installed the latest version, use DNS Resolver and disable the "DHCP Registration". IPv6 is disabled. I will see if its now better. Thank you!

You could choose not to pass though the hardware and then set the virtual NICs as e1000. Then they will use the em(4) driver and match. Steve

Level 1 is the default. Logging queries can produce a lot of logs of your network is at all busy. It's usually unnecessary. I only set that logging level when trying to diagnose something. Steve

Our own training is now also online and self-paced: https://www.netgate.com/training Steve

No I can't do that here. We have commercial support if you need it. Post screenshots showing how are accessing it and from where. (the source IP address) Steve

You should be able to ping the pfSense WAN interface at 70.70.70.2 from the Win7 VM in the LAN with only the default rules. The only reason you might not be is if the VM has no default route or a bad default route. Or something in the hypervisor is blocking it. You will not be able to ping from the server to anything on the LAN without firewall rules to pass it and a route to reach that subnet. Steve

@fabrizior said in 2.6.0 - Installed Pkgs - Unable to retrieve package information.: ipv4 workaround has now been working reliably https://forum.netgate.com/topic/171035/since-about-1400-hours-i-have-been-unable-to-get-updates-in-dashboard/13

@bingo600 That's it! Thanks.

Okay. Finally solved this for the friend. She had SimpleWall installed and it was blocking everything! I did not know it until I found we couldn't ping websites then investigated further and wallah! Thank you all!