So you want to use the same cert on all your devices, ie wildcard cert?  And you want to use it with a single label domain .home as well?  Yeah that is broken setup just thinking about it.  What is using the cert?  Most browsers will not like that, many browsers will want for a wildcard a valid tld so .home would be out, other would want 2 labels home.tld, etc. I don't think there is anything in the rfc that says you can not have a single label wildcard but seems like a really really bad idea… To me those are not host names, those are domain names you always have host.domain.tld so you are trying to create a wildcard cert for different domains the way I look at it. Your certs are FREE, and take like 3 seconds to produce, why would you want a wildcard in this setup in the firstplace?

@yrebrac - your patch to set the NAS-IP to a different value, was that merged into the project?  I am running into a problem where the RADIUS server I am using will not accept 0.0.0.0 as the NAS-IP.  I am running the latest 2.3.1 release.  Can you post the diff? Patch works  :) :) :) v2.2.6

Great, glad to hear you like my changes Chris! :) I did start doing some of the php coding myself, I was able to get this done so far, IPv4 address append configuration type add CIDR to subnet mask change ISP DNS Servers to just DNS Server(s), very simple change lmao. display NIC name Here's what it looks like, and no I didn't edit the HTML this time ;) [image: 07_06_16_22_50_59.png] What I'll probably not be able to figure out is how to parse the dhclient.leases file to pull the DHCP lease info, but you never know I could figure it out. I'm new to PHP, but I've had my foot in the water a few times with it so it's nothing terribly new to me.

I didn't make it in the last release, it is (will be) in 2.3.2 though.

That's up to the client, but you can disable the port 80 redirect on pfSense, which would also stop that from being a problem. Though you'll have to remember to go to https://x.x.x.x manually and not rely on the redirect in that case. The option is under System > Advanced on the Admin Access tab

The traffic graphs are in the process of being redone with nvd3 so that the styling can stay within the stylesheets. Nice work, but this won't end up in the main repo because of the way it was (read:  had to be) implemented.

Glad that was it. It could really use a better message in that case, rather than looking like it was successful and leaving you wondering what the deal is.

worked like a charms!! thank you!!

I made some tests and I encoutered very strange issue : Connecting from Lan or Wan on a Linux platform it's not working with Chrome but it's working with Firefox

Adding a second nav tier is a discussion worthy of another thread, although the implementation could be somewhat involved. It would still be nice to have the thought exercise of what a potential 2-tier nav could like like (without confusing existing users). edit: Another option is to see if there are any pages that can logically be combined into a new page that page has them as tabs instead. For example, moving Status > DHCPv6 Leases into Status > DHCP Leases and creating v4 and v6 tabs (I have not idea how hard or what implications that might have)

Thanks luckman, clearing the cache solved the problem

Yes, clearing the cache made it working again… Poor of me. I mark the thread as solved.

@Tracktor: try remount the root partition as read-write mount -u / and role back… I just read your reply. I end up installing a new one and restoring latest backup. I'll take note of your suggestion, thanks! kind regards,

Linux Mint 17.1.  I just ran an update and it did update to 46 now (I still can't believe how fast they're pushing entire new versions now, 46 lol.. just crazy).  I don't run it every single day, it gets a little tedious, so I do it whenever I don't have much going on and can reboot. (some updates want to reboot).

bug report created: https://redmine.pfsense.org/issues/6378

I see that it kind of works, but it still creates a lot of double typing. When you create alias of any type, you hide the original value - like IP in my case (but same goes for ports!). So if you see a log entry of a certain IP and wonder where/what host it is, you can't just hoover over the alias-group to quickly isolate/find the host. Alias is often a good way to help find Host Alias->IP, but the interface ignores the other way, IP->Host alias. The hoover should contain the alias value as well, like IP, port or whatever the original value is. A work-around is to enter the IP in the alias, but this creates a possible difference in real value vs textual description and a lot of extra work/confusion. Hope this is fixed in later versions. Another usefull feature developers could implement, is the number of referenced IP, hosts etc. in the fw rules, from Aliases. This is how Fortigate does it (if an alias is used three times, it has a link with number 3 that leads to fw-rules).

Is this fixed or still present? Is it just when using NAT it occours or is it for all rules?