MDK wrote: > Yes, for some reason, star-os routes private ip's toward whatever your > default route is. GAAK! > This is normal behavior for most (maybe even all) routers, provided that there isn't an access list or firewall rules in place to prevent this. There are plenty of legitimate reasons to route these IPs. They are non-Internet routeable, not non-routable.
> To trap these, just put those IP's on a dead end, like attach those networks > to an ethernet port on your ap's or something, and they die there. You DO > route at the AP, right? > You can do that or you can null-route these addresses. I don't know how this works in StarOS; Many times, if there isn't a null interface or an explicit null-route option people will just add a route for those networks using an unused IP address as the gateway. Routing to localhost might be dangerous as the router may keep forwarding the packets (to itself) until the TTL expires. This could unnecessarily increase load on the router and degrade performance. Hope this helps, Charles -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
