We ran into this issue on a multi-homed Intel Linux box running Samba months
about a year ago when we upgraded the server.  In our case, we had to set
the value for rp_filter to zero.  You can read more about this change here:
http://ifup.org/2011/02/03/reverse-path-filter-rp_filter-by-example/

Aria

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
Michael O'Reilly
Sent: Friday, April 13, 2012 4:28 PM
To: [email protected]
Subject: Re: Linux router


Martha,

 If your SLES11 is SP1 and if, when you receive a ping, you see the RX
count tick up, while the TX count remains the same, you might want to
consider: Applying SLES 11 SP 1 Causing Communication Issues at
http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=
7007649&sliceId=1&docTypeID=DT_TID_1_1


 ________________________

 Mike O'Reilly
 IBM Linux Change Team



















             Martha McConaghy
             <[email protected]
             du>                                                        To
             Sent by: Linux on         [email protected],
             390 Port                                                   cc
             <[email protected]
             ist.edu>                                              Subject
                                       Linux router

             04/13/2012 11:52
             AM


             Please respond to
             Linux on 390 Port
             <[email protected]
                 ist.edu>






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/


----------------------------------------------------------------------
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/

----------------------------------------------------------------------
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/

Reply via email to