search

custom-components / authenticated

A platform which allows you to get information about sucessfull logins to Home Assistant.
MIT License
82 stars 28 forks source link

exclude RANGE of IPs (not LIST of IPs) #55

Closed enrysan0 closed 4 years ago

enrysan0 commented 4 years ago

Hi,

it seems I didn't explain well my problem with the precend issue that was closed without a truly sensate answer to my question. So here I'm to explain again with other words my issue. If it's not an issue, but a feature not implemented yet, sorry if I posted in the wrong section and please move this topic to the feature request. Thanks

Version of the custom_component 1.2.2

Describe the bug is this component able to exclude RANGE of IPs and not only LIST of IPs?

I know that with this configuration I can exclude a LIST o IPs:

- platform: authenticated
  enable_notification: yes
  exclude:
      - 108.177.64.1
      - 108.177.70.1
      - 108.177.71.1

But I'm triyng to exclude a RANGE of IPs: for example all the IPs from 108.177.64.1 to 108.177.64.254. Can I simple use a configuration like this:

- platform: authenticated
  enable_notification: yes
  exclude:
      - 108.177.64.0

or

- platform: authenticated
  enable_notification: yes
  exclude:
      - 108.177.64.0/24

or simple this component isn't able to exclude RANGE of IPs?

Thanks for your time.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

enrysan0 commented 4 years ago

No this issue is not solved yet. Thanks

officiallybob commented 4 years ago

I agree, it would be nice to exclude full subnets/ranges from this. For example, my cell data IP changes frequently, but always within the same range managed by my cell operator. Be nice to exclude the entire range so I'm not flooded by my own logins.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

enrysan0 commented 4 years ago

Not solved jet. Thanks

enrysan0 commented 4 years ago

This issue is'nt solved, so I don't understand why it was closed.

akargl commented 4 years ago

Just FYI, you can use notation like 192.168.1.0/24 in the exclude option since #44

enrysan0 commented 4 years ago

Just FYI, you can use notation like 192.168.1.0/24 in the exclude option since #44

Thanks for your answer. I'll try this way.