Re: Hercules networking redux

Sorry, I’m running Hercules-390/Hyperion V4.0.0.0 which I got from GitHub. My MacOS level is Mojave 10.14.5. I got tun/tap from tuntaposx.sourceforge.net <http://tuntaposx.sourceforge.net/> and while I can’t say what version I have, it’s likely I got it in 2014/5.

I can’t ping in either direction: into z/OS or out of it. Pinging is usually my first test and it fails in this context. With regards to your advice, how exactly would I go about getting it working. I’m happy to read whatever docs I need to, but as you no doubt know, IBM has a boatload of them and it is difficult to know where to start.

So perhaps what I’ll do is update my version of Hercules as you intimate in your post and go from there.

Thanks

John Murray

Ottawa

> On 14 Jun 2019, at 16:03, Harold Grovesteen [email protected] [hercules-390] <[email protected]> wrote:
> 
> On Fri, 2019-06-14 at 13:02 -0400, John Murray [email protected] <mailto:[email protected]>
> [hercules-390] wrote:
> 
> > 
> > 
> > Thanks for that. Yes, I made the TCPIP profile changes suggested
> > earlier and indeed, they didn’t work. Now the thing of all this is,
> > I’m running Hercules on a Mac (hence MACOS) which, under the covers,
> > is Unix. But most of the responses I’ve received for this problem are
> > set in a Linux context and, as we all know, Linux is not Unix, so the
> > question I have is really, what should I be doing for MACOS?
> > 
> > Thanks as always.
> > 
> > 
> > John Murray
> > 
> > Ottawa
> > 
> 
> For the record, you should probably ensure the list knows the version
> of Hercules you are using, from where you downloaded it, and what is
> your Mac OS level.  If you separately installed the TUN/TAP driver,
> what is its release level?
> 
> Notice, I did not provide any commands.  My personal experience is
> primarily with Linux, and, as a network architect, I have a grounding
> in network design principles.  That helps a lot.  That is what most
> lack in experience and where troubles begin.  These are mostly
> independent of the software, although one needs to understand the
> software to ensure the networking design is consistent with the
> software.
> 
> I have made the assumption that the TUN/TAP drivers on MAC and Linux
> are logically the same even if the details are different.  This may not
> be valid.
> 
> First things first...
> 
> Can you ping in both directions from your Hercules guest to your
> Hercules host systems with your original IP settings?  If that is not
> working, ping'ing to your router will certainly not. In general get
> that working, then move to outside of the Hercules host.  This is true
> regardless of your host OS.
> 
> If that works, you still need to enable proxy ARP in the Ethernet
> interface.  How to do that on a MAC is beyond my personal experience.
>  Google may be your friend there.
> 
> For MAC commands, you really need someone with actual MAC experience.
>  There was also a period when TUN/TAP had issues on OS/X.  So you
> really need someone with MAC experience there, too.
> 
> MAC introduces a lot of variables that are less familiar.  If the
> simple things I suggested do not work (assuming you can enable them),
> looking at the version and release of Hercules and the MAC itself may
> be of some help.  A lot of work was done in the Hyperion version of
> Hercules for MAC's in the new build process.  Steve Orso has some
> experience there.
> 
> Before going off the deep end and changing things that may not need it
> at all, validate Guest/Host interactions.  If that works, enable Proxy
> ARP otherwise get it to work and then try with Proxy ARP your router.
> 
> Get the router pings to work first.  After that, if needed, the MTU's
> can be addressed.
> 
> Harold Grovesteen
> 
> 
>