On 01/28/10 11:29 AM, James Carlson wrote:
Robert Hartzell wrote:
RTM_ADD: Add Route: len 376, pid: 376, seq 6, errno 0, flags:<GATEWAY,DONE>
locks: inits:<hopcount>
sockaddrs:<DST,GATEWAY,NETMASK,IFP>
24.0.0.0 10.0.0.20 255.0.0.0
At a guess, PID 376 ("ps -fp 376") is in.routed, and the problem is that
your new gateway device is broadcasting garbage over RIP.
You can verify that with snoop or wireshark, and monitoring UDP port 520.
The next question is whether it's sending out that garbage because of
misconfiguration or because it's just inherently bug-ridden. If it's
the former, then fixing the configuration should do it. If it's the
latter, then you'll probably need to disable RIP and rely on static
routes (or discard this new device in favor of one that works).
The device is a Netgear Prosafe vpn Firewall FVS338
I'm pretty sure its misconfiguration on my part.
disabling RIP on the firewall removes the 24.0.0.0 route from the table
but when I try to add default 10.0.0.20 its added but without an
interface listed.
My options for RIP are:
RIP Direction
none
in only
out only
Both
RIP Version
Disabled
RIP-1
RIP-2B
RIP-2M
initially set at Both and RIP-1
Any pointers on what would be appropriate settings?
--
Robert W Hartzell
bear at rwhartzell.net
RwHartzell.Net
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
