Evan Layton wrote: > Hi Sundar, > > Looking at what we're doing in setup-dhcp.sh and how the dhcp server > needs to be set up it appears that in order to create the proper macro > we have to have the default router for that subnet we are attempting to > configure. However if the subnet we're are attempting to configure is > not the same as the default router on the server we have no way to > determine the router for that subnet. > > Based on this I've found no way to do any kind of automated > configuration of all the subnets on the system. The best I can think of > to do for this bug is to print out a message telling the user that we > found other subnets and if they wish to configure those for dhco they > will have to do it manually. We can generate at least part of the macro > needed however since we need to default router for the subnet to do this > we can only give an example and not a fully functional command. > > Does anyone have any ideas on another way to handle this or to gather > the default router for all the subnets on the server? >
Well, strictly speaking a router (default or otherwise) is only required if you need to communicate with systems which are not on your local link. If the install server is connected to the link, then installation should work just fine without any router being configured. Thus I'm not sure what problem you're concerned about here? Dave
