On 11/24/2010 2:31 PM, Philip L Pinto wrote:
Philipp,
I have the goods and have booted up the system. The thing I'm puzzled
over is the network.
I have ubuntu 10.10 with the 3.07 hercules source built running the system.
Fedora 14 is configured with lcs from what I saw, and I see that
hercules immediately opens tun (in this case /dev/net/tun) when it start
up pre ipl.
I IPL and watch all the messages go by, and when I see it get to the net
startup it says "helper threads started" or some such, I assume one for
each network pipe.
The thing I'm used to seeing is that in the host ubuntu environment I do
an ifconfig, and still only see eth0 and lo0. No sign of tun0.
That sounds like a Ubuntu issue. The Herules scripts provided for
Fedora on System z assume you are also running on a Fedora/Red Hat
system on the host machine. Not surprisingly that is what the Fedora
team does. There can be permissions issues related to the Hercules
binary and its use of tun. This depends on how you installed the
Hercules system. Distribution quirks enter into this, but you should
eventually get it to work.
I am starting hercules with the hercules.exec. which sets up the
iptables stuff, and I'm running as root, so all devices and so forth
should not have permissions problems.
I think i should add a route for 192.168.200.xx to the tun0 to get to
the system, but w/o that, any ideas on what to do to get to the
192.168.200 net?
Trouble shooting recommendation: get reachability to a host IP address
from the Hercules guest working first. Then get reachability outside
of the host. Fealure to reach the host is caused by tun and guest
interface related issues. The second is usually routing issues back to
the guest from local routers or devices when the guest appears to
reside on a different subnet.