Find the answer to your Linux question:
Results 1 to 4 of 4
OpenVPN attempts to start during normal system startup (S19). The problem is that the WiFi adapter isn't online until after the user has logged in (I have auto login setup) ...
  1. #1
    Just Joined!
    Join Date
    Sep 2010
    Posts
    1

    Need WiFi to start when system starts, not when user logs in

    OpenVPN attempts to start during normal system startup (S19). The problem is that the WiFi adapter isn't online until after the user has logged in (I have auto login setup) and then the keyring is opened and the network connets. Until that happens, OpenVPN will error as the IP address for the WiFi adapter isn't active. How can I fix this?

  2. #2
    Linux Newbie JosePF's Avatar
    Join Date
    Jun 2010
    Posts
    225
    Hello,
    according to the howto:
    "Starting up the VPN and testing for initial connectivity
    Starting the server

    First, make sure the OpenVPN server will be accessible from the internet. That means:

    * opening up UDP port 1194 on the firewall (or whatever TCP/UDP port you've configured), or
    * setting up a port forward rule to forward UDP port 1194 from the firewall/gateway to the machine running the OpenVPN server.

    Next, make sure that the TUN/TAP interface is not firewalled.

    To simplify troubleshooting, it's best to initially start the OpenVPN server from the command line (or right-click on the .ovpn file on Windows), rather than start it as a daemon or service:

    openvpn [server config file]

    A normal server startup should look like this (output will vary across platforms):

    Sun Feb 6 20:46:38 2005 OpenVPN 2.0_rc12 i686-suse-linux [SSL] [LZO] [EPOLL] built on Feb 5 2005
    Sun Feb 6 20:46:38 2005 Diffie-Hellman initialized with 1024 bit key
    Sun Feb 6 20:46:38 2005 TLS-Auth MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
    Sun Feb 6 20:46:38 2005 TUN/TAP device tun1 opened
    Sun Feb 6 20:46:38 2005 /sbin/ifconfig tun1 10.8.0.1 pointopoint 10.8.0.2 mtu 1500
    Sun Feb 6 20:46:38 2005 /sbin/route add -net 10.8.0.0 netmask 255.255.255.0 gw 10.8.0.2
    Sun Feb 6 20:46:38 2005 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:23 ET:0 EL:0 AF:3/1 ]
    Sun Feb 6 20:46:38 2005 UDPv4 link local (bound): [undef]:1194
    Sun Feb 6 20:46:38 2005 UDPv4 link remote: [undef]
    Sun Feb 6 20:46:38 2005 MULTI: multi_init called, r=256 v=256
    Sun Feb 6 20:46:38 2005 IFCONFIG POOL: base=10.8.0.4 size=62
    Sun Feb 6 20:46:38 2005 IFCONFIG POOL LIST
    Sun Feb 6 20:46:38 2005 Initialization Sequence Completed

    "

    You could include that command in your start up applications.
    (Ah, and disable Openvpn with update-rc.d if you dont want to try init booting)

    I hope this help you
    Regards

  3. #3
    Linux Guru reed9's Avatar
    Join Date
    Feb 2009
    Location
    Boston, MA
    Posts
    4,651
    You can also switch to wicd, which if you set it to autoconnect to a network, will do so as soon as the daemon starts.

    Or manually setup your interface, using /etc/network/interfaces and disabling networkmanager or wicd.

  4. #4
    Linux Newbie
    Join Date
    Apr 2010
    Posts
    119
    Right click your wifi icon. Click on Edit Connections. Click the wireless tab. Select your wifi, and ADD. Save. Reboot. it should log in automatically now.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...