On 04/ 8/10 08:39 PM, [email protected] wrote:
Yes, we do make assumptions of a deafult route. If the machine does not
have a static route as discoverable by 'route get default' or 'netstat
-rn |egrep "^default "' then we will fail to properly setup DHCP with a
router macro at this time.
FWIW 'route get default' doesn't get you the default, but instead looks
up where packets sent to 0.0.0.0 would be sent. Since 0.0.0.0 is really
an old broadcast address, that might return something different than the
default. YMMV.
The netstat approach is more reliable.
However, we will advise the administrator
with the following to try and proceed gracefully:
Unable to determine the proper default router
or gateway for the X.X.X.X subnet. The default
router or gateway for this subnet will need to
be provided later using the following command:
/usr/sbin/dhtadm -M -m X.X.X.X -e Router=<address> -g
We hope to provide a setup automatically for the administrator but I
don't know how we can provide a more automated solution for unusual
routing configurations, such as for a multi-homed system ignorant of
some of its networks' default routes. As such, I believe such a solution
as we do today for advising how to add the router macro is the best way.
Unless, there are some ideas on how we can provide this information for
the user along the lines of the 80%/20% rule or better?
My point was that on a multihomed system that has a default route out
each interface the above netstat | egrep more or less works. Just add a
grep for the interface name.
In general you could look for a good route using
netstat -rn | grep G | awk '{print $2}' | sort -u
And then feeding the resulting gateway address into
route get $gw -ifp $if
You might want to rank the above gateway addresses to look for default
routes first.
That works on single-home and on multi-homed systems.
Correct. The admin just wants to say "let this MAC address (or client
ID) get an IP address assigned based on the interface on which you
hear the DHCP packets".
That is my hope for automatic setup. The administrator need not provide
any information to create the client and as long as they have properly
setup their network infrastructure (minimum networking information in
DHCP -- router; DNS server, if desired) then the client should just work.
If so, that is envisioned to be handled by a nifty feature of the
Solaris DHCP server. The administrator will be advised to create a macro
on the server keyed off the client ID (MAC address). However, macros are
served off any interface the server is configured for. Lastly, the
server will overlay macros, so the client will get data such as router
and boot server from the particular network macro and then get the boot
file info it needs out of its client specific macro.
OK
You said above that the "IP addresses will need to be filled in by the
admin", and it seems that wouldn't be needed in the above case.
Can you explain in what cases the admin would have to fill in the IP
addresses?
The IP addresses necessary for the administrator to provide would only
be router addresses.
OK, and I think you can avoid that as above.
Erik
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
