1) Check logs to see what it says when it can't load the menu.
2023.01.04 06:37:07 Setting start menu:
2023.01.04 06:37:07 Error loading menu:
2023.01.04 06:37:07 Shutting down
choose to disable the anti-spoofing (IP) check? E.g. for the scenario
when a user uses fTelnet (an fTelnet proxy somewhere in the world) and then wants to download the file via his/her web browser (another IP)?
A configuration option for the download URL (e.g. if you have a web
server in front of MIS for HTTPS support with a "real" SSL certificate) would also be a great addition. :)
Can you upgrade to the latest build in prealpha when you have time and check the logs again. I changed it to show where its taking the menu value from which should help me get to the bottom of the issue.
2023.01.04 13:33:16 Setting time left to 60
2023.01.04 13:33:16 Setting menu to "" (Security start menu)
2023.01.04 13:33:16 Error loading menu:
You can also just go into the user and do a CTRL+U select the security level and it never changes the start menu for the user.
As far as it not updating the user field when you upgrade the user security level, thats expected behavior. Older versions would copy the start menu from the security into the user record, but now it just pulls the menu name directly from the security record.
The reason for the change is because if you wanted to change the start menu for a security level in the past you'd have to then go into each user's record and update their start menu field. Now you can blank out all of the user's start menu fields and let it pull the menu from the system default or their security profile. You'd only set the start menu directly on the user's record if you really wanted them to have their
own custom start menu.
Hope I was able to explain that in a way that made sense lol.
Hope I was able to explain that in a way that made sense lol.
I think I'll put up something in the FAQ about this as it seems to be something that folks may need some further education / awareness on.
I was able to find the issue with that logging, thank you! I am
uploading a new build now which will include the fix.
As far as it not updating the user field when you upgrade the user security level, thats expected behavior. Older versions would copy the start menu from the security into the user record, but now it just pulls the menu name directly from the security record.
The reason for the change is because if you wanted to change the start menu for a security level in the past you'd have to then go into each user's record and update their start menu field. Now you can blank out all of the user's start menu fields and let it pull the menu from the system default or their security profile. You'd only set the start menu directly on the user's record if you really wanted them to have their
own custom start menu.
Hope I was able to explain that in a way that made sense lol.
I think I'll put up something in the FAQ about this as it seems to be something that folks may need some further education / awareness on.
Makes perfect sense. There was something else related to this kind of change to. A mass way of updating users security levels? Any way of
doing that. I'm getting of topic, but curious.
It couldn't hurt. It should be somewhere in there thats for sure. FAQ might make sense and then when it comes time to document the start menu fields in System Config, Security editor, user editor, etc it can link back to that FAQ?
I did discuss it in the whatsnew also.
Makes perfect sense. There was something else related to this kind of change to. A mass way of updating users security levels? Any way of doing that. I'm getting of topic, but curious.
There isn't a global user editor for some reason. I don't really
remember why I never made one considering things like Echomail nodes, msg/file bases all have them.
I don't want to work on it before A48 at this point since I'd like to
get this thing released sooner than later, but I think it could be something that I focus on early in A49
Alright don't mean to add more to your list.
I have some other questions, unrelated to this.
I will create a new message.
fTelnet should be responding to a SENDLOC request which allows Mystic to get the non-proxied IP address of the user. This is either not working
or Mystic is accidentally not using that IP for web downloads which is highly possible.
Yes, it seems so. I have enabled the fTelnet SendLocation support (I'm using the https://embed-v2.ftelnet.ca/ fTelnet Embed Wizard), but still see the proxy IP instead of the client IP in the .dlreq data file.
I added some logging into the MIS window for the telnet location and its in the latest Linux/Pi builds that I just put up. It does look like I wasn't passing the location IP into Mystic, but there is code there to
get the value.
Lets first make sure that the location part works and then I can move on to getting dlreq sorted out.
I just pulled the latest 64-bit Linux A48 prealpha, but I'm afraid it doesn't appear to work as it still logs:
------------------- Node 2 (Mystic v1.12 A48 2023/01/05)
2023.01.06 19:43:43 Connect from 81.4.100.99 (81-4-100-99.cloud.ramnode.com) 2023.01.06 19:43:43 Country: Netherlands
Sorry I didn't explain it well. The log you need to look at is the MIS log. It should log that it received a telnet location when the
connection received is logged.
| Sysop: | Nitro |
|---|---|
| Location: | Portland, OR |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 58:39:47 |
| Calls: | 132 |
| Files: | 710 |
| Messages: | 85,089 |