A light comes glimmering through. If your supposition is correct, then
above.net and ORBS aren't communicating very well. Given your assumption
that above.net does not want to see 10.1.1.* scanned by ORBS, we would hope
that above.net would have TOLD ORBS "hey, leave 10.1.1.* alone! But the
rest of the address space is fair play."
After all, the static space is set by the request of the address owners, if
I'm reading all the info correctly.
So did above.net say 10.1.1.*, or 10.*.*.*? If the latter, than above.net
is shooting itself in the foot.
(Nothing personal, I'm just the curious type.)
Satch
At 07:33 PM 1/18/00 , David Lang wrote:
>the issue with abovenet is not what you are thinking
>
>If I am understanding it correctly here is the issue (random IP addresses
>used for demonstration)
>
>above.net has 10.x.x.x addresses assigned for them and their customers.
>
>above.net has their own servers running in the 10.1.1.x subnet
>
>above.net blocks scanning of 10.1.1.x but NOT the rest of the 10.x.x.x net
>
>VA linux gets the 10.200.100.x subnet from above.net for their
>servers. (which are configured properly)
>
>VA linux discovers that they are unable to send mail becouse ORBS flags
>the ENTIRE 10.x.x.x range owned by above.net, even though most of it is
>not blocked, and does not contain any open relays.
-====---====---====---====---====---====---====---====---====---====---====-
to unsubscribe email "unsubscribe linux-admin" to [EMAIL PROTECTED]
See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
