The pfSense Store

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - gordc

Pages: [1] 2 3 4 5
1
Official pfSense Hardware / SG-1000 bandwidth issues
« on: October 30, 2017, 07:48:18 am »
I have been working on this case with support since Aug 25 (#27001).   As indicated in the notes I ran extensive testing on the firewall in question only to be told that support could not replicate the problem that it must be an issue with the particular unit I had.   We paid to send the firewall back and we received it back with a new board inside.   When I plugged it in I had the exact same issue.  By this time the issue is two months old.   The client that purchased the firewall has been using a borrowed firewall during this time.  Now I am told it is a bug #7532 and that I have to wait for the bug fix.

So here are my concerns.  If this is a bug and support was supposed to have tried to replicate the problem why did they indicate they could not.
When I look at the bug I notice that it is stated that it was to be fixed in 2.4.1 but then pushed to 2.4.2 and now 2.4.3
So how long do we have to wait so that the product purchased over two months ago is usable since in the meantime the client has a firewall that is useless to them.   This may not seem like an issue to you but it is to the client who is a small non-profit company with little money to spend on IT which is why we went with this unit to begin with.
I am not happy at all with pfSense at this point. 

2
Official pfSense Hardware / Re: SG-1000 microFirewall
« on: October 25, 2017, 09:33:36 am »
I have been working on this case with support since Aug 25 (#27001).   As indicated in the notes I ran extensive testing on the firewall in question only to be told that support could not replicate the problem that it must be an issue with the particular unit I had.   We paid to send the firewall back and we received it back with a new board inside.   When I plugged it in I had the exact same issue.  By this time the issue is two months old.   The client that purchased the firewall has been using a borrowed firewall during this time.  Now I am told it is a bug #7532 and that I have to wait for the bug fix.

So here are my concerns.  If this is a bug and support was supposed to have tried to replicate the problem why did they indicate they could not.
When I look at the bug I notice that it is stated that it was to be fixed in 2.4.1 but then pushed to 2.4.2 and now 2.4.3
So how long do we have to wait so that the product purchased over two months ago is usable since in the meantime the client has a firewall that is useless to them.   This may not seem like an issue to you but it is to the client who is a small non-profit company with little money to spend on IT which is why we went with this unit to begin with.
I am not happy at all with pfSense at this point.

3
Official pfSense Hardware / Re: SG-1000 oddity (maybe hardware bug?)
« on: August 29, 2017, 07:23:26 am »
I am still working on this.  At this time I am not completely sure what is going on.  I am going to be setting this firewall up in my lab and run some tests. 

4
Official pfSense Hardware / Re: SG-1000 oddity (maybe hardware bug?)
« on: August 25, 2017, 10:21:37 am »
What was the result of this.  I have a client that is having this exact same issue.   As soon as they use the 100MB switch their speeds drop to nothing.

5
2.4 Development Snapshots / Re: SG-1000 issue
« on: August 22, 2017, 03:38:49 pm »
We often have to do it because the ISP hard codes the speed/duplex.  Autoselect causes issues when they do this.

6
2.4 Development Snapshots / Re: SG-1000 issue
« on: August 22, 2017, 02:45:08 pm »
After looking at the gateway logs I am thinking there is a speed/duplex mismatch as indicated.  I usually don't use autoselect and that is what it is set at.

Thanks for the reply.

7
2.4 Development Snapshots / Re: SG-1000 issue
« on: August 22, 2017, 02:32:32 pm »
This makes me wonder if it is a speed/duplex issue.  It is currently set to autoselect.  I could be wrong but I thought this was set to 100baseTX full duplex.  When I get a chance I will try changing this.  The firewall is located elsewhere and dont want to change it remotely.


Aug 22 15:18:14   dpinger      WANGW 184.70.46.41: Clear latency 12750us stddev 7442us loss 17%
Aug 22 15:17:45   dpinger      WANGW 184.70.46.41: Alarm latency 13080us stddev 8634us loss 21%
Aug 22 15:13:47   dpinger      WANGW 184.70.46.41: Clear latency 15156us stddev 7528us loss 18%
Aug 22 15:12:45   dpinger      WANGW 184.70.46.41: Alarm latency 13742us stddev 7397us loss 21%
Aug 22 14:02:08   dpinger      WANGW 184.70.46.41: Clear latency 12726us stddev 6721us loss 17%
Aug 22 14:01:47   dpinger      WANGW 184.70.46.41: Alarm latency 13176us stddev 6498us loss 21%
Aug 22 13:45:19   dpinger      WANGW 184.70.46.41: Clear latency 16134us stddev 8836us loss 19%
Aug 22 13:44:58   dpinger      WANGW 184.70.46.41: Alarm latency 15759us stddev 8625us loss 21%
Aug 22 13:31:15   dpinger      WANGW 184.70.46.41: Clear latency 13211us stddev 6386us loss 20%
Aug 22 13:30:57   dpinger      WANGW 184.70.46.41: Alarm latency 13172us stddev 6238us loss 21%
Aug 22 13:30:56   dpinger      WANGW 184.70.46.41: Clear latency 12995us stddev 6242us loss 19%
Aug 22 13:30:43   dpinger      WANGW 184.70.46.41: Alarm latency 12521us stddev 6148us loss 21%
Aug 22 13:28:27   dpinger      WANGW 184.70.46.41: Clear latency 11987us stddev 5275us loss 13%
Aug 22 13:27:10   dpinger      WANGW 184.70.46.41: Alarm latency 11816us stddev 6244us loss 22%
Aug 22 13:22:38   dpinger      WANGW 184.70.46.41: Clear latency 14519us stddev 13324us loss 20%
Aug 22 13:21:29   dpinger      WANGW 184.70.46.41: Alarm latency 15109us stddev 8514us loss 21%
Aug 22 13:17:53   dpinger      WANGW 184.70.46.41: Clear latency 13772us stddev 6947us loss 17%
Aug 22 13:17:37   dpinger      WANGW 184.70.46.41: Alarm latency 15529us stddev 7296us loss 21%
Aug 22 13:17:22   dpinger      WANGW 184.70.46.41: Clear latency 15388us stddev 7366us loss 19%
Aug 22 13:16:51   dpinger      WANGW 184.70.46.41: Alarm latency 15241us stddev 8437us loss 21%
Aug 22 13:01:40   dpinger      WANGW 184.70.46.41: Clear latency 16017us stddev 9412us loss 14%
Aug 22 13:00:23   dpinger      WANGW 184.70.46.41: Alarm latency 12731us stddev 6924us loss 21%
Aug 22 12:10:23   dpinger      WANGW 184.70.46.41: Clear latency 12759us stddev 8030us loss 18%
Aug 22 12:09:28   dpinger      WANGW 184.70.46.41: Alarm latency 14062us stddev 6526us loss 21%
Aug 22 11:56:14   dpinger      WANGW 184.70.46.41: Clear latency 14633us stddev 8874us loss 16%

8
2.4 Development Snapshots / Re: SG-1000 issue
« on: August 22, 2017, 01:02:42 pm »
Thanks for the quick response.

Here is a larger sample of the logs.

Does the upgrade require a reboot.  If so I will have to schedule the upgrade. 

Aug 22 13:46:36   pkg      pfSense-repo upgraded: 2.4.0.r.20170821.1244 -> 2.4.0.r.20170822.1126
Aug 22 13:45:19   check_reload_status      Reloading filter
Aug 22 13:45:19   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:45:19   check_reload_status      Restarting ipsec tunnels
Aug 22 13:45:19   check_reload_status      updating dyndns WANGW
Aug 22 13:44:58   check_reload_status      Reloading filter
Aug 22 13:44:58   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:44:58   check_reload_status      Restarting ipsec tunnels
Aug 22 13:44:58   check_reload_status      updating dyndns WANGW
Aug 22 13:31:15   check_reload_status      Reloading filter
Aug 22 13:31:15   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:31:15   check_reload_status      Restarting ipsec tunnels
Aug 22 13:31:15   check_reload_status      updating dyndns WANGW
Aug 22 13:30:57   check_reload_status      Reloading filter
Aug 22 13:30:57   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:30:57   check_reload_status      Restarting ipsec tunnels
Aug 22 13:30:57   check_reload_status      updating dyndns WANGW
Aug 22 13:30:56   check_reload_status      Reloading filter
Aug 22 13:30:56   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:30:56   check_reload_status      Restarting ipsec tunnels
Aug 22 13:30:56   check_reload_status      updating dyndns WANGW
Aug 22 13:30:43   check_reload_status      Reloading filter
Aug 22 13:30:43   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:30:43   check_reload_status      Restarting ipsec tunnels
Aug 22 13:30:43   check_reload_status      updating dyndns WANGW
Aug 22 13:28:27   check_reload_status      Reloading filter
Aug 22 13:28:27   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:28:27   check_reload_status      Restarting ipsec tunnels
Aug 22 13:28:27   check_reload_status      updating dyndns WANGW
Aug 22 13:27:10   check_reload_status      Reloading filter
Aug 22 13:27:10   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:27:10   check_reload_status      Restarting ipsec tunnels
Aug 22 13:27:10   check_reload_status      updating dyndns WANGW
Aug 22 13:22:38   check_reload_status      Reloading filter
Aug 22 13:22:38   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:22:38   check_reload_status      Restarting ipsec tunnels
Aug 22 13:22:38   check_reload_status      updating dyndns WANGW
Aug 22 13:21:30   check_reload_status      Reloading filter
Aug 22 13:21:30   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:21:29   check_reload_status      Restarting ipsec tunnels
Aug 22 13:21:29   check_reload_status      updating dyndns WANGW
Aug 22 13:17:53   check_reload_status      Reloading filter
Aug 22 13:17:53   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:17:53   check_reload_status      Restarting ipsec tunnels
Aug 22 13:17:53   check_reload_status      updating dyndns WANGW
Aug 22 13:17:37   check_reload_status      Reloading filter
Aug 22 13:17:37   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:17:37   check_reload_status      Restarting ipsec tunnels
Aug 22 13:17:37   check_reload_status      updating dyndns WANGW
Aug 22 13:17:22   check_reload_status      Reloading filter
Aug 22 13:17:22   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:17:22   check_reload_status      Restarting ipsec tunnels
Aug 22 13:17:22   check_reload_status      updating dyndns WANGW
Aug 22 13:16:52   check_reload_status      Reloading filter
Aug 22 13:16:52   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:16:52   check_reload_status      Restarting ipsec tunnels
Aug 22 13:16:52   check_reload_status      updating dyndns WANGW
Aug 22 13:01:40   check_reload_status      Reloading filter
Aug 22 13:01:40   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:01:40   check_reload_status      Restarting ipsec tunnels
Aug 22 13:01:40   check_reload_status      updating dyndns WANGW
Aug 22 13:00:23   check_reload_status      Reloading filter
Aug 22 13:00:23   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:00:23   check_reload_status      Restarting ipsec tunnels
Aug 22 13:00:23   check_reload_status      updating dyndns WANGW
Aug 22 12:10:23   check_reload_status      Reloading filter
Aug 22 12:10:23   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 12:10:23   check_reload_status      Restarting ipsec tunnels
Aug 22 12:10:23   check_reload_status      updating dyndns WANGW
Aug 22 12:09:28   check_reload_status      Reloading filter
Aug 22 12:09:28   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 12:09:28   check_reload_status      Restarting ipsec tunnels
Aug 22 12:09:28   check_reload_status      updating dyndns WANGW
Aug 22 11:56:15   check_reload_status      Reloading filter
Aug 22 11:56:14   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:56:14   check_reload_status      Restarting ipsec tunnels
Aug 22 11:56:14   check_reload_status      updating dyndns WANGW
Aug 22 11:55:20   check_reload_status      Reloading filter
Aug 22 11:55:20   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:55:20   check_reload_status      Restarting ipsec tunnels
Aug 22 11:55:20   check_reload_status      updating dyndns WANGW
Aug 22 11:45:15   check_reload_status      Reloading filter
Aug 22 11:45:15   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:45:15   check_reload_status      Restarting ipsec tunnels
Aug 22 11:45:15   check_reload_status      updating dyndns WANGW
Aug 22 11:43:57   check_reload_status      Reloading filter
Aug 22 11:43:57   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:43:57   check_reload_status      Restarting ipsec tunnels
Aug 22 11:43:57   check_reload_status      updating dyndns WANGW
Aug 22 11:42:27   check_reload_status      Reloading filter
Aug 22 11:42:27   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:42:27   check_reload_status      Restarting ipsec tunnels
Aug 22 11:42:27   check_reload_status      updating dyndns WANGW
Aug 22 11:41:17   check_reload_status      Reloading filter
Aug 22 11:41:17   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:41:17   check_reload_status      Restarting ipsec tunnels
Aug 22 11:41:17   check_reload_status      updating dyndns WANGW
Aug 22 11:41:13   check_reload_status      Reloading filter
Aug 22 11:41:13   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:41:13   check_reload_status      Restarting ipsec tunnels
Aug 22 11:41:13   check_reload_status      updating dyndns WANGW
Aug 22 11:41:03   check_reload_status      Reloading filter
Aug 22 11:41:03   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:41:03   check_reload_status      Restarting ipsec tunnels
Aug 22 11:41:03   check_reload_status      updating dyndns WANGW
Aug 22 11:40:22   check_reload_status      Reloading filter
Aug 22 11:40:22   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:40:22   check_reload_status      Restarting ipsec tunnels
Aug 22 11:40:22   check_reload_status      updating dyndns WANGW
Aug 22 11:38:22   check_reload_status      Reloading filter
Aug 22 11:38:22   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:38:22   check_reload_status      Restarting ipsec tunnels
Aug 22 11:38:22   check_reload_status      updating dyndns WANGW
Aug 22 11:33:20   check_reload_status      Reloading filter
Aug 22 11:33:20   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:33:20   check_reload_status      Restarting ipsec tunnels
Aug 22 11:33:20   check_reload_status      updating dyndns WANGW
Aug 22 11:31:15   check_reload_status      Reloading filter
Aug 22 11:31:15   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:31:15   check_reload_status      Restarting ipsec tunnels
Aug 22 11:31:15   check_reload_status      updating dyndns WANGW
Aug 22 11:30:44   check_reload_status      Reloading filter
Aug 22 11:30:44   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:30:44   check_reload_status      Restarting ipsec tunnels
Aug 22 11:30:44   check_reload_status      updating dyndns WANGW
Aug 22 11:29:32   check_reload_status      Reloading filter
Aug 22 11:29:32   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 11:29:32   check_reload_status      Restarting ipsec tunnels
Aug 22 11:29:32   check_reload_status      updating dyndns WANGW
Aug 22 09:52:35   check_reload_status      Reloading filter
Aug 22 09:52:35   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:52:35   check_reload_status      Restarting ipsec tunnels
Aug 22 09:52:35   check_reload_status      updating dyndns WANGW
Aug 22 09:51:57   check_reload_status      Reloading filter
Aug 22 09:51:57   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:51:57   check_reload_status      Restarting ipsec tunnels
Aug 22 09:51:57   check_reload_status      updating dyndns WANGW
Aug 22 09:50:50   check_reload_status      Reloading filter
Aug 22 09:50:50   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:50:50   check_reload_status      Restarting ipsec tunnels
Aug 22 09:50:50   check_reload_status      updating dyndns WANGW
Aug 22 09:46:27   check_reload_status      Reloading filter
Aug 22 09:46:27   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:46:27   check_reload_status      Restarting ipsec tunnels
Aug 22 09:46:27   check_reload_status      updating dyndns WANGW
Aug 22 09:44:26   check_reload_status      Reloading filter
Aug 22 09:44:26   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:44:26   check_reload_status      Restarting ipsec tunnels
Aug 22 09:44:26   check_reload_status      updating dyndns WANGW
Aug 22 09:41:50   check_reload_status      Reloading filter
Aug 22 09:41:50   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:41:50   check_reload_status      Restarting ipsec tunnels
Aug 22 09:41:50   check_reload_status      updating dyndns WANGW
Aug 22 09:31:36   check_reload_status      Reloading filter
Aug 22 09:31:36   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:31:36   check_reload_status      Restarting ipsec tunnels
Aug 22 09:31:36   check_reload_status      updating dyndns WANGW
Aug 22 09:31:21   check_reload_status      Reloading filter
Aug 22 09:31:21   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:31:21   check_reload_status      Restarting ipsec tunnels
Aug 22 09:31:21   check_reload_status      updating dyndns WANGW
Aug 22 09:30:32   check_reload_status      Reloading filter
Aug 22 09:30:32   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:30:32   check_reload_status      Restarting ipsec tunnels
Aug 22 09:30:32   check_reload_status      updating dyndns WANGW
Aug 22 09:29:39   check_reload_status      Reloading filter
Aug 22 09:29:39   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:29:39   check_reload_status      Restarting ipsec tunnels
Aug 22 09:29:39   check_reload_status      updating dyndns WANGW
Aug 22 09:29:30   check_reload_status      Reloading filter
Aug 22 09:29:30   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:29:30   check_reload_status      Restarting ipsec tunnels
Aug 22 09:29:30   check_reload_status      updating dyndns WANGW
Aug 22 09:26:59   check_reload_status      Reloading filter
Aug 22 09:26:59   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:26:59   check_reload_status      Restarting ipsec tunnels
Aug 22 09:26:59   check_reload_status      updating dyndns WANGW
Aug 22 09:25:26   check_reload_status      Reloading filter
Aug 22 09:25:26   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:25:26   check_reload_status      Restarting ipsec tunnels
Aug 22 09:25:26   check_reload_status      updating dyndns WANGW
Aug 22 09:24:38   check_reload_status      Reloading filter
Aug 22 09:24:38   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:24:38   check_reload_status      Restarting ipsec tunnels
Aug 22 09:24:38   check_reload_status      updating dyndns WANGW
Aug 22 09:17:26   check_reload_status      Reloading filter
Aug 22 09:17:26   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:17:26   check_reload_status      Restarting ipsec tunnels
Aug 22 09:17:26   check_reload_status      updating dyndns WANGW
Aug 22 09:15:17   check_reload_status      Reloading filter
Aug 22 09:15:17   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:15:17   check_reload_status      Restarting ipsec tunnels
Aug 22 09:15:17   check_reload_status      updating dyndns WANGW
Aug 22 09:14:12   check_reload_status      Reloading filter
Aug 22 09:14:12   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:14:12   check_reload_status      Restarting ipsec tunnels
Aug 22 09:14:12   check_reload_status      updating dyndns WANGW
Aug 22 09:13:16   check_reload_status      Reloading filter
Aug 22 09:13:16   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 09:13:16   check_reload_status      Restarting ipsec tunnels
Aug 22 09:13:16   check_reload_status      updating dyndns WANGW
Aug 22 08:57:15   pkg      pfSense-repo downgraded: 2.4.1.a.20170821.1244 -> 2.4.0.r.20170821.1244

9
2.4 Development Snapshots / SG-1000 issue
« on: August 22, 2017, 12:50:51 pm »
I keep seeing the following repeated every minute or so.


Time                           Process                  PID   Message
Aug 22 13:31:15   check_reload_status      Reloading filter
Aug 22 13:31:15   check_reload_status      Restarting OpenVPN tunnels/interfaces
Aug 22 13:31:15   check_reload_status      Restarting ipsec tunnels
Aug 22 13:31:15   check_reload_status      updating dyndns WANGW


Current Base System 2.4.0.b.20170710.2021


10
2.4 Development Snapshots / Re: SG-1000
« on: August 22, 2017, 08:05:20 am »
Normally I would agree about the untested hardware.   This is an unusual case in that regard though.  The client has a problem with getting hit by lightening.  They have had the problem for years and haven't been able to find a good solution.   As a result they end having to replace equipment fairly often.  So they are more concerned about price point than using untested hardware.

11
2.4 Development Snapshots / Re: SG-1000
« on: August 18, 2017, 12:54:51 pm »
I agree there should be some kind of notice or disclaimer on the page indicating that the unit is using BETA software.  In this case the unit was purchased for a client.   They noticed while I was installing it that it said    2.4.0-BETA on the dashboard.   This ended up with having to have a meeting to with both my boss and the client explaining what happened and also trying to reassure them that the product would not cause any issues.   This resulted in time for both us and the client in dealing with this.  It has also resulted in that the client is now questioning us a lot more on all aspects of our support.   All this could have been eliminated with a simple disclaimer.

12
2.4 Development Snapshots / Re: SG-1000
« on: August 17, 2017, 09:33:18 am »
OK.  I guess what I am getting to with the BETA version is that nothing indicated that this unit was shipping with a BETA version on it.  Shouldn't there be some kind of note or notice on the page for the device indicating that the unit is shipping with that version on it.  Then if the person orders it they are fully aware of what they are getting.

13
Firewalling / Re: States column
« on: August 16, 2017, 10:34:28 am »
Thanks.  That helps.  I am going to go over the rules and see what is going on.  We had to make a lot of changes in a hurry recently so I need to clean things up now.  We moved offices, and introduced VOIP at the same time.  Lots of fun.

14
2.4 Development Snapshots / Re: SG-1000
« on: August 16, 2017, 10:30:12 am »
Thanks for the quick reply.  Much appreciated.

15
Firewalling / States column
« on: August 16, 2017, 08:43:37 am »
I am doing a review of my firewall rules and I have a question regarding the states column when looking at the rules list. 
It shows X/X B

I am a little confused with this. 
I have done some reading that this is the amount traffic associated with a state.  So that number will show 0/0B if there is no current state made using that rule.   Does that mean that rule is not being used, or just that it is not being used at the time of viewing.  When I look at my list of rules and see 0/0 B it makes me wonder if the traffic is being handled by a different rule that I am not expecting.

Any clarification on this would be greatly appreciated.

Gord

Pages: [1] 2 3 4 5