> 206.190.23.192 27 206.190.23.216 local NL 1 ether0
> 0.0.0.0 0 209.190.23.193 local NS 1 Unknown
^
/|\
|
This one looks like a typo. You told the PM3 to set the default
route to 209.190.23.193 but didn't give it a route to that
address. I think that this should be 206.190.23.193 instead.
Since that is a directly connected network the PM3 can find it.
As for fixing, if I am right in you wanting to use a default
route of 206.190.23.193, use set gateway 206.190.23.193.
> 2. I recently delagated a block of 24IPs off of our subnet to a colo
> machine running its own primary and secondary DNS. The customer cannot
> ping the IPs that I have delagated. As a matter of fact the pinging of
Are the IP's actually in use? You can delegate a block of IP's
but unless there is an interface to respond to pings you won't
get anything back.
> IPs on our subnet problem starts at the address that the new PM3 is on.
You lost me on this last sentance. It may just be lack of
caffeine thought. :)
> These problems could be related? I am stumped and really need some help.
The first one looks like a typo. The second not sure.
Michael
----------------------------------------------------------------------------
Michael J. Hartwick, VE3SLQ
Prime-Line Communications
hartwick@primeline.net
-
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/>