Re: rump oddity

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Fri, 12 May 2017 17:25:15 +0100
    From:        Patrick Welche <prlw1%cam.ac.uk@localhost>
    Message-ID:  <20170512162515.GB14949@quartz>

  | The puzzle is: while sitting at 192.168.1.2, why can I ping 192.168.2.2
  | but not 192.168.2.1?

I suspect you may be missing (in the export RUMP_SERVER=$sock_gw block)
something equivalent to
	rump.sysctl -w net.inet.ip.forwarding=1
(add -q if you like.)  (I don't know if there is a rump.sysctl, but there
must be a mechanism to allow that to be done...)

And while the little diagram you drew might be a logical descr of what
you're configuring, I think a more accurate one would be:

#
#    ===================================================================
#           |                        |                         |
#           |           +---------------------------+          |
#  int 192.168.1.2      + 192.168.1.1  192.168.2.1  +     ext 192.168.2.2
#                       |            gw             |
#                       +---------------------------+

gw would need to be configured with shmif0 & shmif1 to accurately
model the original diagram.   Not that this should really matter
to the test you tried.

kre