Rules Show Strange Byte Count

MaxK 0

@cmcdonald Reloading solved it temporarily but then it reverted back.

johnpoz

@MaxK-0 how long did it take to go - like that? Did it count up really fast to a very large number?

What if you change the rule to just be your source net, which I assume is this barsoumsec net? Why would you have any there as the source - is this a transit network for downstream networks that would not be this barsoumsec net?

MaxK 0

@johnpoz It took maybe a few hours for it to revert. It seems to make it into the GiB range then goes to the strange number.

Source net does not matter (happened with any and barsoumsec):

cmcdonald

@MaxK-0

What platform/hardware are you on?

If you execute the following in the Execute PHP Commands section under Diagnostics > Command Prompt:

print_r(pfSense_get_pf_rules());

After finding the problematic rules, what do they show for bytes ? This will tell me where in the stack the issue is

MaxK 0

@cmcdonald SG-3100. I rebooted and that did not help. Count gets strange after crossing 2 GiB.

Output from print_r:

cmcdonald

@MaxK-0 Yea, it's an overflow caused by PHP limitations on 32bit platforms. It's cosmetic, but is something we should fix. Internally pf(4) stores counters as uint64. However, PHP on 32bit can only represent integers up to 2,147,483,647.

johnpoz

@MaxK-0 said in Rules Show Strange Byte Count:

SG-3100

Well they just extended the $60 off upgrade for a 4100 ;)

stephenw10

Opened a bug for this: https://redmine.pfsense.org/issues/14440

MaxK 0

@johnpoz I was thinking about that but couldn't tell my wife, with a straight face, that I needed to upgrade because of an 32 bit integer overflow display problem (she worked in IT too). On a side note, I was able to supercharge my car by telling her I needed an "active induction system" - she heard "astro projection system." :-)

MaxK 0

@stephenw10 Thank you very much.

SteveITS

@MaxK-0 said in Rules Show Strange Byte Count:

I needed to upgrade because of an 32 bit integer overflow display problem (she worked in IT too)

Seems like a perfectly good reason IT to upgrade!
https://en.wikipedia.org/wiki/Year_2038_problem
(if we get our clients through Y2K and Y2K38 we should be good for a while...right? right? hello?)

Interesting this bug didn't seem to be an issue on 23.01...?

Gertjan

@MaxK-0

I would pay a small fortune for that one : coming home, put on the friendly and puzzled face, and ask : honey, can you take care of the overflow issue ?

edit :
4100 using 23.05 :

IPv6 takes the lead !

johnpoz

@Gertjan said in Rules Show Strange Byte Count:

IPv6 takes the lead !

hahah..

Not here, on a "old" 4860 on 23.05

stephenw10

@SteveITS said in Rules Show Strange Byte Count:

Interesting this bug didn't seem to be an issue on 23.01...?

On a 3100?

SteveITS

@stephenw10 said in Rules Show Strange Byte Count:

@SteveITS said in Rules Show Strange Byte Count:

Interesting this bug didn't seem to be an issue on 23.01...?

On a 3100?

Yes, I didn't specify that, did I. You made me check again though since we have a few routers in our office...make sure I connected to the right one yesterday. :) (tip: colored login page backgrounds)

stephenw10

Ha, yup, I've run out of colours at this point!

SteveITS

@stephenw10 said in Rules Show Strange Byte Count:

Ha, yup, I've run out of colours at this point!

In your next team meeting point out most video drivers now can show 16 million. #a3bd44 and #a3bd43 are different after all. ;)

Perhaps a checkbox to show the router hostname on the login screen?

But I digress…

stephenw10

There are several options being discussed..

SteveITS

@SteveITS said in Rules Show Strange Byte Count:

Perhaps a checkbox to show the router hostname on the login screen?

“Show hostname on login banner”
Oh hey look at that.

stephenw10

Be nice to show other things there maybe.