Chet Luther wrote:

I've snipped the irrelevant portions of that output out. Do you know
why your routing is setup this way? It looks like your interface is
setup with an IP of 10.200.0.1 and a netmask of 255.255.255.255, then
specific host routes (netmask 255.255.255.255) were added for every
single host on that subnet.

Here is the config of the interface.  It is using the suggested netmask.

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet 10.200.0.1 netmask 0xffffff00 broadcast 10.200.0.255
        ether 00:30:48:2b:2b:b6
        media: Ethernet autoselect (1000baseTX <full-duplex>)
        status: active

I don't presume to know how your network is setup, but off the top of
my head I can't understand why this would be necessary. Maybe you
could just set the netmask on that interface to 255.255.255.0 and
delete all of those host specific routes?

Here are the routing tables for the interface in question. The odd thing I see is the first entry. None of my other boxes have that entry. Have you seen that before?

admin01% netstat -nr
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
...
10.200.0.0         ff:ff:ff:ff:ff:ff  UHLWb       1       14    em0 =>
10.200/24          link#1             UC          0        0    em0
...

Thanks,
Calvin

--
S i x  F e e t  U p , I n c .  |  "Nowhere to go but open source"
Silicon Valley: +1 (650) 401-8579 x602
Midwest: +1 (317) 861-5948 x602
Toll-Free: 1-866-SIX-FEET
mailto:[EMAIL PROTECTED]
http://www.sixfeetup.com  |  Zope/Plone Custom Development

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to