Simplewall: Improve network alert

Created on 20 Mar 2020  路  3Comments  路  Source: henrypp/simplewall

Currently, this information is provided:
grafik

In case of inbound this just gives us the source address (and source port I _assume_) and in case of outbound it just gives the destination address and port.

  1. Could you please add destination ("local") information for inbound and source ("local") information for outbound?

Each network alert steals the focus which can be very annoying and interrupting.

  1. Could you please add an option to still show the network alerts but NOT requesting focus?

And alternative would be not showing the network alerts window but sending a Windows notification instead. Clicking the notification would then open the network alerts window with all the missed alerts.

edit:
Creating a rule based on an inbound network alert only does not fill in the local address.

  1. Please fill both remote and local addresses (if available) when creating a new rule.
bug question

Most helpful comment

In case of inbound this just gives us the source address (and source port I _assume_) and in case of outbound it just gives the destination address and port.

Network alerts displays only remote address information, because local address are used local network ip's or empty (0.0.0.0)

Could you please add an option to still show the network alerts but NOT requesting focus?

This is UI bug and fixed now.

All 3 comments

I also think color wise there should be some difference between outbound and inbound connection notification.

In case of inbound this just gives us the source address (and source port I _assume_) and in case of outbound it just gives the destination address and port.

Network alerts displays only remote address information, because local address are used local network ip's or empty (0.0.0.0)

Could you please add an option to still show the network alerts but NOT requesting focus?

This is UI bug and fixed now.

Network alerts displays only remote address information, because local address are used local network ip's or empty (0.0.0.0)

The information is actually very important and it's not just the IP address but also the port.

What does "Remote: x.x.x.x, Port: 56832, Inbound" tell you? Nothing.

This could have been an inbound connection to some svchost service, a http server, a ssh server ...
Right now, to find out what the destination was, I have to enable the log, then search for the remote port and then in the log line it also gives me the local address & port.

Please add this.

Also, instead of having two fields for the address and port you could just do: ":" in a single line.

Lastly, the local IP address is also very important. Use cases are multiple interfaces with different IPs, broadcasts, multicasts, etc.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

geonanorch picture geonanorch  路  3Comments

ltGuillaume picture ltGuillaume  路  3Comments

ltGuillaume picture ltGuillaume  路  3Comments

TontyTon picture TontyTon  路  3Comments

pwn0r picture pwn0r  路  3Comments