From: jjs <jjs@tmsusa.com>
To: Jochen Hein <jochen@jochen.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.65] tun not working
Date: Fri, 21 Mar 2003 11:30:55 -0800 [thread overview]
Message-ID: <3E7B686F.9030102@tmsusa.com> (raw)
In-Reply-To: 873clgh6t7.fsf@jupiter.jochen.org
Just as a data point, tun itself works for
me on x86 - I use openvpn between my
lan and our remote pop3 server, so I'd
find out in a big hurry if it ever broke -
(currently running 2.5.65 on the vpn gw)
Sounds like a 390-sepecific issue, or
a hercule-specific issue?
Joe
Jochen Hein wrote:
>I'm using tun to connect my virtual S/390 from hercules to the local
>machine. That works pretty well with 2.4, but with 2.5.65 hercules
>fails with:
>
>root@gswi1164:~# hercules -f /etc/hercules/hercules.cnf
>Hercules Version 2.16.5
>(c)Copyright 1999-2002 by Roger Bowler, Jan Jaeger, and others
>Built on Jul 9 2002 at 23:09:56
>Build information:
> Debian
> Modes: S/370 ESA/390 ESAME
> Using setresuid() for setting privileges
> HTTP Server support
>
>Running on Linux i686 2.5.65 #1 Thu Mar 20 19:11:34 CET 2003
>ckddasd: /mount/d/hercules/linux.191 cyls=300 heads=15 tracks=4500
>trklen=47616
>HHC894I Error setting MTU for tun: No such device
>HHC897I Error setting driving system IP addr for tun: No such device
>HHC897I Error setting Hercules IP addr for tun: No such device
>HHC897I Error setting netmask for tun: No such device
>HHC898I Error getting flags for tun: No such device
>HHC848I 0400 configuration failed: hercifc rc=4
>HHC038I Initialization failed for device 0400
>
>hercules uses /dev/net/tun to access the tun device.
>
>The module tun is loaded:
>
>dmesg:
>Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
>
>root@gswi1164:~# lsmod | grep tun
>tun 6240 0
>
>Any idea why this fails?
>
>Jochen
>
>
>
next prev parent reply other threads:[~2003-03-21 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 19:13 [2.5.65] tun not working Jochen Hein
2003-03-21 19:30 ` jjs [this message]
2003-03-29 18:27 ` Jochen Hein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E7B686F.9030102@tmsusa.com \
--to=jjs@tmsusa.com \
--cc=jochen@jochen.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox