@akuma1x
simply because you don't want to keep in memory what customers is using what addresses. It's a bit difficult when you get up to 400+ customers divided on 4 addresses, it's much easier installing some kind of load balancer dividing all traffic on several setups. but sure enough it would work, if you wouldn't mind a bit of hassle.

The SG-5100 is now at 699.00 vs 799.00: https://store.netgate.com/SG-5100.aspx

You mean this one :

0_1551371049246_4a228a85-d762-41e8-8242-d5669f041918-image.png

Did it showed available packages in the past ?
It never showed any packages ?

Have a look at your :

0_1551371175064_896fba38-6eda-48cd-b35e-5eb9dbbbc225-image.png

You see the "Version information updated at Thu Feb 28 15:45:56 CET 2019" ?
What is your date / time ?

The question that takes care of 75 % of all "can't upgrade/update/install packages" cases : you broke the DNS, so pfSense itself can't reach out to the Internet anymore.
Repair or undo your DNS settings - go back to the "always works" mode : the one that was present by default.

If not, you are lined up for the conquest : "Asking a question without any useful information" 👍

It's true and easiest disabling the DNS for DHCP clients.

Thanks for all.

After contact with microsoft helpdesk I found the solution for me.
For future reference: I had to turn on mss clamping and set it to 1350. This is also in the advanced IPSec settings

Maybe this settings was defaulted after an update? I wasn't the one who configured it in the first place, so I wouldn't know for sure.

I made sure to match my settings to this document https://docs.microsoft.com/nl-nl/azure/vpn-gateway/vpn-gateway-about-vpn-devices

@stephenw10 Thanks for the reply, I had this disabled already, but the pointer was appreciated

I am having this issue as well, looks like there is a bug open: https://redmine.pfsense.org/issues/8987

@kennethw said in Pfsense 1: 1 to the outside with all_ports open.:

I have entered externally with all ports open via a rule ip.

What does that mean in English?

Have you gone through the port-forward troubleshooting guide?

https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

Post some screencaps of your config if you want someone to help you.

@dayve said in No internet this morning.:

Can I install Munin on 2.4.4-RELEASE-p2

That's a good question that I can't answer.
I realized that I'm upgrading pfSense ever since .... somewhere in 2015, when I installed munin as a FreeBSD package, not a pfSense package - on pfSense.
Among others, I used https://forum.netgate.com/topic/104705/munin-node-package-for-2-3 and some other posts on this forum (use the Serach function) to install and setup a munin slave on my pfSense. It works ever since.
FreeBSD package maintenance changed somewhat but I'm pretty sure the concept is still valid.

I see, that's too bad. Since I am fresh out of unused, identically-configured servers - I guess I'll continue my search. :) Thanks for the info and for updating the website, that will help others.

I've been here for 5+ years and I've never heard of squish until today.

Maybe start by showing what you did to install squish, what happened when you tried to run it, and any errors in the system log, squid's log etc.

@sugaredaxe said in Can't login to web configurator or ping the LAN ip:

says that the lan port doesn't have internet access.

Maybe you have a problem with dns? Windows determines if it has internet access via a dns query.

Post the output of ipconfig all on your box your plugging into pfsense.. Did it get an IP from pfsense dhcp server.

And again your LAN should NO gateway setup on it.

You don't My point is you can listen on lan or lan and opt or wan only, etc. etc. If you don't pick an interface it "listens" on all interfaces - but listening has zero to do with doing query from..

It would use the interface connected to that network if local, or if network where the ntp server is is not local then it would use its wan or normal default route interface.. If you had say a vpn service pulling all your default routes setup, etc.

Yeah you can't have two interfaces in the same subnet like that.

You don't need two interfaces though you can just add two gateways on the one interface.

That's a bit ugly though it would be better to use different internal subnets on each ADSL router and connect them separately.

Or even better to set the ADSL routers in bridge mode and pass public IPs to each WAN interface on pfSense directly.

Steve

@vronp said in very strange problem:

@kom said in very strange problem:

That log doesn't look very good. High latency and packet loss.

What type of NICs are you using?

As stated, this is an SG-3100, from Netgate. So, I believe they are Intel.

The concern I have is not this "event", but the ongoing result after the packet loss and latency appear to have returned to normal levels.

I think the next time this happens, after I do what you suggest regarding ping tests, I will disconnect/reconnect the coax cable from the modem and leave the ethernet cable to the pfsense box alone.

This appears to be resolved and was apparently due to a faulty modem (Netgear CM600).

You aren't being rude, you are withholding required information, which is only hurting yourself. Before we can tell you where to get the correct version of the library, you need to answer the questions I asked. Not because we're being nosy, but because without knowing that, you could install the wrong one and cause harm to your firewall (at worst) or have a broken application (at best).

For example: pfSense 2.4.4-p2 is based on FreeBSD 11.2. Your application and the library you are seeing must also be compiled for FreeBSD 11.2. If your application is compiled against FreeBSD 12, it's likely to fail.

If you don't want to answer any questions, then the solution is: Get it from FreeBSD. If you need more guidance than that, you need to cooperate, or this thread is useless.

@davey_bones said in Errors trying to install or uninstall packages:

looks like im missing /usr/ all together.

A small hope : reboot to single user mode, and be friends with fsck a while.
Your system is in a real bad shape.
Put on your todo list : Get a copy of your config.xml file.

I am glad that you edited and added to your post I was starting to think your name should be salty johnpoz :).

I am surprised you have never seen this before. As I stated in my post this is typical of every consumer grade device that I have ever owned and configured, and all the ISP devices that I have ever used for ADSL/Cable/ and now Fiber. There have been a bunch since 1998 until now.

I did state the results from the different settings above in my post. I just posted the medium settings. I was wondering why I would need 53 open (not hosting anything) and the ICMP as well, but I am no expert.

Yes when I select the different settings nat only, low, medium, high, it changes the allowable settings and checked boxes as referenced above.

Thanks for everyone's help. I will keep reading and changing configurations until I feel confident that I can put my test pfSense box into full time operation, with vlans, dhcp, firewall, vpn, etc.

As a take away I am glad that from this discussion it seems confirmed that the default configuration of the pfSense firewall is better than my ISP box on it's high.

Thanks!

Snorf

You probably didn't account for the larger subnet in your firewall rules, outbound NAT rules, IPsec P2s, and other places. You probably need to add more rules or adjust subnet masks to match what you changed.