For NAT: Create your own outbound NAT rules and switch to manual mode.

Your limitations are going to be how big your internet pipe is, how you configure the lan side, etc.  I personally would not put 1000 devices on the same segment - because that ends up being a lot of broadcast noise..

There will be a limitation of your state table, etc. If you only have 1 public IP to nat too that could end up being a limiting factor even if you had a 10ge pipe to handle traffic, etc.

But you could have 1000's of clients behind sure..

@johnpoz:

How does your blocking their C&C prevent that?

It doesn't always but it depends on the variant - for example CrytoLocker will stay dormant (and does not encrypt files) if it cannot reach the designated C&C server.

Has that kept it out?  No.  But you now have a hit on your DNSBL which you can use to isolate an infected machine.

@alex1962:

[Mon Jan 22 15:41:06 CET 2018] 'www.cybercrimine.com' is not a issued domain, skip.

Can't use https://crt.sh right now - better check with that site when it comes up again.

@alex1962:

if I analyze the start of pfsense I see a lot of faied pullup errors.
can it be connected?

Don't know what you mean.

@Derelict:

That or I suppose someone is trying to spoof ARP for an interface address. You would need to handle that in your switching gear.

Diagnostics > Packet Capture for ARP on that interface and see what you see.

No. I think this is caused by my own ignorance.  :D

I use lots and lots of local names.. You shouldn't be using .local - states that right in the notes for when setting up your domain under general settings.

Do not use '.local' as the final part of the domain (TLD), The '.local' domain is widely used by mDNS (including Avahi and Apple OS X's Bonjour/Rendezvous/Airprint/Airplay), and some Windows systems and networked devices. These will not network correctly if the router uses '.local'. Alternatives such as '.local.lan' or '.mylocal' are safe.

I would turn off register dhcp… Just have it register reservations.. All devices you want to resolve most likely should have the same IP - so just setup a reservation for them, etc. so they always get the same IP..

@johnpoz:

Yeah you can see for sure that IP is part of the ntp pool.

http://www.pool.ntp.org/scores/95.211.224.12

Yeah…that's my biggest gripe with a lot of the blacklist type of IP lists.  They mix up the good guys and the bad guys sometimes, and it is frequently difficult to get mistakes fixed.

Bill

@pronten2:

Ok i will try i will update you later tnx

Nothing to "try" actually, it's disabled by default, so a user can use the same login ID on multiple devices already.
See image.

multiple.PNG
multiple.PNG_thumb

@triangleman:

@Harvy66:

Probably easier to re-install and restore your config from backup. You backup, right? And using ZFS would probably help prevent this in the future, at the cost of more memory.

I'm all-for preventing this from happening again and will look into ZFS,
but re-installing after a mere power failure seems a little much.

Surely there's a way to use the 'recovery mode' from the CD to run FSCK on the disk right?
I looked into it, FSCK does run, but i don't know how use it for this.

I'm not familiar with UFS. Most modern filesystems don't trash committed data, only data or metadata changes that are in-flight run the risk of corruption. My pfSense box has experienced 3 unexpected power failures in the many years. Never had an issue, but could just be lucky or you could be unlucky or something pathological.

Yep, right before going in and setting it manually because it wasn't working either for some reason.  I'm just gonna restore it to defaults and go through the setup again.

I also tested this with another appliance with nearly no changes to the default configuration, but I get the same result.

If anyone could tell me where i've might made a mistake that would be really appreciated.

Thanks. That seems like a good starting point.

I looked the script /etc/rc.newwanipv6 and it looks like I have two options:

a) Modify the script to call my script as well. But then I might have to change that file after every upgrade of pfsense, I'm assuming.
b) At the end of the script, there is a function to restart packages. Maybe I could package my script, so it will be called from there automatically? Will have to investigate this a bit more…

Well stated Gertjan - but would like to clarify one small part..

