@johnpoz I don't think it matter now either, because I changed the mask to 192.168.100.0/24 and Virtual IP to the same and it works. I think the web interface on the Hiltron CODA56 running SW Version 7.3.5.0.1b5 seems like its goes unresponsive. I rebooted the modem and the web interface was back. Seems like they had issue with older code, but pfsense is working as it should.

Nope that's the only location on the firewall It will save up to 30 backup configs. It makes a backup any time you make a config change.

You can restore a backed up config file you have locally in Diag > Backup / Restore.

And what error did it show when you tried to ping? Just timed out? No route? TTL expired? Network down?

If ifconfig shows the NICs as still linked and it has a valid route still then I would expect it to try to send traffic to the gateway. If the virtual NICs just stopped passing traffic then it will fail to ARP for the gateway and show an error related to that. However if it can still ARP for the gateway then that's probably some network config issue.

Nothing that I've seen. You can add a feature request: https://redmine.pfsense.org/

Steve

I found solution for me, I rebooted.... then internat came to my LAN

Try setting the monitoring IP to something external, it will give you better data anyway.

Edit the gateway in System > Routing > Gateways. Try using 8.8.8.8 or 1.1.1.1 etc.

Yeah it would need to support that specifically. Otherwise you could probably run two VMs for example.

Sounds good to me.

For most patches nothing further is required. However some of the recommended patches for 2.7.2 do so I would reboot after applying to be sure. When restarting or rebooting is required it's noted in the patch description.

Check Diag > System Activity or top -HaSP at the command line. What is using the CPU cycles when this happens?

@terryzb said in pfBlockerNG vulnerability?:

Is this a concern?

tl:dr: Nope. 😉

Mmm, I had my device in a lagg when I tested it but I was accessing over it directly not using a VLAN

@dada00 Thanks for asking/posting this. This was exactly my situation as well. I had long forgotten that I had set a particular host as a test VPN server. I was racking my brain trying to figure out where the monitoring was happening.

@jamesonp You rock!

Thanks!

@Fandangos said in Is it possible to have a device from one interface to have an ip on another interface?:

no I set it up manually on the docker container.
So if an IP is not set up by DHCP it will not show up at DHCP leases. Makes sense.

Exactly. You can see the IP in Diagnostic > ARP table, however, after a communication with it for 20 minutes.

If your intention is to use its host name to access it add a host override to your local DNS.

When I'm doing a VLAN here, I have a smart managed switch that will tag the port connecting to PfSense and tag the ports I'm using to connect my devices to it.

No, the VLAN has to be terminated on Unraid and pfSense. If there is a VLAN-capable switch in between both ports need to tag the packets with the proper VLAN tag.

Isn't it possible to create virtual IP and NAT it somehow?

NAT = translate the IP from one L2 subnet into another one.
As I wrote in my very first setence, DLNA requires both, server and client to reside within the same L2.

Nice! Yeah there's a lot of ways to get that to fail! Sounds like you removed them all though. 😉

Sorry for the late reply.

For anyone interested in Minisforum releasing a bios fix for this issue, I'd recommend you email support@minisforum.com and voice your interest in this.

Hopefully they will not state a fix is not possible, but if they do, kindly point them to the following:
https://www.asrockind.com/en-gb/index.php?route=newsblog/faq&faq_id=91

This is a competitor's board with an AMI bios and the same i226-LM chip. I am not a bios expert by any means (it probably is not as simple as this sounds), but that link did seem to get them to consider the possibility.

@stephenw10 Yes.

php shell script probably easiest then.

https://docs.netgate.com/pfsense/en/latest/development/php-shell.html

Well it could be an alias in layer 2 rules perhaps... all the normal firewall and NAT rules would need to resolve a hostname or MAC to an IP dynamically.

Hi

I downloaded version 2.7.2 and reinstalled the system. Now it works.

Thanks