[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

RE: [Openvpn-users] New problem with openvpn (formerly up-script problem).


  • Subject: RE: [Openvpn-users] New problem with openvpn (formerly up-script problem).
  • From: "Tibbs, Richard" <rwtibbs@xxxxxxxxxxx>
  • Date: Sun, 5 Dec 2004 15:55:13 -0500

Well, someone from leaf-user list said that the tun0 is removed because
the script fails.  So, the attempts openvpn 1.6 makes are apparently
failing, viz. daemon.log:
> Dec  4 21:55:38 firewall openvpn[9273]: TUN/TAP device tun0 opened
> Dec  4 21:55:38 firewall openvpn[9273]: ip link set dev tun0 up mtu
1500
> Dec  4 21:55:39 firewall openvpn[9273]: ip addr add dev tun0 local
> 10.1.1.1 peer 10.1.1.2

So, I was trying to see if could set a tunnel manually, then try out all
my script commands to see if they work.

I think you are right below --- I cannot do anything with a tunnel until
openvpn sets it up.
What I do not understand is why I can't manually create a tunnel at the
command line with iproute(2).

I have looked long and hard at the ip man page, and cannot figure how to
do it by hand. 
I try 
  ip link set tun0
and then ip link show does not reveal the tun0

How can a set up a tunnel from the command line?
Rick.

-----Original Message-----
From: openvpn-users-admin@xxxxxxxxxxxxxxxxxxxxx
[mailto:openvpn-users-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Jean-Pierre Schwickerath
Sent: Sunday, December 05, 2004 11:57 AM
To: openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Openvpn-users] New problem with openvpn (formerly
up-script problem).


> Logged in as root, I tried typing
> ip link set dev tun0 up mtu 1500
>  and I get the message
> SIOCSIFMTU: Operation not supported by device.
> ( this happens no matter what mtu I type)

Why do you want to set the mtu if openvpn does it for you?


> # ip link show
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue 
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop 
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:02:e3:13:02:78 brd ff:ff:ff:ff:ff:ff
> 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:02:e3:12:7d:94 brd ff:ff:ff:ff:ff:ff
> 6: ipsec0: <NOARP,UP> mtu 16260 qdisc pfifo_fast qlen 10
>     link/ether 00:02:e3:13:02:78 brd ff:ff:ff:ff:ff:ff
> 7: ipsec1: <NOARP> mtu 0 qdisc noop qlen 10
>     link/ipip 
> 8: ipsec2: <NOARP> mtu 0 qdisc noop qlen 10
>     link/ipip 
> 9: ipsec3: <NOARP> mtu 0 qdisc noop qlen 10
>     link/ipip
> 
> What is wrong here?

I would say your problem is that there is not device tun0. So you can't
set a link mtu on a device that does not exist. 


Jean-Pierre

-- 
Powered by Linux From Scratch - http://schwicky.net/
PGP Key ID: 0xEE6F49B4 - AIM/Jabber: Schwicky - ICQ: 4690141

Nothing is impossible... Everything is relative!

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users


____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users