Hi Mate. Thanks for your response. I don't think so , the wan is set up statically and supplied by a data centre. The connection will be coming from another firewall VLAN. When we plugged the older pfsense in with the same config no issues were occurring. Just trying to look through the logs using shell due to the fact they only show a certain time in the GUI. Thanks

Yes. Just like you would with an rfc1918 network. If they routed 1.1.1.0/25 to you: Interface: 1.1.1.1 /25 Usable: 1.1.1.2 - 1.1.1.126 They'd set 1.1.1.1 as the gateway. Or you could configure DHCP to hand out the addresses if you wanted. You could also just use a /26, /27, /28, /29, /30, /31 on the inside interface and use the rest of the space for other purposes.

@stephenkwabena No actual commands. I was using a mouse. If you don't know how to look at a file : @gertjan said in PFsense 2.4.4 FreeRadius Mac Address Authentication Qouta: Have a look at /var/log/radacct/datacounter/daily/ - see the files yourself. That makes under stand things much faster. or what it means, then IMHO : it's not worth looking. You could use the pfSense GUI, or, go for a free program like WinSCP.

If you just want to do DNS bases blacklisting you could take a look at pfBlockerNG.

Die Anzeige der Rufnummer ist von Anbieter zu Anbieter unterschiedlich und wird in der Fritzbox korrigiert, wenn du dort auch Telekom hinterlegst. Bei "anderm Anbieter" passiert das nicht bzw. du mußt das manuell machen. im ip-phone-forum ist da einiges zu finden. Gruß pfadmin

Merci @ccnet pour votre retour. Alors depuis mon espace OVH je vois bien une passerelle mais sur mon VPS, il n'y a aucune passerelle de configurer... 2001:41d0:0305:2100:0000:0000:0000:0001 Effectivement le but de ma démarche et d'obtenir une passerelle afin d'interconnecté mon VPS avec un réseau exterieur.

@thehermit Hardware encryption will probably be a requirement for v 2.5

@jimp Thank you! It worked.

Whatever the proxy is for or is doing is probably messing up DNS resolution for your pfSense. The package management system needs a completely clean DNS resolution to operate properly, namely there can not be any filtering or tampering with SRV records, the pkg package manager uses those all the time for finding suitable mirrors for the packages. Either that or the proxy is doing something to the http(s) downloads of the package catalogs to mess up the update system.

@medikopter said in OpenVPN TLS Fehler: Das klingt ja eigentlich ganz cool und simple, allerdings scheitere ich schon an der Umsetzung eines Failover. Nunja, aber das sind ja auch zwei verschiedene paar Stiefel ;) VPN auf beiden Interfaces zum Laufen zu bringen ist wesentlich leichter, weil du nichts umschalten/routen/sonstwas musst. Daher überhaupt nicht schwer. Also das er das Interface automatisch wechselt wenn eins Down ist. Es genügt doch eine Gateway Gruppe zu machen und die bei den Regeln auf dem LAN einzusetzen?

@andyc Yeah, i want to have access to my ESXi management from work and at home. (only for a while, as I am preparing everything for my VM ect ..) i will make a IP restriction or something like that if it's possible, to allow only my home public IP and the work IP Or i can just do a VPN with my pfSense (i saw come options to do this), i don't know, i'll think about it