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]

That sounds rather odd (not being able to disable auth).  I can't say I've ever heard of such a thing.

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.

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.

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.

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.

I appreciate that.

You can easily use gPXE/iPXE to provide HTTP access instead of using lpxelinux.0 and it could do authentication.

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]

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.

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]

The NSLU2 is rather limited in what it allows the end user to configure.

It would appear like many have improved that:

http://www.nslu2-linux.org/

[gmc]

By the way, how do I stop/restart udhcpd?  I have tried stop, start, and restart with what I believe is the correct path, but there is no indication that anything happens, not even an error message.

[gmc]

The NSLU2 is rather limited in what it allows the end user to configure.

It would appear like many have improved that:

http://www.nslu2-linux.org/

Yes, and I am very interested in going that route.  In fact, this past Friday I received a second, used, NSLU2 I found on Amazon.  I am researching which firmware would be best for my needs.  But it will take time to get that set up so I am continuing to work on the TCL/PXE boot http issue from both angles.

Thanks for the tip.

[tinypoodle]

By the way, how do I stop/restart udhcpd?  I have tried stop, start, and restart with what I believe is the correct path, but there is no indication that anything happens, not even an error message.

A suggestion would be using 'htop', which lets you kill a selected process while providing realtime feedback.

[Juanito]

Code: [Select]

$ ps aux | grep udhcpc
$ sudo kill xxxx [pid from result of above command]
udhcpc should also create a pid file of the form /var/run/udhcpc.eth1.pid

[gmc]

Thanks guys. 

I gather that the standard stop/start/restart commands don't work in TC?  I thought it was something I was doing wrong.  I especially wanted the restart command so that when I make a change in the config I could test it easily with a restart command.

Thanks for your tips - very helpful.

[genec]

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.

Unrecognized requests with the Authorization header, yes.  Without the header it's a failure with HTTP stastus 401.

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.

Working as intended.  You'd need a ONERROR command specified and COM32 module to pause the screen or try without the menu.

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.

Just like gpxelinux.0/ipxelinux.0: add a script and possibly pxelinux.0.  At that point, try the URL with username/password in the PXELINUX config.

[gmc]

@genec - Very useful information.  I managed to get an http boot to work with ipxelinux.0, thanks.  I'm still hoping to get it working with syslinux but now I have another option to fall back on for the present.  All the tips were what I needed, thanks.

I'm presently trying to get a second NSLU2 I picked up upgraded to openwrt firmware.  That should allow me to have the control needed to work with syslinux http booting.  The reflashing went OK, but I could not get an IP address to the unit.  I off to work on that now...