Hi, Martha, -- Maybe set the default route on the "inside" guests? But also, with OSA, you may need to tickle it into playing nice. Alan would know more, but am guessing you either need to explicitly set it to allow forwarding (which PRIROUTER may affect) or run it in layer 2 mode.
I've used Linux as a router for years. Until a hardware failure about 18 months ago, a Linux box served as my primary router/gateway on the home network. Never heard of anything quite like PRIROUTER per se. But ... all parties had to know about the routes. The "outside" guys needed to know to get to that subnet via the external addr of the Linux box. The "inside" guys needed to know that their default route was by way of the internal addr of the Linux box. As it happens, I still use a Linux box as a primary router. Since my ISP does not yet provide native IPv6, I use a tunnel for IPv6. The details are a little different, but the concept is the same. Outside world knows the path into my subnet. Machines on my subnet know to use the internal addr of that host as their default route. I hope this helps. -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ On Fri, Apr 13, 2012 at 2:52 PM, Martha McConaghy <[email protected]> wrote: > I've been working on setting up a zLinux (SLES 11) system to act as a router > between two networks (its on an ensemble, but that doesn't really matter at > the moment). Everything is set up within Linux (yes, I have IP routing turned > on) and the real network has been updated to have a static route to this > system. Pings are successful to the main IP address on the adapter (on a > vswitch connected to a 1000BaseT OSA). Pings are also successful from the > other adapter as well. > > However, when we try to ping the adapter on the far side of the router from > the network, the packets make it as far as the OSA and then drop. Our TCPIP > routing guru, Alan Altmark, reminded me that the PRIROUTER setting has to be > turned on in the vswitch for the OSA to recognize that it will be routing > other traffic through it. I've got that set now, but am still seeing the > problem. > > If this were a VM TCPIP machine, I would have to also set PRIROUTER on the > DEVICE statement to get this to work (I'm tempted to switch over to this if I > can't get it working). Is there an equivelent setting for qeth? I've been > googling around, but haven't found anything. > > Martha > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
