Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 26 subscribers
  • Views 6512 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Log Viewer - Filter by firewall id stucks

lferrara

Hi All,

I am using the XG 17 MR3 and using the add filter b y rule id will make the log viewer unusable! The wheel in the center is loading but even after 10 minutes, nothing happens. The rule id exists.

Regards



This thread was automatically locked due to age.
Parents
  • 0

    Hi Luk and welcome back,

    Wrong answer, same issue only for the first time and then maybe 15 seconds. Maybe you have lots of traffic against the rule you are sorting on? When I tried one of the lesser used rules the response was almost instantaneous.

     

    Ian

  • 0 in reply to rfcat_vk

    Thanks Ian. On the first Firewall rule (id 24), the match traffic should be only skype exceptions. I tried on the firewall rule which produces more traffic and the filter works.

    Can you try on a small Firewall rule?

    Thanks

  • 0 in reply to lferrara

    Hi Luk,

    well all I can say is that test did not fail, but threw up a bug as far as I am concerned. The rules that do not have much traffic reported against all worked, some quicker than others.

    The bug is, I used to have a rule 10 for IPv6 which due to XG's failure to work correctly and the ISPs IPv6 implementation having developed some connectivity issues, I deleted all references to IPv6. Now to test what you requested I created a new reject rule at the bottom. The new rule's ID is 10 so all the traffic that was in rule 10 for IPv6 now appears in the deny any rule with some of it showing valid connections.

    Some further issues show up with my VoIP phones, there registration traffic does not register in the logs. I have searched using IP address. I have watched as the ATA shows it has re-registered and there is only one entry. I also fixed the NTP issue it was having, well I thought I did. Back to working on that issue.

    Ian

    Update: logviewer does not show any of the phone call traffic from either VoIP phone. Something seriously wrong with the logviewer and the logging sub-system.

Reply
  • 0 in reply to lferrara

    Hi Luk,

    well all I can say is that test did not fail, but threw up a bug as far as I am concerned. The rules that do not have much traffic reported against all worked, some quicker than others.

    The bug is, I used to have a rule 10 for IPv6 which due to XG's failure to work correctly and the ISPs IPv6 implementation having developed some connectivity issues, I deleted all references to IPv6. Now to test what you requested I created a new reject rule at the bottom. The new rule's ID is 10 so all the traffic that was in rule 10 for IPv6 now appears in the deny any rule with some of it showing valid connections.

    Some further issues show up with my VoIP phones, there registration traffic does not register in the logs. I have searched using IP address. I have watched as the ATA shows it has re-registered and there is only one entry. I also fixed the NTP issue it was having, well I thought I did. Back to working on that issue.

    Ian

    Update: logviewer does not show any of the phone call traffic from either VoIP phone. Something seriously wrong with the logviewer and the logging sub-system.

Children
No Data