On Apr 4, 2008, at 11:43 AM, Mark Hamzy wrote:
> On Fri, 2008-04-04 at 09:45 -0500, Mark Hamzy wrote:
> > I've been asked to look into calculating at least something to
fill in
> > for an initial stab at a gateway address. I know you can't
determine
> > what the real router's address is. But you could get the user at
least
> close. What do y'all think about that in general?
> We used to do it, you're always wrong about half the time. Some
people
> use the first, some use the last. It's just not something that
you can
> guess.
Okay, I can understand that. How about in the case where there is
just one interface defined? For example, given an IP address of
9.53.40.25 and a netmask of 255.255.255.0, how about filling in just
"9.53.40."? That way, the user has to complete the gateway IP
address or they will receive an error dialog.
This assumes they will have a gateway. There are users who are
working on a gateway-less LAN and are doing a network install.
Forcing them to enter this information would break their network
configuration.
This affects only a limited part of the networking configuration in
anaconda. It's only IPv4, only deals with one interface, and only
occurs when users do manual interface configuration. I would prefer
not to autofill the gateway field even in this case, because then
people will start asking to autofill DNS and such (which happened at
one point, but it was cut too).
The minimal required information users should have in front of them
when manually configuring IPv4 is:
IPv4 address
prefix or network mask
Gateway is optional, DNS is optional. Broadcast and network addresses
are calculated for IPv4.
Rather than autofilling entry fields, can we improve the text
presented to the user when we are asking for these values?
--
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list