Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: SOC PCAP column headers hidden from view #14234

Open
1 task done
dougburks opened this issue Feb 14, 2025 · 5 comments
Open
1 task done

FIX: SOC PCAP column headers hidden from view #14234

dougburks opened this issue Feb 14, 2025 · 5 comments
Assignees
Labels
2.4 Planned for 2.4.X PCAP SOC
Milestone

Comments

@dougburks
Copy link
Contributor

Discussed in #14233

Originally posted by Ximalas February 14, 2025

Version

2.4.120

Installation Method

Security Onion ISO image

Description

other (please provide detail below)

Installation Type

Distributed

Location

on-prem with Internet access

Hardware Specs

Exceeds minimum requirements

CPU

32

RAM

384 GB

Storage for /

155 GB (manager)

Storage for /nsm

312 GB (manager)

Network Traffic Collection

tap

Network Traffic Speeds

1Gbps to 10Gbps

Status

Yes, all services on all nodes are running OK

Salt Status

No, there are no failures

Logs

No, there are no additional clues

Detail

I upgraded our fleet to 2.4.120 this morning, around 09:00 UTC. No issues of any kind, except:

The column headers for PCAP are briefly shown, then hidden by the PCAP banner, with the plus button on the left, making it impossible to sort on any columns. Maybe this is intended, but I would argue it's handy to sort the table using any of the available columns.

Also, the contents of each PCAP no longer corresponds to the metadata shown in the pull down.

I didn't have any use for the previously generated PCAPs, so I deleted everything and repeated the latest one. At least the contents of this PCAP matches the metadata shown in the pull down.

Guidelines

@dougburks dougburks added 2.4 Planned for 2.4.X PCAP SOC labels Feb 14, 2025
@dougburks dougburks added this to the 2.4.130 milestone Feb 14, 2025
@dougburks
Copy link
Contributor Author

@Ximalas Thanks for reporting this.

The column headers for PCAP are briefly shown, then hidden by the PCAP banner, with the plus button on the left, making it impossible to sort on any columns. Maybe this is intended, but I would argue it's handy to sort the table using any of the available columns.

I can confirm that this is a bug so I've converted this discussion to an issue.

Also, the contents of each PCAP no longer corresponds to the metadata shown in the pull down.

I haven't been able to duplicate this. Can you provide any further information?

@Ximalas
Copy link

Ximalas commented Feb 14, 2025

We had several PCAPs stored on the manager. After the upgrade, none of them were shown in a numerical ascending order. I clicked on one of them, and adjusted the URL to, say PCAP 1211. The metadata at the top matched this particular PCAP, but the contents of the PCAP was something else entirely.

It's hard to reproduce this particular issue now that I have cleared everything. Later created PCAPs are shown in numerical ascending order, and the packets shown matches what I searched for.

@dougburks
Copy link
Contributor Author

Here's the fix for the next version:
Security-Onion-Solutions/securityonion-soc#751

@dougburks
Copy link
Contributor Author

If your SOC PCAP column headers are currently hidden, you should be able to restore them by clearing your browser cache OR doing the following:

  • go to DevTools > Application > Storage > Local storage > [soc url]
  • find the key settings.jobs.sortBy and delete it
  • refresh the page

However, you will need to wait for 2.4.130 if you want to sort the PCAP page by non-standard values.

@dougburks dougburks changed the title FIX: Column headers hidden from view for PCAP in SOC, and mismatch between PCAP job number and the actual contents FIX: SOC PCAP column headers hidden from view Feb 14, 2025
@Ximalas
Copy link

Ximalas commented Feb 14, 2025

In my case settings.jobs.sortBy was set to number. I'm not sure what value it had earlier today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.4 Planned for 2.4.X PCAP SOC
Projects
None yet
Development

No branches or pull requests

3 participants