> What I don't quite see at the moment: how do I *prevent* the z/os- LPAR > from choosing the "usual" way > (of being routed): is it by defining a static route for the hipersocket > interface in the Profile-dataset? BSDROUTINGPARMS or BEGINROUTES or > whatever?
Yes. See the paper I posted last night for an example and a diagram. If the z/OS IP stack has a more specific route for the destination address range on the other side of the hipersocket link, it will route packets destined for those addresses via the hipersocket link. The other packets will fall through to the default route and be sent the ordinary way. > AND: how and where do I do the corresponding thing for the Linux LPAR? You do this with the route command, eg: route add net a.b.c.d netmask n.n.n.n gw p.d.q.r where p.d.q.r is the ip address of the next hop. Linux will take care of making this persistent. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
