Gated and OSPF, syslog message

[Phil Gregory_1]

I am getting the following error message on some (but not all) HPUX 10.20.47 clients. All run gated for OSPF with the same generic configuration.

mehp4b4c gated[784]: OSPF RECV 10.150.72.1 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.79.24 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.115.24 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.79.24 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.72.70 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 10.150.72.2 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.72.24 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 10.150.72.2 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.79.2 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.115.9 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.79.9 -> 224.0.0.5: IP: bad destination
mehp4b4c gated[784]: OSPF RECV 194.33.115.9 -> 224.0.0.5: IP: bad destination

The client that logs these messages is on a 194.33.75.0 (255.255.255.0) subnet. Is this message logged soley because it is receiving OSPF braodcasts from different subnets?

Thanks, Phil.

[Alex Glennie]

Phil,

I warn you I know next to nothing about this, however I have found some info ... hopefully you'll receive some replies from some experts in this field soon ?

However ; the errors may well be because of different subnets but there are other causes :

If rip = yes is in the gated config they may be rip routes. Try turning off rip and see if the routes still come in . If not then they are running RIP ... rip is configurable to listen only.

If not then you may need to investigate the error messages further.... hopefully this makes sense , if not feel free to ignore me ;)

[Phil Gregory_1]

Thanks Alex,
I dont run RIP in my network, and I have RIP=no in the gated config.

[Kofi ARTHIABAH]

Phil:

the 224 address in the log indicates multicast address - so you probably want to turn off your MROUTED in your /etc/rc.config.d/netdaemons on that box.

[Phil Gregory_1]

Thanks Kofi,
MROUTED is off on all clients.

The clients are on an Ethernet segment which has a couple of OSPF routers on it. These routers also run a number of token ring subnets, the broadcasts are coming from the token ring interfaces on these routers.