Got it ... it's dmesg | grep igb0 [2.5.0-DEVELOPMENT][admin@NollipfSense.nollipfsense.lan]/root: dmesg | grep igb0 igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xa1000000-0xa10fffff,0xa1104000-0xa1107fff at device 0.0 on pci7 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: Using 4 RX queues 4 TX queues igb0: Using MSI-X interrupts with 5 vectors igb0: Ethernet address: a0:36:9f:09:b0:3c igb0: netmap queues/slots: TX 4/1024, RX 4/1024 igb0: link state changed to UP igb0: promiscuous mode enabled igb0: link state changed to DOWN igb0: link state changed to UP igb0: link state changed to DOWN igb0: link state changed to UP igb0: link state changed to DOWN igb0: link state changed to UP igb0: link state changed to DOWN igb0: promiscuous mode disabled igb0: link state changed to UP igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xa1000000-0xa10fffff,0xa1104000-0xa1107fff at device 0.0 on pci7 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: Using 4 RX queues 4 TX queues igb0: Using MSI-X interrupts with 5 vectors igb0: Ethernet address: a0:36:9f:09:b0:3c igb0: netmap queues/slots: TX 4/1024, RX 4/1024 igb0: link state changed to UP igb0: promiscuous mode enabled igb0: link state changed to DOWN igb0: link state changed to UP igb0: link state changed to DOWN igb0: link state changed to UP igb0: link state changed to DOWN igb0: link state changed to UP igb0: promiscuous mode disabled igb0: promiscuous mode enabled igb0: promiscuous mode disabled igb0: link state changed to DOWN igb0: link state changed to UP igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xa1000000-0xa10fffff,0xa1104000-0xa1107fff at device 0.0 on pci7

@zsing82 said in Script not executing... command not found: Debian boxes. BSD is a whole different animal Actually, for the most part Linux and BSD are similar, in that they're both Unix variations. However, there are some differences, but nowhere near the difference between either and the Windows shell commands.

textdump.tar(1).0 might backup my config and reload it on a clean install. still crashing

@fabiolanza I contacted the seller/company that confirmed the chipset was Intel made. I am waiting for them to list more so I can purchase.

Resolved by putting unbound into DNS forward mode, instead of resolver.

@carobell said in DDNS not updating, cert expired: The problem seems to have been solved on my side. Did a "save and force update" this morning with no change, tried again just now and it's updating! Yepp: http://freedns.afraid.org/news/

Because of this: https://docs.netgate.com/pfsense/en/latest/nat/accessing-port-forwards-from-local-networks.html Steve

The J3455 is not powerful CPU but I would expect it to push more then 100Mbps of OpenVPN given a reasonable connection to the server. You have to check top -aSH though to know what's limiting it. Steve

Hi PiBa, I disabled Cookie protection Set "secure" attribure on cookies (only used on "http" frontends) in the backend settings under HSTS / Cookie protection Under Advanced settings for the backend in Backend pass thru, I added this line you suggested http-response replace-header Set-Cookie "^((?:(?!; [Ss]ecure\b).)*)\$" "\1; secure" if { ssl_fc } This appears to be working fine, since the older setting rspirep ^(Set-Cookie:((?!;\ secure).)*)$ \1;\ secure if { ssl_fc } was placed under the backend settings afterall. Thanks

I figured out how to accomplish my goal, and I did not need to create a gateway or static route. LAN is associated with 192.168.92.1 the switch ETH2 port, per the default setup for the XG-7100. Opt3 is assigned to igb3 (Expansion Card)with a static ip of 192.168.93.1 I enabled the DCHP server for Opt3. I added a rule that allows TCP traffic from Opt3 to LAN. I added a rule that allows ICMP traffic from Opt3 to LAN Now I can access the GUI from a machine connected to an ethernet port that is not part of the XG-7100 switch and pfsense response to pings from my PC with 192.168.93.10 to 192.168.92.1.

Doesn't matter which way you do it.. Be it your routed is native or a vlan.. Or if you change this one or add the routed space.

So easy, thanks :D

There is pretty much nothing different in 2.4.5 regarding the installation and configuration, Whether or not it has WAN access or not, etc. In fact, 2.4.4-p3 and 2.4.5 use the same configuration version, 19.1. You can generally use a 2.4.5 configuration on 2.4.4-p3 and vice-versa. Yes, the pfctl issue is a drag. 2.4.5-p1 will be released "soon." (When it's ready) and all indications are that problem has been solved.

@bmffsc said in redirect wan ip requests to lan ip address: reaching through http://212.252.119.3:8092/OurApp/ Horrible setup! Use a fqdn that resolves to this IP.. Now outside users can get to it via http://something.domain.tld:8092/ourapp where that resolves to 212.x.x.x. your public IP. And internally it resolves to 192.168.1.100 or whatever you local IP of that server is. So the same bookmark works be it they outside or inside.