Thanks for verifying that. So here is what I'm currently seeing. During the install I can see the Linux installer pinging my nfs server and it replys back but never reaches my Suse VM. I put a static route in the nfs server to point to the VM4.3 machine for the IP of the Suse install. This didn't help. All of these machines are in the same subnet (suse install, nfs server, and VM4.3). It looks to me that VM might not be passing it to the Suse install.
Thanks >>> [EMAIL PROTECTED] 9/17/2004 10:32:53 AM >>> On Fri, 2004-09-17 at 08:34, Doug Griswold wrote: > I have one more question. In a ctc connection when going through the > install the "Peer IP Address" is the address of the VM instance? Yes. > Also > how do I get out of the mainframe if this is a point to point > connection? Does VM have to route me out to the default gateway? Yes. And this is probably your problem. VM is likely to already be routing you out, but whatever is upstream of VM in the network doesn't know that to get to your address it has to go through VM. Either your network guys will have to configure a static route, or they will have to accept dynamic routing updates from VM and VM will have to announce the route to your Linux guest. The CTC itself is (from the Linux perspective) simply a point-to-point IP link; think of it like dialup PPP if you like. If you're running z/VM 4.2 with recent service or anything later, you probably want to use Guest LANs instead, as they're a lot more like just working with an Ethernet adapter. Adam ---------------------------------------------------------------------- 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 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
