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

Disabling client internet access does not work until a reboot #24

Open
esotericnonsense opened this issue Dec 18, 2021 · 2 comments
Open
Labels
bug Something isn't working

Comments

@esotericnonsense
Copy link
Contributor

esotericnonsense commented Dec 18, 2021

Reproduce: connect a device, enable internet access for the client, disable it, internet access still functions until a host reboot.

Issue: the iptables rules are persistent, forwarding is never removed.

Solution: change the code such that forwarding is disabled (at least for the specific interface) if disabled.

I may end up solving this myself and submitting a PR, just leaving it here for future reference. :)

@mezen
Copy link

mezen commented Feb 7, 2022

Even after rebooting my hassio, the internet access is still granted:

ssid: MySSID
wpa_passphrase: MyPassword
channel: '6'
address: 192.168.42.1
netmask: 255.255.255.0
broadcast: 192.168.42.255
interface: wlan0
hide_ssid: '1'
dhcp: '1'
dhcp_start_addr: 192.168.42.100
dhcp_end_addr: 192.168.42.200
allow_mac_addresses: []
deny_mac_addresses: []
debug: 1
hostapd_config_override: []
client_internet_access: '0'      <--- Is set to Zero
client_dns_override: []

At the moment I use client_dns_override: [127.0.0.1] as a workaround

@mattlongman mattlongman added the bug Something isn't working label Jun 21, 2022
@mattlongman
Copy link
Owner

Doing some testing on PR 20 which will also include this.

@mattlongman mattlongman linked a pull request Jun 24, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants