THanks to all that responded. The problem was routing.

Thomas L. Geyer
Email:[EMAIL PROTECTED]
Phone:(330) 471-2073
Fax:(330) 471-4034


-----Original Message-----
From: Alan Altmark [mailto:Alan_Altmark@;us.ibm.com]
Sent: Thursday, November 14, 2002 11:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Problems loading qeth for a Guest Lan


On Thursday, 11/14/2002 at 10:57 EST, "Geyer, Thomas L."
<[EMAIL PROTECTED]> wrote:
> I am attempting to setup a Guest Lan on zVM 4.3 on a z800. I have one
Linux
> machine, lnxrtr1, up and running with a CTC connection to the zVM TCPIP
> virtual machine. My goal is to have the lnxrtr1 linux machine act be a
> router for my Guest Lan. I am now trying to get lnxrtr1 to communicate
to
> the Guest Lan. I have defined the LAN as follows:
[snip]
> I have used presentations from Share, presentations from IBM's zVM/zOS
> Technical Conference, IBM's Large Scale Linux Deployment Redbook and the
> Device Drivers and Installation Commands Manual as reference in this
effort.
>
> If anyone can see what I did wrong please let me know, I have been
fighing
> this for days. Your help is greatly appreciated. I apologize for the
length
> of this email.

Routing, son, routing.  Look carefully at the subnet mask of eth1:

eth1      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:147.185.179.65  Mask:255.255.0.0

All of your real network LAN traffic that was previously being bounced
back through the CTC connection is now flowing into the virtual bit
bucket.  Fix up the subnet mask (255.255.255.128?) and all will be well
(he said hopefully).

Alan Altmark
Sr. Software Engineer
IBM z/VM Development


**********************************************************************
This message and any attachments are intended for the
individual or entity named above. If you are not the intended
recipient, please do not forward, copy, print, use or disclose this
communication to others; also please notify the sender by
replying to this message, and then delete it from your system.

The Timken Company
**********************************************************************

Reply via email to