"
Hi,
- Update from 26.1.4 to 26.1.11 (is also when upgrading to 26.1.8)
- The captive portal is no longer working, because the redirection is not working
- When a new captive portal is created, there are the automatically generated firewall rules which you can see in Rules [new]:
- Allow access from IF "902_CaPo_113" to "This firewall" port 9006
- Allow access from IF "902_CaPo_113" to "This firewall" port 8006
- Block access from IF "902_CaPo_113" to "! __captiveportal_zone_6" this is the "Default Captive Portal block rule (zone 6)"
- Automatic Redirection is not done
- When using a self-constructed https link to port 8006,
you arrive at the portal. And when the credentials are entered,
you get access to the configured destination.
- When using https on port 8006, after authentication the redirection is in http and not in https,
you need to change the link to https to get access after all
- Disabling the "Client roaming option" does not change anything
Anyone some ideas?
Kind regards
- Update from 26.1.4 to 26.1.11 (is also when upgrading to 26.1.8)
- The captive portal is no longer working, because the redirection is not working
- When a new captive portal is created, there are the automatically generated firewall rules which you can see in Rules [new]:
- Allow access from IF "902_CaPo_113" to "This firewall" port 9006
- Allow access from IF "902_CaPo_113" to "This firewall" port 8006
- Block access from IF "902_CaPo_113" to "! __captiveportal_zone_6" this is the "Default Captive Portal block rule (zone 6)"
- Automatic Redirection is not done
- When using a self-constructed https link to port 8006,
you arrive at the portal. And when the credentials are entered,
you get access to the configured destination.
- When using https on port 8006, after authentication the redirection is in http and not in https,
you need to change the link to https to get access after all
- Disabling the "Client roaming option" does not change anything
Anyone some ideas?
Kind regards
