> 208.226.220.0/30 (Unusable, all 0's and 1's)
> 208.226.220.252/30 (Unusable, all 0's and 1's)
Welcome to CIDR. The restrictions of not using first or last subnets are
no longer applicable unless you have old broken hardware on your
network...but that's not the issue.
> From anywhere I can ping 208.226.220.135 (255.255.255.192) but I can't
> connect to port 80 from anywhere (including the server it's aliased on).
> One potentially important note here. If I ping one of the other aliased
> IP's from the server itself it answers with the IP:
I can ping 208.226.220.135, but can't traceroute to it or connect to any
tcp port there. It would be interesting to see the following:
output of 'route -n' on the system with the aliases problem. Output of
ifconfig on same system. Note...if you have more than about 30 aliases,
you will need to either issue ifconfig manually for each device beyond the
first 30, or use a hacked ifconfig that uses a bigger buffer. Output of
ipfwadm -lIn, -lFn, -lOn if you use any IP firewalling on that system.
Output of 'show ip route' on the [cisco] router at 208.226.220.34. That's
the last responding hop in traceroute. Output of 'show access-l' on same
router, with notes on which access-lists are applied to which interfaces
in which direction.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or
Network Administrator | drawn and quartered...whichever
Florida Digital Turnpike | is more convenient.
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu