Both are forms of NAT, translating IP addresses/ports. pfSense just uses the term port forwarding for inbound. Steve

@johnpoz said in Unknown servers on VLAN: @lewis yeah arp scanning is very fast, and most anything is going to answer an arp, even if firewall blocking all protocols and ping, etc. Only problem with that sort of scan is you have to be on the same L2.. But for what your looking for its prob more in line with what your looking to do.. Yes, basically just wanting to make sure I have my own relatively secure LAN (VLAN) network. I'll do it again once everything is up.

@stephenw10 Ahh, I see, good to know, thanks!

@zzkazu said in Helium Miner - Port Forwarding Issue: outlined by "Lawrence Systems" on you tube He says to block the whole planet - normally they put out pretty good info.. I would be disappointed if they said to setup what you had to be honest..

Now it seems back online. thank you Max

@maliaga See if this thread helps.

There is no way to submit them automatically anymore. They could potentially contain sensitive information, so it's best not to post them without reviewing the content. The textdump.tar files are the ones with the useful information. You can expand them with 7-zip or similar though you may have to rename them first (for example, rename textdump.tar.0 to textdump0.tar), and the most important files inside each are ddb.txt and msgbuf.txt. ddb.txt contains the panic backtrace which may point toward a specific cause, while msgbuf.txt contains the kernel message buffer which may have additional clues if the backtrace alone isn't sufficient. You can post the tar files here on the forum, or just the txt files, but review the content first to make sure you aren't posting anything identifiable that you aren't comfortable sharing with the world. For example in your screenshot it has your hostname.

Sorry, I typo'd that. I meant that not a load balancing group! Each WAN in a different tier like that creates a failover group. Steve

@stephenw10 Thank you for your insight. In our case that was the only modification to the configuration after noticing the issue and it resolved it. Hopefuly others will able to try should the encounter the issue.

@stephenw10 Great tip, thanks!! It was set there to 150000000. Deleted, saved, now got the expected 500 in pfSense.conf. cat /var/etc/newsyslog.conf.d/pfSense.conf | egrep filter /var/log/filter.log root:wheel 600 7 500 * C

That's already the case. If you try you see: The following input errors were detected: This LAGG interface cannot be deleted because it is still being used. Steve

Relayd was deprecated in 21.02/2.5. There is a thread detailing an effort to bring it back as a package: https://forum.netgate.com/topic/154871/reestablish-relayd/ You might also try Squid reverse proxy which has a lot less features than HAProxy. Steve

That's a smart move!

I think so too. However, I wanted to follow a tip first and reinstall the software. However, I now also no longer have access to the console. Everything does not sound so good. If there is something interesting to report, I'll let you know. Otherwise, thank you for your time.

@jimp OK, thanks for your prompt response. I applied the patch and can confirm that can't reproduce the issue any more, even after enabling bogon networks block. Thanks for the tip!

I have been running the cron update every other saturday at 1am and yet to have a problem.

Thanks stephenw10 for pointing out typo on subnets. Subnet .1 on pfsense & AP WAN side. Subnet .9 on AP LAN side. I cannot edit the previous post to correct.

@tristargod BSD was created based on the original AT&T UNIX. However, it soon diverged to become independent. There was even a lawsuit over that. Linux was developed completely separate, with Linux Torvalds wanting to create a Unix like OS, after finding MINIX inadequate. Then we had SCO Unix/Caldera claiming ownership over Linux based on very tenuous claims. One was through IBM, which created JFS for OS/2 and then ported it to AIX, which was then claimed to be a derivative work of UNIX, even though it was originally developed for OS/2. That's the sort of nonsense SCO/Caldera was using to justify their claims. There's lots more. BTW, this history was covered extensively on Groklaw.

@stephenw10 Problem fixed. Backups now visible again. thanks Steve

@shinobi said in PHP ERROR: Type 1 - reoccurring alert: I have seen this alert & cleared it a few times. It seemed to pop up right around the Log4j debut.. so any log related error is causing me to 2nd glance it. Does this look like a legit "not enough memory" message, or maybe a buffer overrun.. ? PHP errors PHP ERROR: Type: 1, File: /usr/local/www/suricata/suricata_logs_browser.php, Line: 54, Message: Allowed memory size of 536870912 bytes exhausted (tried to allocate 6336420904 bytes) @ 2022-03-12 01:20:08 Your log file has grown too large to view using the PHP viewer applet. That code works by loading the entire log into RAM and then displaying it to the browser as one string. The PHP process in pfSense has a limited amount of RAM allocated for it, so if the log file is too big, that limited RAM is exhausted when trying to load the log. The solution, as @SteveITS said, is to turn on the log rotation options and set a much smaller log size for alerts.