I believe I’m having this issue, and have been for some time now. I always wondered why sometimes PPP would drop, and I’d drive out to site only to do a reboot and everything works. Sometimes I’d even have people put on site reboot for me, but it wouldn’t work. Is there any update on this issue? Below log is newest on top, so read in reverse. Feb 21 09:25:12 ppp 98216 [wan] IFACE: Down event Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: LayerDown Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: SendTerminateReq #38 Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: state change Opened --> Closing Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: Close event Feb 21 09:25:08 ppp 98216 [wan] IPCP: LayerDown Feb 21 09:25:08 ppp 98216 [wan] IPCP: SendTerminateReq #76 Feb 21 09:25:08 ppp 98216 [wan] IPCP: state change Opened --> Closing Feb 21 09:25:08 ppp 98216 [wan] IPCP: Close event Feb 21 09:25:08 ppp 98216 [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Feb 21 09:25:08 ppp 98216 [wan_link0] Link: Leave bundle "wan" Feb 21 09:25:08 ppp 98216 [wan_link0] LCP: state change Opened --> Stopping Feb 21 09:25:08 ppp 98216 [wan_link0] LCP: peer not responding to echo requests Feb 21 09:25:08 ppp 98216 [wan_link0] LCP: no reply to 5 echo request(s) Feb 21 09:24:58 ppp 98216 [wan_link0] LCP: no reply to 4 echo request(s) Feb 21 09:24:48 ppp 98216 [wan_link0] LCP: no reply to 3 echo request(s) Feb 21 09:24:38 ppp 98216 [wan_link0] LCP: no reply to 2 echo request(s) Feb 21 09:24:27 ppp 98216 [wan_link0] LCP: no reply to 1 echo request(s

Thanks guys.  I now see the distinction between Port Trunking and Ethernet Trunking.  In a sense one is the inverse of the other? And Derelict, I will give your test suggestion a work out as soon as I can.

@stephenw10 Thank you, I will give that a shot. I appreciate the feedback.

Havia removido o grupo Default (não me lembro o pq), recriei ele, movi pro topo da lista de grupos, salvei, ele APARECE na aba Users, mas, no final dela. Um grupo continua sumido da lista na aba Users, mas outro que tinha movido pra cima, agora obedeceu a ordem na aba Users. Edit: Criei um outro grupo de teste, e quando olhei na aba Users, o grupo que tinha sumido, reapareceu no lugar certo, o grupo Default que tinha acabado se criar, sumiu e no lugar dele mostra o grupo de teste que criei.

@stephenw10 Oh I see. Yep PCAP was on the VM (172.16.0.202). Yep I don't get it. I see what you're saying and all just can't wrap my head around what is going on here.

Thank you marcelloc. My e2guardian package showed a squidguard dependency and installed a squidguard packaged… even though I don't see it in the Services or Firewall menus. Transparent proxy is what I want. I will Internet search how to set it up. Do you have any pointers or references on doing this with e2guardian & squid?

as a home user I am also taking the Official Announcement or send me an email since I have a pfsense + install...either way please let us know asap some of us are disabled veterans- well at least I am and have strict as frick budgets

Frank, thank you very much for your very detailed explanation! I checked it and pins and springs are OK. There are only 2 Pins for the cooler and you can move it so that the springs are become more tention. So it seems that it works as it should work and that there is some lash for the cooler. Temp is about 50° in my supermicro 505 rackmount case without active cooling in a full network rack. I took a better look at the standard shield from the case. and yes, it works if you open every inlay and leave it closed for displayport/hdmi.

@elvisimprsntr Updated 25.07.1 to 1.90.6_1, copied and pasted from @elvisimprsntr's post: pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.90.6_1.pkg (Why it worked this time and not on previous updates: Over the last couple of days, I ran into the "Shared object "libutil.so.10, not found..." error that triggered the version 25.07.1 update issues some of us have been having. After I fixed that error, I decided to go back to the usual update method, and it worked.)

Se ha creado un grupo de Telegram https://t.me/fw_movistar para compartir los avances en el proceso de configuración de un Firewall que sea compatible con la Triple VLAN Movistar

Das ist ein BIOS/Treiber Problem - leider seit ewiger Zeit nicht gefixt… Mir fehl dazu leider der nötige "Background".... Siehe auch: http://www.pcengines.info/forums/?page=t&fid=DF5ACB70-99C4-4C61-AFA6-4C0E0DB05B2A&cachecommand=bypass&pageindex=2 Gruß Thomas

@moscato359: I had the same problem with sch_codelq, but sch_fairq with codel fixed it I have the same problem (500/30 without shaping goes to 250/20 with codel shapers set to 20 for wan and 480 for lan) Tried fairq shaper with the same result. What is sch_codelq and sch_fairq? Is this the same as codelq shaper and fairq shaper in the gui?

Bei mir schon Hast Du die Beta am laufen? [image: 03-03-_2017_19-52-23.png] [image: 03-03-_2017_19-52-23.png_thumb]

@maverick_slo: Hi! snort-2.9.4.6.tbz is June version on the link u posted? Regards, M UPDATE #2 (9:22 AM September 28):  The updated Snort binary for 2.0.3 pfSense installs is now available in the files repository. UPDATED INFO (9:30 PM September 27):   I received a note back from the pfSense guys.  There are some issues with getting the 2.0.3 binary packages rebuilt.  The issues are generic with the Ports tree and not specific to Snort.  It could be later this weekend or even early next week before the 2.0.3 binaries get rebuilt.  If you have a 2.1 install, you are golden because the PBI packages are good to go. If you want the new Snort GUI fixes, then go ahead and reinstall the Snort package now.  Just click the PKG or XML icons.  They both will do the same thing in terms of reinstalling the GUI PHP code.  I will post back later when the new Snort binaries for 2.0.3 pfSense are built and posted. **Original Post follows –- ** Yeah, I think maybe those rebuild overnight.  I will e-mail the Core Team guys and have one of them check it out.  The new binary is not a huge deal, but if you use the SMTP preprocessor and sometimes saw the message about "SMTP:  changing file_depth requires a restart", then the updated binary will fix that (and allow Snort to soft-restart correctly). It won't hurt anything to do a package reinstall by clicking the PKG or XML icon, then later when the new binary is posted you can do the remove and re-install then.  The major bug fixes and new features are all in the GUI code anyway. Bill

Marcelo , bom dia. Meu usuarios no A.D estão criados com numeral da matricula funcional , seria possivel ajustar o script para busca o Display Name p.f ? No squid alterei o LDAP Username DN Attribute e o LDAP Search Filter para "cn" e consigo logar com o Display Name !!!

Still stable with no discernible drops over the last few days. I think the issue is resolved with the driver! Many thanks to those who posted the info!

@stephenw10 I did it this way: used a 25.07.1 VM set update path to 25.11 forced install of pkg with pkg install -f pkg --> pkg 2.3.x installed immediatly afterwards, running of pkg fails because of dependencies lldpd now also fails with the same reasons Yes I know, normally one wouldn't force pkg to install a new version but that's what now has happened to various systems twice. Once in a beta build or when the first RC came out? and once now at the beginning of that thread. Every time we checked, pkg has updated itself to a new 2.x.x version and thus threw errors and lldpd died. So something seems to have triggered a pkg upgrade to a newer version even if 25.07 was selected fixed as install path. Cheers :)