@GregTheHun said in Resetting package settings?: Lawrence Systems Ok I understand Anyway, this is the only usable source.... the Lawrence Systems with the rest just carefully........ with a lot of misleading video or thought process are pumped. otherwise watch the logic of the proxy cache ...: In today's world there are very fast CPUs, plus tons of RAM ISP speeds are rising into the skies So caching the web pages, with a few endpoints is unnecessary ... this can really only be good for hundreds of users when many people visit the same intranet or internet website, for internal enterprise resource planning (CRM, etc.) systems, if the web is based on access, and similar delicacies

I'm quite sure that syslog traffic follows the normal routing rules. If you're telling pfSense to log to 192.168.3.3 , and ie. OPT1 has the IP 192.168.3.1/24 , then the syslog packages will be sent out of OPT1. But all traffic to 192.168.3.3 would go out of OPT1 (best route) , not only syslog trafic /Bingo

@gab-rc14 said in Help!! WAN DHCP is not working trough my ISP router as bridge pfsense: and assign it inside the range of my IP Public (73.124.X.X) when I assigned this I tried to do ping or tracertroute to 8.8.8.8 but nothing responded So you just took an IP, belonging to your ISP, that is probably assigned to a fellow-client, and you tried to use that. ( while doing so the connection of this fellow probably also died ). @gab-rc14 said in Help!! WAN DHCP is not working trough my ISP router as bridge pfsense: Hi, I tried to configure the my ISP Netgear router SW as bridge, but when I tried to set up the interface wan by DHCP I didn't get a correct IP. it took 0.0.0.0 and the default gateway in the range of the 192.168.0.X. It could be anything. First, look at the paper from your ISP that explains how to set up a typical router device as a bridge. Does your connection actually accepts bridging devices ? If so, is standard "DHCP" as described in the RFC used ? Or did your ISP use some "home made protocol" by adding DHCP "options" that the client should sent ? Etc. A know issue us : when the WAN NIC, from a pfSense point of view, comes up, the DHCP-client is fired. But to early, the bridge isn't build yet, and you obtain some RFC19819 IP. This : InterfacesWAN (driver) > DHCP Client Configuration > Options = Advanced Configuration can be used to solve timing issues, or to exclude RFC1919 answers, etc.

Pretty convinced our issues are gone with the new card. Hell we even get better speeds in and out. Thank you to all on this board who help us out.

Btw : the image above isn't acutal any more. 'submission' is phasing out. It's all port 465 now, or smtps. The protocol setting for 'smtps' connections can be set to "Auto" as Outlook 365 will figure it out. Omg who is this guy? This is so wrong on so many levels ...

@stephenw10 Sorry I meant pfSense WAN queries not being displayed in OpenDNS Prosumer. I think this version only works with a roaming client installed on the machine and not properly on the network.. [image: 1599207494288-opendns-prosumer.png]

OK I have done it like this and all work fine. Regards and thanks, Ramsés

Looks like there is support for ET1310: https://www.freebsd.org/cgi/man.cgi?query=et [2.4.5-RELEASE][admin@2220.stevew.lan]/root: kldstat -v | grep pci/et 146 pci/et Never used one myself. Steve

Oh, yeah just use express card then. Almost certainly not restricted in the same way.

Does it come and go, or remain constant? I'm having a problem which sounds similar, but it comes and goes. Specifically, while I have user activity on my network everything looks pretty normal, but after user activity stops, the bandwidth usage on my WAN port increases significantly, while my other (interior) ports remain idle. Once user activity resumes, the excess load continues for a little while, then vanishes. Maybe this is unrelated, but I just thought I'd ask. Here is the thread for mine: https://forum.netgate.com/topic/155591/pfsense-using-unreasonable-amount-of-bandwidth-while-idle/66

@kiokoman said in command line to add new host/net in alias: it will not survive a reboot or a reload if you don't put that inside the config.xml Oops forgot about that, there is a bulk import if you need to add a load of entries. Firewall -> Aliases -> Bulk import You might be able to do something a bit funky like pfBlocker does with URLs, not sure how often they fetch the list. [image: 1599140735236-screenshot-2020-09-03-at-14.44.08.png] [image: 1599140960564-screenshot-2020-09-03-at-14.48.44.png]

@DaddyGo Thanks so much will take any help I can get..sent you a DM :)

I used these two references to create no problems for my FreePBX ... https://www.youtube.com/watch?v=QFk5jX-oeSo https://docs.netgate.com/pfsense/en/latest/nat/configuring-nat-for-a-voip-pbx.html The only difference I made from the above is I used a WAN floating rule.