Firewall Rules Bug in GUI (Single Host or Alias)

AhnHEL · Feb 14, 2013, 11:15 PM

Creating a firewall rule and in Source, check Single Host or Alias. Enter a host IP or Alias.

Finish completing any other necessary settings to Save Rule.

When you return after saving, the Source type shows Network instead of Single Host or Alias as saved.

Can anyone else confirm this in a snapshot after February 13th, 16:49? This was on a box with a new install, starting from scratch.

This isn't happening on my box with a February 5th Snap that has been updated regularly.

jimp · Feb 15, 2013, 1:41 PM

What exactly are you putting in? And into which field?

There was some work done to fix http://redmine.pfsense.org/issues/2451 that is likely related, but I can't seem to reproduce it just yet.

Update to a current snap to make sure you have the latest fix from that ticket, and then if you can still make it happen on a new rule, give the exact input for each field so we can try to reproduce it here too.

johnpoz · Feb 15, 2013, 2:00 PM

I was seeing this issue, but don't see it now - posted about in http://forum.pfsense.org/index.php/topic,58881.0.html

Was told to update snap - did so and problem was gone. Currently running, updated again to see if UPnP problem was fixed per another thread.

2.1-BETA1 (i386)
built on Fri Feb 15 04:06:54 EST 2013
FreeBSD 8.3-RELEASE-p5

Gitsync as of a few minutes ago.. I have lots of rules with pfblocker alias setup as not source, just went into multiple rules and dropbox is correct. Before it was changing to network, but not currently. Using the nervecenter theme btw.

AhnHEL · Feb 15, 2013, 5:06 PM

Just updated and yes, it all seems to be working properly again and I'm unable to reproduce, thank you.

athurdent · Feb 15, 2013, 6:12 PM

Hmm, trying to add a Block rule for IPv6 ICMP traffic from "Single Host or Alias" fe80::1 always results in a Network Source with fe80::1/32 for me. I'm on the latest snapshot Fri Feb 15 04:06:24 EST 2013.
Can anybody else confirm this or is that just my system?

phil.davis · Feb 17, 2013, 9:16 AM

fe80::1/32 issue should be fixed in snapshots after this commit: https://github.com/bsdperimeter/pfsense/commit/507aa90af48b14ffaab6664c708a3b03d723164c

athurdent · Feb 17, 2013, 9:29 AM

I have confirmed that it's working now and updated the ticket. Forgot to post here, thanks for the reminder!