Same basic concept.
Create location.
Set for dial on demand.
Set dest IP to 255.255.255.255
This should create a PTP interface in a Suspended state.
Now for the big addition:
Modify the 'add route' command so that it can be in the 'normal' format:
add route dest/nm gateway metric
or this new format:
add route dest/nm location locname metric
If it sees the key 'location' (or 'loc' I'd hope) after the dest/nm, then
it should read that as being a location table entry. The route would GW via
that PTP interface. When traffic for that dest/nm tuple arrives, it should
kick off the dial.
The specific 'set gateway location locname' is just shorthand for
add route 0.0.0.0/0 location locname 1
This addition would allow locations to do dial on demand to destinations
with varying IP addresses, both for single exit point default routes and
individual route entries.
This could even lead to interface routing capabilities in ComOS. Perhaps
even this is just shorthand for something like
add route dest/nm ptp# metric
Which is an even more general case, and would allow interface based routing
similar to Cisco. Using a location is nice for the humans and would just
look up that locations PTP interface number.
-MZ
-- -=*X I'm going down... under that is! <URL:http://www.aussie-isp.net/> X*=- <URL:mailto:megazone@megazone.org> Gweep, Discordian, Author, Engineer, me.. Join ISP/C Internet Service Providers' Consortium <URL:http://www.ispc.org/> "A little nonsense now and then, is relished by the wisest men" 781-788-0130 <URL:http://www.megazone.org/> <URL:http://www.gweep.net/> Hail Discordia! - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>