Well I was pretty certain that I had tried switching the PRIROUTER - NONROUTER previously. But that was also before I had turned off the rp_filter. A college suggested changing the internal network vswitch to a hipersocket connection. So with the vswitch for the internal network replaced with hipersockets, and PRIROUTER set on the external network vswitch I can route just fine.
Thanks very much for all the hints and tips. On Thu, Jun 7, 2012 at 3:23 PM, Mark Post <[email protected]> wrote: > >>> On 6/7/2012 at 09:43 AM, Mark Pace <[email protected]> wrote: > > [ vswitch - prirouter] > > . > > . > > [guest2 - eth1 - 172.16.1.1/24] > > [guest2 - eth0 - 199.xx.xx.xx/25 - GW - 199.xx.xx.1] > > . > > . > > [vswitch - nonrouter] Connected to OSA connected to the internet. > > I think you have the nonrouter prirouter attributes reversed. The virtual > router needs to pick up addresses that wouldn't normally be otherwise > delivered to it: the 172.16.1.0/24 subnet. > > > Mark Post > > ---------------------------------------------------------------------- > 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/ > -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems ---------------------------------------------------------------------- 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/
