According to page 102 of the book, you use primary_connector to tell the OSA interface you're routing between it an a HiperSocket network. You use multicast_router to tell the HiperSockets the same thing. In the section you're working from, they're doing the opposite. They seem to have a number of examples using the latter method, but I don't know which is correct.
Also, according to Alan's note, to use the HiperSocket Network Concentrator model, the non-z/OS side of the network needs to be a QDIO network, not a HiperSocket network. You say you have real HiperSockets on one side, and a HiperSocket Guest LAN on the other. Finally, going back to your original note, you said that the IP address of the z/OS side of things is 192.168.11.10, with a subnet mask of 255.255.255.0. You then said that you set up the Linux systems with IP addresses of 192.168.11.129-255, and a subnet mask of 255.255.255.128. This appears to violate basic IP network principles. When z/OS gets a packet from, say 192.168.11.140, and wants to respond to it, z/OS believes that IP address to be on the same physical network segment. It's going to send out an ARP, and not get an answer. If it tries to initiate a packet, the same thing will happen. This seems to match the behavior you're seeing. From the router instance, you can ping the z/OS system and get a response because they are on the same physical segment. And, you can ping the Linux systems on the HiperSocket Guest LAN, and get a response, because they also are on the same physical segment. But, you cannot get a ping to cross from one to the other. I believe you need to pick another IP subnet for your Linux systems on the Guest LAN, and you probably won't even have to deal with the Concentrator part. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Friday, April 14, 2006 2:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Linux as a hipersocket router... OK, I went back to the device drivers book only. (Same steps as the SHARE presentation).. I do have a layer3 QDIO guest LAN.. For a router or the Hipersocket Network Concentrator thhe book says to issue the following to the hipersocket device: echo primary_connector > /sys/bus/ccwgroup/drivers/qeth/0.0.a1c0/route4 I do and I get (on the 3270 console): qeth: Error (0xe012) while setting routing type on hsi0. Type set to 'no router' The book also says to issue the following to the OSA (the QDIO guest LAN in my setup): echo multicast_router > /sys/bus/ccwgroup/drivers/qeth/0.0.a1c4/route4 and I get: qeth: Error (0xe012) while setting routing type on hsi0. Type set to 'no router' In trying other things, the hsi0 won't accept primary or secondary router or connector, but it will accept multicast_router. And the eth1 guest LAN interface will accept primary_router. But that's backwards from what the book asks for... But still can't ping across the router, the same after the start_hsnc.sh Any further thoughts? Has anyone sucessfully done something similar, or even the Hipersocket Network Concentrator (since the qeth driver won't take the commands from the book)? Thanks, Lee ---------------------------------------------------------------------- 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
