Funny you should mention that...

We just noticed in the past week that we've had a user (to remain
nameless... ) which has been dialing into our WAN (RAS) and has his PC setup
with a dual network and apparently has enabled routing.

Apparently every time he dials in, his dialin (dynamically assigned) IP
address gets added to the 3000 as a default gateway!!! With "0" hops no
less!!! Which very shortly causes all other remote connectivity to fail!

I'll be talking to that user.. but in the meantime this new "feature" is
ANNOYING! And destructive... Especially considering NMMGR won't let you add
a gateway with less than "1" in the hop count... so that "0" entry takes
over! We're having to disable the route manually whenever it happens..
usually after users start calling and asking why they can't get to the
system from our remote offices. :-(

 -Chris Bartram


                -----Original Message-----
                From:   Patrick Santucci [mailto:[log in to unmask]]
                Sent:   Wednesday, June 20, 2001 1:17 PM
                To:     [log in to unmask]
                Subject:        [HP3000-L] Network Gateway Redirects

                I have another question for you network gurus. :-)

                Is there any way to tell our 3000 to ignore gateway redirect
messages? We
                have two routers, one for our WAN and one for the Internet.
Only the WAN
                router is configured on our HP3000 systems.

                When our WAN router (172.18.0.20) loses connectivity with
the router at the
                other end of the connection, it tries to reroute the packets
through the
                Internet router (172.18.1.80). At the same time, it sends a
"gateway
                redirect" message to the system the packets originated from,
telling the
                3000 to send future requests bound for that destination to
the 1.80 router.
                Since these packets should *only* be going over the WAN
router, this is
                *incorrect*. However, the HP system doesn't know that and
happily complies
                with the request. This happens even though the 1.80 router
is *not*
                configured on the HP system at all... It just suddenly
appears, as can be
                seen in NETTOOL when I do a GATELIST:

                [3]NAMEADDR.ROUTING>>>gatel
                    Network address filter: @
                    Gateway address filter: @

                Gateway IP        Hops     Flags    Active    Default
Gateway

______________________________________________________________
                172.18.0.20        21       0          y           y
                172.18.1.80         0       0          y           n

______________________________________________________________

                Total number of gateways = 2
                [4]NAMEADDR.ROUTING>>>

                When the connection is again established over the 0.20 (WAN)
router, there
                is *no* redirect message sent telling the HP system to send
its packets over
                the WAN router, and I have to manually disable the 1.80
router by doing
                GATEDOWN 172.18.1.80 in NETTOOL in order to reestablish a
connection.



* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *