« Return to Thread: Help needed with Fedora11.s390 networking
Re: Help needed with Fedora11.s390 networking
by jsganino-2
::
Rate this Message:
--- In hercules-390@..., "vk2kad" <vk2kad@...> wrote:
>
> Hi All
>
> I have been playing around with the newly released Fedora 11 for s390 - after a few false starts I now have it running on my Ubuntu 8.10 system. I decided to move to Ubuntu after having issues with Windows networking.
>
> I now have an IPLable Fedora running under Hercules 3.06. I first tried Hercules 3.05 but hit a problem with what appears to be PAV support. F11 would start to IPL but crashed trying to bring the sysres online. A helpful hint from Harold G about using the cu=3990-3 parameter advanced me to the stage where I was able to logon - firstly via the Hercules console in line mode - and then via SSH. The line mode of Hercules where all commands are prefixed with a dot is useful but I haven't worked out how to edit any files - there doesn't seem to be any way to send control key sequences to the editor (Like ^c and ^x etc)
>
> So I have a running system that I can get into from my local machine - what is eluding me is getting from Fedora to the internet so that I can configure more packages.
> Below are some snips of how my networking has been set up...
>
> From the Hercules config file
>
> # networking, channel-to-channel adapter
>
> 0600.2 3088 CTCI -n /dev/net/tun -t 1500 192.168.10.13 192.168.10.14
> 0610.2 3088 CTCI -n /dev/net/tun -t 1500 192.168.10.23 192.168.10.24
>
> # networking, LCS adaptor
>
>
> 0700.2 3088 LCS 192.168.10.8 -n /dev/net/tun -m 01:02:03:04:05:06
>
> Only the first CTCI definition seems to be discovered and working.
>
> From Hercules startup
>
> HHCHD018I Loadable module directory is /usr/lib/hercules
> HHCCF065I Hercules: tid=B7AE26B0, pid=7708, pgid=7708, priority=0
> HHCDA020I /home/bern/fedora390.img cyls=10017 heads=15 tracks=150255 trklen=56832
> HHCTE001I Console connection thread started: tid=B785BB90, pid=7708
> HHCTE003I Waiting for console connection on port 3270
> HHCCT073I 0600: TUN device tun0 opened
> HHCCT073I 0610: TUN device tun1 opened
> HHCLC073I 0700: TAP device tap0 opened
>
> Hercules seems happy with the two CTCs and the LCS definition.
>
> From inside Fedora here is the IFCONFIG output
>
> bern@localhost ~!$
> .ifconfig
> ifconfig
> ctc1 Link encap:Serial Line IP
> inet addr:192.168.200.3 P-t-P:192.168.200.4 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:600 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:240 (240.0 b) TX bytes:52800 (51.5 KiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
>
> bern@localhost ~!$
>
>
> Any clues as to what I am missing ????????
>
> Bern
>
You appear to be using a pair of CTC's to connect to your Fedora, but a couple things look a little off to me:
1) What is on the other end of CTC's? I think you'll need a program on the other side to accept and reply to the Fedora. CTC's establish only a point-to-point connection, and I don't see the other endpoint.
2) The IP address you specify inside Fedora is different from the address you specify in the CTC definitions. I believe they have to match.
I think the CTC's generate the tun0 and tun1 devices, and the LCS generates the tap0 device. If you have the ability to configure your Fedora to use the LCS, via the tap0 device, and (1) enable IP Forwarding in your Ubuntu, and (2) enable proxy_arp in your Ubuntu, I think you will have an easier time of it.
Jim
>
> Hi All
>
> I have been playing around with the newly released Fedora 11 for s390 - after a few false starts I now have it running on my Ubuntu 8.10 system. I decided to move to Ubuntu after having issues with Windows networking.
>
> I now have an IPLable Fedora running under Hercules 3.06. I first tried Hercules 3.05 but hit a problem with what appears to be PAV support. F11 would start to IPL but crashed trying to bring the sysres online. A helpful hint from Harold G about using the cu=3990-3 parameter advanced me to the stage where I was able to logon - firstly via the Hercules console in line mode - and then via SSH. The line mode of Hercules where all commands are prefixed with a dot is useful but I haven't worked out how to edit any files - there doesn't seem to be any way to send control key sequences to the editor (Like ^c and ^x etc)
>
> So I have a running system that I can get into from my local machine - what is eluding me is getting from Fedora to the internet so that I can configure more packages.
> Below are some snips of how my networking has been set up...
>
> From the Hercules config file
>
> # networking, channel-to-channel adapter
>
> 0600.2 3088 CTCI -n /dev/net/tun -t 1500 192.168.10.13 192.168.10.14
> 0610.2 3088 CTCI -n /dev/net/tun -t 1500 192.168.10.23 192.168.10.24
>
> # networking, LCS adaptor
>
>
> 0700.2 3088 LCS 192.168.10.8 -n /dev/net/tun -m 01:02:03:04:05:06
>
> Only the first CTCI definition seems to be discovered and working.
>
> From Hercules startup
>
> HHCHD018I Loadable module directory is /usr/lib/hercules
> HHCCF065I Hercules: tid=B7AE26B0, pid=7708, pgid=7708, priority=0
> HHCDA020I /home/bern/fedora390.img cyls=10017 heads=15 tracks=150255 trklen=56832
> HHCTE001I Console connection thread started: tid=B785BB90, pid=7708
> HHCTE003I Waiting for console connection on port 3270
> HHCCT073I 0600: TUN device tun0 opened
> HHCCT073I 0610: TUN device tun1 opened
> HHCLC073I 0700: TAP device tap0 opened
>
> Hercules seems happy with the two CTCs and the LCS definition.
>
> From inside Fedora here is the IFCONFIG output
>
> bern@localhost ~!$
> .ifconfig
> ifconfig
> ctc1 Link encap:Serial Line IP
> inet addr:192.168.200.3 P-t-P:192.168.200.4 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:600 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:240 (240.0 b) TX bytes:52800 (51.5 KiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
>
> bern@localhost ~!$
>
>
> Any clues as to what I am missing ????????
>
> Bern
>
You appear to be using a pair of CTC's to connect to your Fedora, but a couple things look a little off to me:
1) What is on the other end of CTC's? I think you'll need a program on the other side to accept and reply to the Fedora. CTC's establish only a point-to-point connection, and I don't see the other endpoint.
2) The IP address you specify inside Fedora is different from the address you specify in the CTC definitions. I believe they have to match.
I think the CTC's generate the tun0 and tun1 devices, and the LCS generates the tap0 device. If you have the ability to configure your Fedora to use the LCS, via the tap0 device, and (1) enable IP Forwarding in your Ubuntu, and (2) enable proxy_arp in your Ubuntu, I think you will have an easier time of it.
Jim
« Return to Thread: Help needed with Fedora11.s390 networking
| Free embeddable forum powered by Nabble | Forum Help |
