|
|||
Quote:
Ok, I've just loaded up the system where as usual it now prompts for the "Auth user name" and then "password" before proceeding to the main login screen Xterm window. After typing Code:
pgrep -lf openvpn Code:
ifconfig tun0 I feel like theres just some minor thing preventing this from all working and it might just be another matter of solving another typo.... Jasenko, judging by your sig you may have more than a good idea what the problem is given the various posts above... and jggimi, even if you're not directly familiar with OpenVPN surely you have some idea of whats going on (or wrong) here because you clearly known the standard function/locations of these hostname files, and if there's one thing I've learnt from my short time on OpenBSD its that everything tends to operate in a very simple and standardised way across many different programmes.... Why should OpenVPN be any different?... EDIT: It seems from your reply that my vi input to make the hostname.tun0 file is fine, but why do I get no obvious error or response on running Code:
pgrep -lf openvpn Last edited by Entropic; 4th December 2022 at 02:27 PM. |
|
|||||
Quote:
Quote:
Quote:
Quote:
Quote:
|
|
||||
Only NICs that have a hostname.if(5) file will be provisioned on boot by the OS. The netstart(8) script scans for these files, and takes no action when it doesn't find them.
First: confirm your em0 network connection has been provisioned on your running system. Do this by issuing the command $ ifconfig em0 , and review the output. If your em0 NIC has an IP address and netmask assigned, and an active status, the NIC has been provisioned. If you don't have an active em0 NIC, then issue $ ifconfig by itself and get a list of all your NICs. You'll have a loopback pseudo-NIC, all physical NICs, an IPSec encapsulation pseudo-NIC, and your non-working OpenVPN tunnel pseudo-NIC.Second: If em0 has been provisioned, it had to have been provisioned somewhere. Either via netstart -- which you have told us does not have a provisioning file for em0 -- or by an rc.local(8) script, which you haven't mentioned and is therefore unlikely, or by manually entering ifconfig(8) provisioning commands some time after booting, which you haven't mentioned doing. If you are manually entering a command like # ifconfig em0 inet autoconf after your system is already running, this would be after your OpenVPN connection has already failed to start. If em0 has been provisioned with an IP address, and a) you do not have an /etc/hostname.em0 file, and b) you do not have an /etc/rc.local file, and c) you are not manually provisioning em0 ... then the only other remaining possibility is the openvpn client application is somehow doing the provisioning. Which is improbable, but not completely impossible. You can test this improbability by temporarily renaming the file to something netstart(8) will not act on, such as: # mv /etc/hostname.tun0 /etc/do.not.start.tun0 and reboot. If, on reboot, em0 is no longer provisioned you will know the improbable became possible. To rename the file back, you would use # mv /etc/do.not.start.tun0 /etc/hostname.tun0 .
|
|
|||
Quote:
Without the ability to upload the script here (No explanations were given when I asked about how I'd browse to a file from within openBSD firefox to upload earlier in this thread), I can report the following following "ifconfig": em0: flags=xxxxxx<UP, BROADCAST, RUNNING, SIMPLEX, MULTICAST, AUTOCONF4> mtu 1500 lladr: xxxxxxxxx index 1 priority 0 llprio 3 groups: egress media: ethernet autoselect (1000baseT full-duplex) status: active inet 192.168.xxx.x netmask broadcast 192.168.xxx.255 tun0: flags=xxxx <UP, POINTOPOINT, RUNNING, MULTICAST> mtu 1500 Index: 5 priority 0 llprio 3 groups: tun status: down pflog0: flags=141 <UP, RUNNING, PROMISC> mtu 33136. index 6 priority 0 llprio 3 groups: pflog There's a bunch of other interfaces in there such as iwn0 (WLAN - wireless), enc0 (active - whatever this is: Bluetooth?, lo0 (127.0.xxx - loopback?) but I doubt these are relevant. I'm listing them in case they might be... Quote:
Quote:
Frankly I don't see how this really takes me any further. I'd already established in previous posts that my internet was working, and that its the OpenVPN thats not. This troubleshooting just done merely confirms what we already knew and doesn't do anything to resolve the lack of OpenVPN... Can anyone help here noting the very detailed posts earlier in this thread clearly explaining both system observations and actions taken to try and get OpenVPN working? i.e. openvpn has been installed successfully, my openvpn (.ovpn) files have been placed in /etc/openvpn where they should be, and hostname.tun0 has been edited with vi to include the appropriate "up !/usr/local/sbin/openvpn --daemon --config /etc/openvpn/openbsd.ovpn" command which seems to be doing something because on startup I'm being prompted for an auth username and pw.. yet still openvpn (tun0) is reporting "down" on ifconfig checking. |
|
||||
Quote:
Quote:
Quote:
|
|
|||
Quote:
Code:
script -a /tmp <filename.typescript> Quote:
Code:
cat sweden.ovpn Code:
dev tun Code:
remote switzerland-ca-version-2.expressnetw.com 1195 |
|
||||
Quote:
$ col -b < input.file > output.file or $ cat input.file | col -b > output.file .Quote:
Last edited by jggimi; 6th December 2022 at 01:13 PM. Reason: typos |
|
|||
Beaten but not broken. I'm back after a week giving this all a break to come back with fresh eyes. I think it's time I got some typescript files up here so you can see exactly what I'm facing in getting this OpenVPN connection to my VPN provider (as client) sorted. There's a couple of things I need to sort out before I do so, however:
(1) How do I output a limited typescript file that won't include sensitive info like root passwords etc ? (2) What's the command for checking for all running daemons. I'm sure I've seen the instruction somewhere but on re-checking the man pages for daemon I found no such instruction :/ |
|
||||
Quote:
Quote:
|
|
|||
Quote:
Code:
vi /etc/scripts/blahblah.typescript Code:
/text So what else can I use to "edit" this typescript file and redact the sensitive bits? I tried ed(1) already btw but its hopeless. It seems to have the same inane secret handshake methodologies for performing basic functions as vi, but unfortunately not the same specific shortcuts as vi's... and I'm just going nowhere with it, even with the man pages... So what else can I use to edit the file, and why is vi failing me? Quote:
Thinking that perhaps I messed up the openvpn installation at some point of my creating / deleting the config file I used Code:
pkg_delete openvpn Code:
pkg_add -vv openvpn |
|
||||
Quote:
OpenBSD comes with vi(1), mg(1), ed(1), and sed(1), and to be honest there's a learning curve for all of them. Quote:
You may be able to find out why OpenVPN is failing to start, with: # rcctl -d start openvpn . The rc.d(8) man page describes the -d option:Code:
-d Setting this option will print the function names as they are called and prevent the rc.subr(8) framework from redirecting stdout and stderr to /dev/null. This is used to allow debugging of failed actions. Quote:
Last edited by jggimi; 14th December 2022 at 09:49 PM. Reason: clarity, typo |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
OpenBSD Vlan setup | Crypt | OpenBSD Security | 6 | 13th August 2020 01:25 AM |
Your OpenBSD shell setup | hanzer | OpenBSD General | 11 | 23rd October 2017 09:35 PM |
OpenBSD Multiple VPN Setup | Dr-D | OpenBSD Security | 10 | 7th April 2014 10:50 AM |
OpenBSD VPN Setup | Dr-D | OpenBSD Security | 2 | 4th April 2014 01:23 PM |
how setup arpwatch for OpenBSD | mfaridi | OpenBSD Packages and Ports | 1 | 11th December 2008 05:22 PM |