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

An option to allow LAN traffic based on the device's MAC address. #1560

Closed
AllenCyborg opened this issue May 31, 2024 · 5 comments
Closed

An option to allow LAN traffic based on the device's MAC address. #1560

AllenCyborg opened this issue May 31, 2024 · 5 comments
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements

Comments

@AllenCyborg
Copy link

What would you like to add or change?:
An option to allow traffic to and from LAN devices based on their MAC addresses. I do not know about the feasibility of such an option nor the security implications. The way I see this working is PM scans MAC addresses of all LAN devices similar to network monitoring tools, then automatically temporarily whitelists the IP of the device with the MAC the user wants to let through. Maybe this would need to be run periodically to change IP of the device as it changes or when another device is connected.

If a MAC address based solution is not possible, then some other way to persist rules to specific devices that may change its assigned local IP is what I'm trying to suggest.

Why do you and others need this?:
This would make it easier to talk to LAN devices that do not have a static IP and to the ones that use mDNS. Examples include Printers, IoT devices, etc.

The alternatives now are:

  1. Allow incoming traffic from a specific IP using an APP/global setting.
  2. Disable force-block incoming LAN option.
  3. Shutdown PM all together.

IMO all of these are less than ideal .
Another less way would be to have an option to allow traffic for a set amount of time with an option to immediately terminate if connection to the device is lost for a defined amount of time.

@AllenCyborg AllenCyborg added the suggestion TYPE: idea for new feature or improvements label May 31, 2024
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@Raphty
Copy link
Member

Raphty commented May 31, 2024

Interesting idea, I guess just using the dhc server to set the static IP is not what you are looking for? are you concerned that a device will not respect the configured setting?

we are thinking about more extended network protections like port scan detection and so on. Sadly we see not much resonance about those things in the community over all, and we need to focus our limited resources on the things that actually are in demand.

I hope you understand, and i hope you shed some more light on the specifics why you would need this feature.

@AllenCyborg
Copy link
Author

I thought this would be a better option than a static IP cuz:

  1. I'm connected to someone else's shared router/network(with permission) and that would be an awkward conversation 😅 since I sometimes use multiple wifi dev boards during development.
  2. I sometimes connect to other networks including Android Hotspots and I don't think it's possible to assign a static IP there.
  3. I think this would be a nice feature to have.

Copy link

github-actions bot commented Aug 5, 2024

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Aug 5, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements
Projects
None yet
Development

No branches or pull requests

2 participants