Your not limited to the 1 (one) lan side port with vlans..  If you have multiple ports you can use them for multiple lan side networks..  As long as you have a switch you can connect your multiple ports from the router as different networks tagged or untagged.

Router ports or interfaces are very valuable on a router - trying to bridge them to put in the same layer 2 network is waste of time, effort to end up with a more complex setup and less performance..  You might only do such a thing when you want to connect interface types…  Say you had a fiber connection on your router and you wanted this fiber connection to be in the same L2 network and as normal copper ethernet network.

Or if you wanted to split the same L2 network but be able to firewall beside your split ends..

There are for sure uses of bridging interfaces on your router - but unless your doing something that is a bit more complex and requires such a setup... It going to be a much better idea to get just a vlan capable switch when you need more "ports"  leverage your routers interfaces as switch ports via bridging them not a good idea almost ever.

If you need a few ports in the same network and you want them to be on your router box - get say the sg-3100, it has a 4 switch ports that you can use a switch in the same network or break them out as individual vlans, etc.

But you can for sure get a 8 port get switch that is smart and easy to configure for like $30... If you want multiple interfaces on the same network - your way better off getting a switch then trying to bridge your very useful router interfaces.. It would be better to let those interfaces just sit unused for future use then try and leverage them as switch ports.  If your ocd and don't like these router ports left open - then use them in a lagg to your shiny new switch ;)  Be it your using 1 network or multiple vlans.

Hello forum,

I need some help. I am not a networking expert. I am a noob to pfSense.

I have my set up functional as this:

Internet –> Cable Modem --> pfSense (Qotom) --> Dlink Switch (DGS1100 - 8 port easy smart) ---> Ubiquity AC Pro AP.

The way configured now is simple. No Vlans defined. That is the part I need help on.

What I want to accomplish is to have an SSID defined which will always route traffic via openVPN client (PIA). I have not defined the client yet - but I will be doing so once I am able to define vlans.

Should I define Vlans on pfSense and also on Dlink Switch? If yes how do I instruct the Vlan defined on pfsense to use a specific port of the switch?

The dlink Switch is only accessible on its own default IP. Should I connect to it and change it to an static IP of my choice so that I can access the web GUI of the switch?

The Unifi AC Pro AP also has capability to identify the vlan for wireless traffic. So I must probably identify the tag for specific vlans for a particular SSID. Am I right?

Appreciate the time spent on responding to my questions.

Regards

Guru

@jahonix:

As long as both ends of a cable are configured the same way it doesn't matter.
One manufacturer (r+m) made a comparison and found TIA568A to be capable of slightly faster transmission speeds than TIA568B. I cannot find the paper ATM though and can't explain why that should be.

Just found on de.wikipedia that 568A is supposed to be the preferred standard in Europe and 568B is around in the US for historical reasons … oh well.

The only difference between pairs is the twist rate.  Each pair has a different twist rate, to minimize cross talk.  However, with a 10 or 100 Mb cable,the same 2 pairs are used and only the signal direction reversed between A & B.  With Gigabit, all 4 pairs are used.  568B goes back to what eventually became 10baseT, StarLAN.  StarLAN was designed to share an existing 3 pair CAT3 cable with a telephone.  The phone would be on the first pair (blue/white), with the 2nd (orange/white) and 3rd (green/white) used for the LAN.  It also used a 6 position connector, as was common for phones.  This also means that Ethernet was designed to share a cable with phones, but that's not recommended practice now.

https://en.wikipedia.org/wiki/StarLAN

@Grimson:

@kcallis:

This morning, in a moment of inspiration, I thought I would get tor working. So I configured polipo as well as tor and decided that it wasn't working for me. I removed the packages and find that I could no longer access the internet.

Those aren't official packages, so whatever you did there probably messed with the pfSense install itself. Do a fresh install.

I was hoping for a snazzy way to solve this problem, but the tried and true solution always win! I was just burning my USB thumb drive when I saw your response!

K.