Help Needed: “Unsupported protocol” Error with OpenNDS on OpenWrt

Hello everyone,

I am experiencing an issue with OpenNDS on OpenWrt and am seeking some assistance from the community. I've encountered frequent “Unsupported protocol” errors in my logs while attempting to set up the Forwarding Authentication Service (FAS). This error seems to be related to my attempts to download custom files from specific URLs.

Here’s the specific error message I am seeing:

Unsupported protocol [] for [logo.png] in url [] - skipping download
'

Sat May 25 10:11:20 2024 daemon.err opennds[18704]: : Unsupported protocol [] for [logo.png]in url [] - skipping download
Sat May 25 10:11:20 2024 daemon.err opennds[18704]: : Unsupported protocol [] for [banner1.jpg]in url [] - skipping download
Sat May 25 10:11:20 2024 daemon.err opennds[18704]: : Unsupported protocol [] for [banner2.jpg]in url [] - skipping download
Sat May 25 10:11:20 2024 daemon.err opennds[18704]: : Unsupported protocol [] for [banner3.jpg]in url [] - skipping download
Sat May 25 10:11:20 2024 daemon.err opennds[18704]: : Unsupported protocol [] for [advert1.htm]in url [] - skipping download

I have double-checked my configuration files to ensure all URLs are correctly formatted and begin with http:// or https://. Despite this, the error persists. Here is a snippet of my configuration:

bash

list fas_custom_files_list 'logo.png=https://example.com/path/to/logo.png'

config opennds



        option login_option_enabled '3'
        option themespec_path '/usr/lib/opennds/theme_user-email-login-custom-placeholders.sh'
        list fas_custom_images_list 'logo_png=https://openwrt.org/_media/logo.png'
        list fas_custom_images_list 'banner1_jpg=https://raw.githubusercontent.com/openNDS/openNDS/v9.5.0/resources/bannerbw.jpg'
        list fas_custom_images_list 'banner2_jpg=https://raw.githubusercontent.com/openNDS/openNDS/v9.5.0/resources/bannerpickle.jpg'
        list fas_custom_images_list 'banner3_jpg=https://raw.githubusercontent.com/openNDS/openNDS/v9.5.0/resources/bannerseawolf.jpg'
        list fas_custom_variables_list 'input=phone:Phone%20Number:text;postcode:Home%20Post%20Code:text'
        list fas_custom_parameters_list 'logo_message=openNDS:%20Perfect%20on%20OpenWrt!'
        list fas_custom_parameters_list 'banner1_message=BlueWave%20-%20Wireless%20Network%20Specialists'
        list fas_custom_parameters_list 'banner2_message=HMS%20Pickle'
        list fas_custom_parameters_list 'banner3_message=SeaWolf%20Cruiser%20Racer'
        list fas_custom_files_list 'advert1_htm=https://raw.githubusercontent.com/openNDS/openNDS/v9.5.0/resources/bannerpickle.htm'

        option faskey '0962fb0237087f2ce380d3baf98631932d5a1b221aff4e8e384b76153b6860ef'

Untitled

Has anyone else encountered this issue, or does anyone have suggestions on what I might try to resolve it? Thank you very much for your help!

And what is in page sources about those images?

I know nothing about opennds, but isn't it by any chance a catch-22 ?

You're trying to display pictures hosted on internet, in a captive portal, where the user hasn't got internet access, yet ?

Thank you for your response! You've highlighted a potential issue. However, these images and other resources are actually designed to be displayed on the splash page before users complete authentication. My intention is to provide a visually appealing interface before users log in.

These images should be accessible before internet access is blocked, typically through setting up a walled garden. This involves configuring network facilities to allow access to specific external resources without full internet access.

The "Unsupported protocol" error I encountered might indicate a problem in how I've configured the URLs or access permissions for these resources. If you have any suggestions on how to correctly configure these resources to ensure they are accessible even before authentication, I would greatly appreciate it.

Designed and accessible are two different things...

Have you done this ?

@bluewavenet might, but I'm sure it's all in the https://opennds.readthedocs.io/en/stable/

Another options is obviously to store the files on the opennds host.

You found a bug!
It seems that when v10 was first released, openNDS stopped parsing the custom files list in the config, so as a result it does not know the url of the image(s).

This is an easy fix and will be incorporated into the next release due in the next week or so.

This functionality is clearly not used very often otherwise someone will have noticed by now.....

There are many other ways to customise the splash page sequence, but this way is ideal for pulling in banner advertising, for example where a different image is displayed from a remote banner server every time. Same can be done for text....

What actually happens (or is supposed to happen) is the router downloads the image and or text/html file then serves to the client, so the client does not need to have access to the remote server at all.

1 Like

Thank you very much for your prompt response and the upcoming fix! It’s very reassuring to know that this issue will be addressed in next week's update.

Thanks again for your support and effort, looking forward to the new release!

If you have any questions or difficulties it is often more direct to open an issue on Github:

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.