Tiny Core Extensions > TCE Talk
syslinux upgrade for tc4.7.x?
genec:
That sounds rather odd (not being able to disable auth). I can't say I've ever heard of such a thing. It'd be EXTREMELY suspicious to see an HTTP 401 on public sites. Most httpds that I've seen are configurable. Consider the HTTP status code definitions. 4xx are client failure errors where a repeated request won't change anything, unless the request is "corrected" or access on the server is changed. Adding/changing authentication information is a "correction" in this context.
Not sure what you're asking about pausing since your httpd returns 401 and PXELINUX's HTTP client likely treats it the same as a 404.
To my knowledge, correct. There is no directive for it. I also doubt that inserting username/password into the URL the standard manner will do anything but return a complete failure. I'll try to see if I can get a quick test set up.
You can easily use gPXE/iPXE to provide HTTP access instead of using lpxelinux.0 and it could do authentication.
genec:
And inserting the authentication information into the URL is parsed but the username/password isn't used ie http://user:password@192.168.4.1/auth/menu.c32.
gmc:
--- Quote from: genec on June 15, 2013, 07:36:29 AM ---That sounds rather odd (not being able to disable auth). I can't say I've ever heard of such a thing.
--- End quote ---
The NSLU2 is rather limited in what it allows the end user to configure. It insists on asking for a user name/password for any access. Failed logongs are supposed to default to the "guest" account.
--- Quote ---Not sure what you're asking about pausing since your httpd returns 401 and PXELINUX's HTTP client likely treats it the same as a 404.
--- End quote ---
At the PXE boot menu, when I select an entry from the menu and press Enter, I need to see the response/error message before PXE returns to the menu (assuming a boot failure occures, which it does when trying an http boot). As it is, I see just the briefest flash of a message and then it is gone and the menu is active again.
--- Quote ---To my knowledge, correct. There is no directive for it. I also doubt that inserting username/password into the URL the standard manner will do anything but return a complete failure. I'll try to see if I can get a quick test set up.
--- End quote ---
I appreciate that.
--- Quote ---You can easily use gPXE/iPXE to provide HTTP access instead of using lpxelinux.0 and it could do authentication.
--- End quote ---
I am currently trying that. So far I just replaced lpxelinux.0 with undionly.kpxe (in udhcpd.conf) per the ipxe setup instructions. I get the ipxe boot screen and can Ctrl-b to break out of the endless loop (again, per the instructions). I have not gotten any further yet, still reading. I was hoping that it would run the 'default' menu by default but it looks like I have to do some more configuration to get to that point.
gmc:
--- Quote from: genec on June 15, 2013, 08:42:24 AM ---And inserting the authentication information into the URL is parsed but the username/password isn't used ie http://user:password@192.168.4.1/auth/menu.c32.
--- End quote ---
That was the syntax I was needing. I tried it. You were right, it did not work. Back to trying to set up ipxe...
tinypoodle:
--- Quote from: gmc on June 16, 2013, 01:35:39 AM ---The NSLU2 is rather limited in what it allows the end user to configure.
--- End quote ---
It would appear like many have improved that:
http://www.nslu2-linux.org/
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version