Thanks @jimp Adding an "Allowed IP Address" of 239.255.255.250 for SSDP (Roku Discovery, DLNA Media, Sonos, UPnP + More) to the captive portal did the trick. Thanks a bunch I've also added 224.0.0.251 for mDNS / Multicast DNS (Chromecast Discovery + Bonjour + More) Works like a charm now :)

You mean this file /var/db/captiveportalxxxxxxxx.db ? This is SQLite3 file - it says so itself : [image: 1624635152269-e2f234dd-8c71-464e-9d6d-33c449cfd7b0-image.png] As pfSense, you need this to interact with it. Good news ; pfSense has the sqlite3 PHP extension loaded. Friendly warning : the simple fact you had to this (IMHO : simple to find out yourself) means that you should not 'mess' with it. Removing a 'record' in that database is can be done with these button button : [image: 1624635290823-aa81f840-6474-4ec2-9c35-c79fa76a83d4-image.png] The other info stored in it (per record) is : allow_time INTEGER, pipeno INTEGER, ip TEXT, mac TEXT, username TEXT, sessionid TEXT, bpassword TEXT, session_timeout INTEGER, idle_timeout INTEGER, session_terminate_time INTEGER, interim_interval INTEGER, traffic_quota INTEGER, bw_up INTEGER, bw_down INTEGER, authmethod TEXT, context TEXT Changing these values isn't useful, the underlying captive portal "ipfw" firewall rule won't get changed.

i solved this problem thanks.

@thisislivin said in Block MAC Headers from known hacked devices: Pfsense newbie. As we are all learning every day, So I guess we all are. But you can shift from "think you know" to "know you know" just by looking at something like this : https://www.youtube.com/watch?v=XaGXPObx2Gs&list=PLowKtXNTBypH19whXTVoG3oKSuOcw_XeW It starts with a wire, 8 conductors .... easy. By the end, you know what 'networks" are, what and IP address is, and a MAC address.

SupporteATECH asked : [image: 1623317547688-c6dfb0bc-f2f7-4683-badd-17470fa3c326-image.png] Older version had old bugs. This issue, "You are connected" doesn't exist any more. I just tried it myself : This is my captive portal zone name : [image: 1623317635684-bd467ce7-b111-4982-9613-966fde1eadf8-image.png] So this is the SQL3 database file that contains all the users that are connected : [image: 1623317701894-81ecd1fb-4825-4062-bf6b-9871f40f41cc-image.png] This file is wiped and created on restart. If this option is set : [image: 1623317772846-8a7dd18b-32b1-44bd-a6d7-55c145b52dd9-image.png] then the file is not reset. Upon reboot, the file is read, and for all captive portal users that were connected upon reboot - listed in this file, 'ipfw' firewall rules and tables are re created. See the ipfw rules for yourself. It works for me I'm using 2.5.1 CE.

@sanctify said in 1 User Per Voucher Code: @gertjan how do you upload or install this patch on the Pfsense that's these "1 User Per Voucher Code"? That question was valid in 2016, that's 5 years ago. These days, you select : [image: 1623131400246-1a3997c6-e867-4d97-b29f-6a38cc9bd176-image.png]

@free4 ThankU, I will continue working this out. Thx

@guillame I've tested pfSense with a "Nordnet" router and a satellite connection a month ago. Works well, as expected, because what the 'WAN' actually is, A/VDSL RTC, PPPoE, over Wifi or satellite, it doesn't matter.

@abraham11 I save the CSV file on the PC them open it with Excell or LibreOffice in my case. You end-up with a list of voucher numbers in Column A Then I have a second tab with a preformated print and the values of the tickets just feel the preformated print. Ready to print And them use scissor to cut them Simple and easy

nevermind, looks like a vlan issue

My Issue is different than @refugeesonline. We are facing random voucher expiry before remaining time. Almost 2500+ voucher active and few of them having this behavior. vouchers are 7 Days, 15 Days & also 30 Days. Expiry happening randomly with different rolls , one client created 1 Year voucher which I also not recommend and suggested him to use Radius authentication ( PfSense Radius ) for long terms users. We have fresh install of 2.5 stable system. NO RAM DISK, NO HA setup. All installations on SSD 480G. We have no issue with System reboots we did it few times and all is well.

Nice !! I replied yesterday -see above - to a post that dates from ..... not the spammer just above but to Erik_CH and @free4 - messages from 2019...... Woken up by some BS of Veralder who want me to look at some Swedish consultancy site - to find issue https://redmine.pfsense.org/issues/11842 - testing that solution - posting a solution for the solution .... To discover just now that it was actually a spammer ( ? ) that made me contribute to pfSense. Great. I need a drink.

Finally I found out a workaround I have another pfsense box with version 2.4.5 and on that one I was able to generate a short private and public key . So I copy paste them to the 2.5.1 box ... and bingo it works ! Six character long voucher code

@westr said in two logins on same portal page (Voucher + No_Auth): and be sent to a separate VLAN Somewhere on the net, a local LAN or VLAN : where ever you want.

Thank You @gertjan I missed one setting. It's work Now.

@free4 It was working fine without any issues in previous releases Anyway, thanks for the information