My situation really is quite simple. I've got a network which is 10.xxx.xxx.xxx.xxx. Let's use 10.2.12.xxx as my home address. I also have an internal hipersockets address of 192.0.1.xxx. This is the configuration for all the images.
As an example (a very good one), if I start a batch FTP to 10.17.252.62, I get a "connection failed to respond" timeout. If I use the GATEWAY statements, I do not have this problem. And thanks for the help. On Sat, 14 Oct 2006 17:54:40 +0200, Chris Mason <[EMAIL PROTECTED]> wrote: >Matthew > >Sorry for the delay, I'm cleaning up posts to which I intended to reply. > >It may work but it won't necessarily work well. > >When packets are destined beyond the adjacent (gateway) router, all is = >well. However, if packets are destined for another node on the same = >LAN/subnetwork as the OSA feature and the adjacent router, they will go = >first to the adjacent router and then to their destination, two "hops" = >where one suffices. The adjacent router will see that a better route = >exists and will potentially update your routing table using an ICMP = >redirect. Thus you should see a single "host" routing entry for each = >such destination. You may have no such destinations so it won't be an = >issue. Of course, you can prevent ICMP redirects packets from adding = >entries to your routing table. If you do that, you will continue with = >the inefficiency of having the same packets sent twice over the same LAN = >outbound.=20 > >I had something of a frown when I saw Steve's technique. More usual is = >to replace his "Where's the gateway?" entry with a subnetwork route. = >However, Steve can be excused I suppose because you didn't give = >sufficient information. We need to know the subnetwork mask for the LAN = >to which the OSA feature is attached and the remainder of the IP address = >for that subnetwork. If we assume that it is 255.255.255.0 or /24 in = >terms of the way a ROUTE entry is defined, that the IP address of the = >subnetwork is 10.1.1.0 and that the IP address of the adjacent router is = >10.1.1.254, Steve's example becomes the following: > > BEGINROUTES >; All hypersocket traffic - Use your interface, not HIPERLF6 > ROUTE 192.10.1.0/24 =3D HIPERLF6 MTU 8192 >; Where is the gateway? > ROUTE 10.1.1.0/24 =3D ETH1 MTU 8192 >; All other traffic defaults here > ROUTE DEFAULT 10.1.1.254 ETH1 MTU 8192 > ENDROUTES > >I've also set the "jumbo" frame size MTU throughout on the assumption = >you have Gigabit Ethernet and that you have Path MTU discovery active - = >and, preferably, respected by the other routers in your network. > >Incidentally John McKown's templates fall down a bit on syntax as you = >can probably see. Also under "gateway_ipaddr" in section 1.2.9, = >"BEGINROUTES" in z/OS V1R8.0 Communications Server IP Configuration = >Reference you will find the sentence "The equal sign is not supported = >for DEFAULT or DEFAULT6 route entry.". This means that Steve's "Where's = >the gateway" ROUTE statement is always required and that, minimally, = >there is the then just a need for a DEFAULT ROUTE statement, that is, = >minimally there must be two ROUTE statements in order to be able to = >specify a DEFAULT ROUTE statement. > >Chris Mason > >Previous posts in the thread: > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
