apache vhosts dhcp ip addresses

[KAD]

so I'll probably have a beta firmware posted up in the next few days

but since I have a few momments, some questions
that if nothing else might make some interesting discussion

I've implemented httpd-vhosts.conf in apache config, so that both wdlxtv-webend and official wd-webend can run at the same time

so I've got a couple of choices to make here
1. use name based addresses on vhosts.conf
- the problem with this is the webend has never run on name based, and after several quick test I was unable to get name based vhosts to work
- if I was to implement this, what would it take or is it worth while, I'd have to somehow report dns names to the dns server on the network (usually a router)
- addresses would look something like wdlxtv-webend.com & wd-webend.com

2. we can use IP based addresses in vhosts.conf
- this actually works quite well but presents some different issues
a. we have to get the WD's IP address into vhosts.conf at boot time and restart apache - done
b. we need to obtain a 2nd IP address and get that into vhosts
-1. preferably we would just get this via dhcp, so we are guaranteed not to create IP conflict on the network - but I don't know how to do this
-2. I can use nmap to get an IP list and iterate over it, and then randomly select an IP in the range that is not used - not implemented yet, but possible
-3. we can force users to manually add an IP on the wdlxtv webend, before we make the official webend available - for now this is in place

but your thoughts/opinions about a setup like this

initially testing shows the final option of 2.b.3 having users input the address manually seems to work ok
but functionality and features of the official webend of coarse are not available until a users do so

[mad_ady]

[KAD]

actually problem 3 is also a problem with having the user manually assign an IP address
we have to know if we're using eth0 or wlan0
but that wasn't that difficult
ifconfig will list the interfaces
but only the active interface will have an IP address so a few cut's and grep and we can check if the interface has an IP address or not
and then create eth0:0 or wlan0:0 on whichever interface already has an IP address

just a couple other random thoughts
why doesn't it work to just add the wd-webend as a plugin to wdlxtv-webend
the way wd-webend was written require the scripts to be run from an address like this http://192.168.1.25
if we try to run it from http://192.168.1.25/wd or anything similiar the path is not the same
and functionality is broken as it can't locate the correct scripts needed, so really the only option to run both is using vhosts

and this is also this reason that alias option for apache does not work as well

[mad_ady]

Hmm, about the webend, you'd have to ask RMerlin. However, even if you manage to fix it easily, it's possible that some other scripts have hardcoded values that point to http://$ip/path (e.g. umsp).

[KAD]