mirror of
https://github.com/f00b4r0/uspot.git
synced 2026-04-26 06:35:54 +03:00
[GH-ISSUE #14] Unable to dispaly login Form #10
Labels
No labels
bug
enhancement
invalid
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uspot#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BDZK on GitHub (Jun 22, 2024).
Original GitHub issue: https://github.com/f00b4r0/uspot/issues/14
Hi
I have installed your software on openwrt.
i have this error on login page Error, An error occured. Please retry.
in the log i have :
daemon.err uhttpd[4138]: uspot: 10.1.8.178 - config not found for "null"
Can you help me please?
@BDZK commented on GitHub (Jun 23, 2024):
It seems that the login script cannot get the mac address, IP etc. of the client. I wonder why. Maybe i nee to install manually a dependency?
@f00b4r0 commented on GitHub (Jun 24, 2024):
Please provide:
opkg list-installed | grep uspot/etc/config/uspot,/etc/config/firewall,/etc/config/dhcp,/etc/config/uhttpd- mask private information such as passwordslogread -e uspotwhen the problem occurs@BDZK commented on GitHub (Jun 24, 2024):
Hello,
Thanks for your replay. Meanwhile I was able to display the login form.
I just renamed 'example' by 'captive' (the name of the hotspot interface) in /etc/config/uspot.
And also i have commented the uam section in /etc/config/uhttpd.
But not i try to login i have this error in the log (logread -f):
user.err : radcli: rc_read_dictionary: rc_read_dictionary couldn't open dictionary /etc/radcli/dictionary: No such file or directory
I have checked in System/Software and libradcli is installed...
Can i get a dictionnary on line and paste in the /etc/radcli folder?
@f00b4r0 commented on GitHub (Jun 24, 2024):
Please follow the instructions https://github.com/f00b4r0/uspot?tab=readme-ov-file#radcli
@BDZK commented on GitHub (Jun 25, 2024):
Now if i submit the form i have 'invalid credentials'.
logread -e uspot is giving me this:
Tue Jun 25 02:59:09 2024 daemon.err uhttpd[2558]: uspot: 10.1.8.44 - start radius flow
Tue Jun 25 02:59:26 2024 daemon.err uhttpd[2558]: uspot: 10.1.8.234 - invalid credentials
Tue Jun 25 02:59:26 2024 daemon.err uhttpd[2558]: uspot: 10.1.8.234 - start radius flow
Tue Jun 25 02:59:26 2024 daemon.err uhttpd[2558]: uspot: 10.1.8.234 - start radius flow
It seems that the form is not even submitting.
Because i check on the radius server and no auth request is present from the client...
@f00b4r0 commented on GitHub (Jun 25, 2024):
Please provide all the requested data.
@BDZK commented on GitHub (Jun 25, 2024):
Here are the requested data :
Tue Jun 25 09:14:20 2024 daemon.debug uspot: captive acct-on call
Tue Jun 25 09:14:37 2024 daemon.err uhttpd[2590]: uspot: 10.1.8.44 - start credentials flow
Tue Jun 25 09:14:37 2024 daemon.err uhttpd[2590]: uspot: 10.1.8.44 - start credentials flow
Tue Jun 25 09:14:44 2024 daemon.err uhttpd[2590]: uspot: 10.1.8.44 - invalid credentials
Tue Jun 25 09:14:44 2024 daemon.err uhttpd[2590]: uspot: 10.1.8.44 - start credentials flow
Tue Jun 25 09:14:44 2024 daemon.err uhttpd[2590]: uspot: 10.1.8.44 - start credentials flow
Other files attached.
Thanks.
dhcp.txt
firewall.txt
httpd.txt
uspot.txt
@f00b4r0 commented on GitHub (Jun 25, 2024):
Option
nasmacis unset, I think that's the problem.@BDZK commented on GitHub (Jun 25, 2024):
Still not working... I have set it with the mac of the captive interface but still not working
@f00b4r0 commented on GitHub (Jun 25, 2024):
You either have a configuration error in uspot or a configuration error in your RADIUS server. With no further information there is very little I can do. You can try setting
option debug '1'in the uspot interface configuration to expand further error messages from uspot@f00b4r0 commented on GitHub (Sep 17, 2024):
Do you have further input to provide or has this issue been resolved for you?
@f00b4r0 commented on GitHub (Jan 20, 2025):
no news after 6 months, closing.