Keep in mind: a hipersocket and a OSA are NOT the same beast -- they
both use QDIO to deliver frames to the media, but the similarity stops
there. Some things just don't work on hipersockets -- for example,
hipersockets don't have that silly PRI/SECROUTER thing, so they *should*
return an error when you try to set it.
> Any further thoughts? Has anyone sucessfully done something similar,
> or even the Hipersocket Network Concentrator (since the qeth driver
> won't take the commands from the book)?
Let's try the simpler approach before you try to get fancy.
If both interfaces are functioning independently, then you should need
only to turn kernel IP forwarding on. You do need to make sure hosts on
both sides of the router have either a) a static route specifying that
the subnet on the other side of the Linux guest is reachable via the
Linux guest interface connected to that segment, or b) a dynamic routing
protocol that can allow them to discover this fact.
Even for something as basic as ICMP/ping, you still have to follow the
basic rules for IP routing and have next hop routes at each point along
the way, eg if your network looks like this:
A----> B (linux router) C----> D
Where A is your z/OS LPAR attached to the real hipersocket
B is the hipersocket interface of the Linux router
C is the guest lan interface of the Linux router
D is the guest attached to the guest lan
At host A, you need two routes:
192.168.11.129-255 via B
0.0.0.0 (default) via your default router (for everything else.
The linux router does not need routes (both networks are directly
connected. If IP forwarding is enabled, packets will flow.
Host D needs two routes:
192.168.11.0-128 via C
0.0.0.0 (default) via the normal default router for everything else)
A and D have no way to dynamically discover this configuration without a
routing protocol on A, B/C and D. What do your routing tables on A and D
show (eg, what's the output of NETSTAT on both?
----------------------------------------------------------------------
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
