From: anterior <anterior@inbox.ru> To: community@lists.altlinux.org Subject: Re: [Comm] Спутниковый интернет. Ошибка - Cannot open TUN/TAP dev Raduga: No such file or directory (errno=2) Date: Fri, 1 Sep 2006 10:55:09 +0400 Message-ID: <200609011055.09406.anterior@inbox.ru> (raw) Добился небольшого прогресса, но все равно выдает ошибку. Смотрите: client.ovpn: client dev tun proto udp ... # openvpn --config /etc/openvpn/config/client.ovpn Fri Sep 1 10:48:08 2006 OpenVPN 2.0.5 i686-suse-linux [SSL] [LZO] [EPOLL] built on Apr 23 2006 Fri Sep 1 10:48:08 2006 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. Fri Sep 1 10:48:08 2006 WARNING: file '/etc/openvpn/config/DpRY200_1227.key' is group or others accessible Fri Sep 1 10:48:08 2006 LZO compression initialized Fri Sep 1 10:48:08 2006 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ] Fri Sep 1 10:48:08 2006 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ] Fri Sep 1 10:48:08 2006 Local Options hash (VER=V4): '41690919' Fri Sep 1 10:48:08 2006 Expected Remote Options hash (VER=V4): '530fdded' Fri Sep 1 10:48:08 2006 UDPv4 link local: [undef] Fri Sep 1 10:48:08 2006 UDPv4 link remote: 80.81.208.66:55460 Fri Sep 1 10:48:12 2006 TLS: Initial packet from 80.81.208.66:55460, sid=0e04ee30 bb12be33 Fri Sep 1 10:48:18 2006 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net Fri Sep 1 10:48:18 2006 VERIFY OK: nsCertType=SERVER Fri Sep 1 10:48:18 2006 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net Fri Sep 1 10:48:26 2006 WARNING: 'dev-type' is used inconsistently, local='dev-type tun', remote='dev-type tap' Fri Sep 1 10:48:26 2006 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1542', remote='link-mtu 1574' Fri Sep 1 10:48:26 2006 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532' Fri Sep 1 10:48:26 2006 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key Fri Sep 1 10:48:26 2006 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Sep 1 10:48:26 2006 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key Fri Sep 1 10:48:26 2006 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Sep 1 10:48:26 2006 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA Fri Sep 1 10:48:26 2006 [RadugaVPN] Peer Connection Initiated with 80.81.208.66:55460 Fri Sep 1 10:48:27 2006 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1) Fri Sep 1 10:48:28 2006 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 80.81.208.66,route-gateway 10.250.35.1,ping 30,ping-restart 120,route 0.0.0.0 0.0.0.0 10.250.35.1,dhcp-option DNS 80.81.208.34,ifconfig 10.250.35.67 255.255.255.0' Fri Sep 1 10:48:28 2006 OPTIONS IMPORT: timers and/or timeouts modified Fri Sep 1 10:48:28 2006 OPTIONS IMPORT: --ifconfig/up options modified Fri Sep 1 10:48:28 2006 OPTIONS IMPORT: route options modified Fri Sep 1 10:48:28 2006 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Fri Sep 1 10:48:28 2006 WARNING: Since you are using --dev tun, the second argument to --ifconfig must be an IP address. You are using something (255.255.255.0) that looks more like a netmask. (silence this warning with --ifconfig-nowarn) Fri Sep 1 10:48:28 2006 TUN/TAP device tun0 opened :) Fri Sep 1 10:48:28 2006 /sbin/ifconfig tun0 10.250.35.67 pointopoint 255.255.255.0 mtu 1500 SIOCSIFDSTADDR: Недопустимый аргумент Fri Sep 1 10:48:28 2006 Linux ifconfig failed: shell command exited with error status: 1 Fri Sep 1 10:48:28 2006 Exiting # :(
reply other threads:[~2006-09-01 6:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200609011055.09406.anterior@inbox.ru \ --to=anterior@inbox.ru \ --cc=community@lists.altlinux.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
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git