You are not logged in.
Could you tell which thread this concerns?
When you say "something not working well", I assume you are getting some error message or something from the command. Perhaps you could share that with us?
"Works for me" [tm]
I copied your command and tried it: 197M and no errors, 399M when unpacked and configured.
Sorry. I think I don't understand the "ip" man page; and maybe it is that the peer address must be given at the same time as configuring it's own address.
Anyhow, maybe use "ipconfig" instead:
# ifconfig tun0 dstaddr 10.3.0.1
That should accomplish the same thing.
I'm not sure how the tun0 interface is created, but the problem here is that its "remote address" is not configured correctly. The interface correctly should have 10.3.0.42 as its own address, but it should have 10.3.0.1 as its PtP address. To do this manually I think you'd do
ip link set tun0 peer 10.3.0.1
But I would have thought that openvpn would do so itself via its configuration. I'm not using openvpn myself so I don't know exactly, but its configuration should declare that 10.3.0.1 is "its" IP address, whereas 10.3.0.42 is the client's IP address (or one of them, depending on how it assigns those).
Ah. the tun interface is not configured correctly. Its P-t-P address should be 10.3.0.1.
The problem is to determine why. And how come it works on the 32bit host (does it get configured correctly)?
Maybe I misunderstood the set up, because there's no trace of using openvpn there? And there's also nothing stopping network traffic, but rather a quite normal, working set up.
Did you really start openvpn before capturing all that?
Ok. Details, please. When you've started openvpn (not working), include the following:
the routing table
# ip route list all
iptables rules
# iptables-save
DNS configuration
# cat /etc/resolv.conf
the result of
# cat /proc/sys/net/ipv4/ip_forward
and interfaces
# ifconfig -a
.
One or some of those should probably tell what the problem might be.
With a simple command like
dpkg -l | awk '$1=="ii" {print $2}' | xargs -rn1 -I+ sh -c "dpkg -L + | grep --label=+ -Hw systemd" > systemd-references.txt
you'll get a listing of how all installed packages have paths with the word "systemd" in their name.
On my laptop (Devuan beta fully upgraded), I find "systemd" mentioned by 29 packages in a total of 148 times, of which 90 are plain files (the other are directory paths). Specifically:
acpid:/lib/systemd/system/acpid.socket
acpid:/lib/systemd/system/acpid.path
acpid:/lib/systemd/system/acpid.service
alsa-utils:/lib/systemd/system/alsa-state.service
alsa-utils:/lib/systemd/system/alsa-store.service
alsa-utils:/lib/systemd/system/alsa-restore.service
alsa-utils:/lib/systemd/system/basic.target.wants/alsa-state.service
alsa-utils:/lib/systemd/system/basic.target.wants/alsa-restore.service
alsa-utils:/lib/systemd/system/alsa-utils.service
alsa-utils:/lib/systemd/system/shutdown.target.wants/alsa-store.service
anacron:/lib/systemd/system/anacron.service
anacron:/lib/systemd/system/anacron-resume.service
at:/lib/systemd/system/atd.service
augeas-lenses:/usr/share/augeas/lenses/dist/tests/test_systemd.aug
augeas-lenses:/usr/share/augeas/lenses/dist/systemd.aug
binfmt-support:/lib/systemd/system/binfmt-support.service
consolekit:/lib/systemd/system/console-kit-log-system-restart.service
consolekit:/lib/systemd/system/console-kit-log-system-stop.service
consolekit:/lib/systemd/system/console-kit-log-system-start.service
consolekit:/lib/systemd/system/console-kit-daemon.service
consolekit:/lib/systemd/system/reboot.target.wants/console-kit-log-system-restart.service
consolekit:/lib/systemd/system/poweroff.target.wants/console-kit-log-system-stop.service
consolekit:/lib/systemd/system/halt.target.wants/console-kit-log-system-stop.service
consolekit:/lib/systemd/system/basic.target.wants/console-kit-log-system-start.service
cron:/lib/systemd/system/cron.service
devuan-baseconf:/etc/apt/preferences.d/avoid-systemd
dmeventd:/lib/systemd/system/dm-event.socket
dmeventd:/lib/systemd/system/dm-event.service
dnsmasq:/lib/systemd/system/dnsmasq.service
ifupdown:/lib/systemd/system/networking.service
ifupdown:/lib/systemd/system/ifup@.service
init-system-helpers:/usr/share/man/man1/deb-systemd-helper.1p.gz
init-system-helpers:/usr/share/man/man1/deb-systemd-invoke.1p.gz
init-system-helpers:/usr/bin/deb-systemd-invoke
init-system-helpers:/usr/bin/deb-systemd-helper
libsystemd0:amd64:/usr/share/doc/libsystemd0
libsystemd0:amd64:/usr/share/doc/libsystemd0/changelog.Debian.gz
libsystemd0:amd64:/usr/share/doc/libsystemd0/copyright
libsystemd0:amd64:/lib/x86_64-linux-gnu/libsystemd.so.0.15.0
libsystemd0:amd64:/lib/x86_64-linux-gnu/libsystemd.so.0
libsystemd0:i386:/lib/i386-linux-gnu/libsystemd.so.0.15.0
libsystemd0:i386:/usr/share/doc/libsystemd0
libsystemd0:i386:/usr/share/doc/libsystemd0/changelog.Debian.gz
libsystemd0:i386:/usr/share/doc/libsystemd0/copyright
libsystemd0:i386:/lib/i386-linux-gnu/libsystemd.so.0
lintian:/usr/share/lintian/checks/systemd.desc
lintian:/usr/share/lintian/checks/systemd.pm
lm-sensors:/lib/systemd/system/lm-sensors.service
lvm2:/lib/systemd/system/lvm2-pvscan@.service
lvm2:/lib/systemd/system/lvm2-monitor.service
lvm2:/lib/systemd/system/lvm2-lvmetad.socket
lvm2:/lib/systemd/system/lvm2-lvmetad.service
lvm2:/lib/systemd/system/lvm2-activation.service
lvm2:/lib/systemd/system/lvm2-activation-early.service
lvm2:/lib/systemd/system/lvm2.service
openssh-server:/lib/systemd/system/ssh.service
openssh-server:/lib/systemd/system/ssh.socket
openssh-server:/lib/systemd/system/ssh@.service
pulseaudio:/usr/lib/systemd/user/pulseaudio.socket
pulseaudio:/usr/lib/systemd/user/pulseaudio.service
pulseaudio:/usr/lib/pulse-7.1/modules/module-systemd-login.so
rsync:/lib/systemd/system/rsync.service
screen:/lib/systemd/system/screen-cleanup.service
slim:/lib/systemd/system/slim.service
sudo:/lib/systemd/system/sudo.service
system-config-printer-udev:/lib/systemd/system/configure-printer@.service
udev:/usr/share/man/man8/systemd-udevd.service.8.gz
udev:/usr/share/man/man8/systemd-hwdb.8.gz
udev:/bin/systemd-hwdb
udev:/lib/systemd/systemd-udevd
udev:/lib/systemd/system/systemd-hwdb-update.service
udev:/lib/systemd/system/systemd-udevd.service
udev:/lib/systemd/system/systemd-udevd-kernel.socket
udev:/lib/systemd/system/systemd-udevd-control.socket
udev:/lib/systemd/system/systemd-udev-trigger.service
udev:/lib/systemd/system/systemd-udev-settle.service
udev:/lib/systemd/network/99-default.link
udev:/usr/share/man/man8/systemd-udevd-control.socket.8.gz
udev:/usr/share/man/man8/systemd-udevd.8.gz
udev:/usr/share/man/man8/systemd-udevd-kernel.socket.8.gz
udev:/lib/systemd/system/udev.service
udev:/lib/systemd/system/sysinit.target.wants/systemd-hwdb-update.service
udev:/lib/systemd/system/sysinit.target.wants/systemd-udevd.service
udev:/lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service
udev:/lib/systemd/system/sockets.target.wants/systemd-udevd-kernel.socket
udev:/lib/systemd/system/sockets.target.wants/systemd-udevd-control.socket
usb-modeswitch:/lib/systemd/system/usb_modeswitch@.service
wpasupplicant:/lib/systemd/system/wpa_supplicant.service
xserver-xorg-input-wacom:/lib/systemd/system/wacom-inputattach@.service
zsh-common:/usr/share/zsh/functions/Completion/Unix/_systemd
dev1galaxy only uses BBCode, which you can find documented following the BBCode link below the Quick reply box, where it says "BBCode: on". The "BBCode" text is a link, to
https://dev1galaxy.org/help.php#bbcode which documents the extent of available markup.
Also, there is a Profile tick box in the "privacy" section for opting-in on getting subscribed to your topics. It might be possible to have that as default, and rather "force" people to to opt-out instead.
Maybe I misunderstood; my
devuan_jessie_1.0.0-beta2_amd64_CD.iso (from files.devuan.org)
includes /pool/DEBIAN/main/w/wpa/wpasupplicant_2.3-1+deb8u4_amd64.deb
The newest addition to the dev1galaxy.org forum intends to make git.devuan.org (gdo) more directly accessible and understandable to Devuan users as well as to (hopefully) help solve outstanding project issues posted at gdo.
Every project and issue at gdo can now be found on dev1galaxy via the two special "Projects" and "Issues" forums in the new "git.devuan.org" section.
The Projects forum (https://dev1galaxy.org/viewforum.php?id=18) organizes Devuan projects into two categories - "devuan-packages / infrastructure" and "other projects". Both categories are presented as alphabetical and activity ordered lists. The project lists offer a short description (if available) and a convenient, single-click access to all projects at git.devuan.org.
The Issues forum (https://dev1galaxy.org/viewforum.php?id=19) holds threads that are automagically created by dev1galaxy's trusty "gdolink" bot, from all open issues at git.devuan.org. The bot will add newly opened issues (if any) to the Issue lists, every 30 minutes. Posting these issues on d1g will give greater exposure to issues that are currently buried in the gdo 'cave' (which is perceived as inaccessible by some). Opening parallel forum threads provides opportunity for discussion and collaborative problem solving that will accelerate Devuan's progress and usability.
Note that the posts in these issue threads are distinct from the comment discussion on gdo. However, when a post suggests a solution to an issue, or has information to advance it, a project team member will be able to capture the post as an original issue comment at gdo.
Finally, the "gdo Help Desk" is the place to ask questions about gdo and to post tips that will help familiarize users with how gdo works.
I saw on IRC that you've done many things trying to get it to work.
What does dmesg say now?
Perhaps it's ok to remove the BusID phrase instead?
You should probably use the longer one, "0000:00:0d.0"
Also, if you would put listings etc in code blocks, i.e. within a pair of [code] and [/code], it'd be easier to read.
This function is has been improved, and you are now able to both have a password log in and to log in via git.devuan.org.
Like before, when you log in via git.devuan.org, your account is promoted into a "via git.devuan.org" account. This is then remembered by the forum through any subsequent log in, whether via password or via git.devuan.org, until you go through the "Forgot my password" procedure.
It's a bit scary to reply to this, because you've raised a fair few issues in the one breath :-)
How about splitting them up into several (is it 3 or is it 4?) threads.
As for the the last issue, "compiling without systemd", I believe a search in the
dyne.org's mailing list may bring up some discussions. That would be my first target for "FAQs in one spot"; though I wouldn't be surprised if there are more spots than one available.
The Dev1 Galaxy Forum now lets you use your git.devuan.org login to log in, where you need authorize the forum to access your user information. Just click the link on the login page and follow the prompts. If you run into problems, contact the forum administrators, or drop a line at freenode#d1g-users for assistance.
As a new forum user, you will be automatically registered with the git.devuan.org username and email, unless of course, there is a clash with an existing account.
As an existing user, with the same username and email, you will automatically "promote" your account to a "via git.devuan.org" account.
As an existing user, with different username or email, you will be automatically registered with the git.devuan.org username and email, unless of course, there is a clash with an existing account.
To revert your account (back?) to a password account, you need to follow the "Forgot my password" route, and set a new password whilst avoiding to log in via git.devuan.org.
Welcome!
Not sure what 'the standard way' means to you, but for example, the group name 'storage' is not listed at https://wiki.debian.org/SystemGroups. I suppose, that might not be normative for Devuan, since Devuan is not Debian, but to me it implies that polkit is not standard.
In any case, whether standard or not doesn't help towards your problem, which rather seems to be, how to configure udisks and/or polkit to work the way you want.
What was wrong with using pmount/pumount ?
Maybe https://www.stopforumspam.com could be of some use?
It's worth to note that some buttons generate many events, with different arguments. E.g., my lid button has "open" or "close" as (third) arguments . The script (or the recognition rule) will then need to distinguish appropriately, to get the right thing done for the right event(s).
I've moved this project to gitlab, https://git.devuan.org/ralph.ronnquist/rrq.git, and included control scripts with a full setup of tun interfaces, routing and iptables rules, as an OOTB filtering solution. Though, it doesn't include block list files; I only have the ones I bought, and no free ones.
There's also an HTTP admin tool for the brave hearted.
Sigh. Several people have told me how wrong I am: apparently in computing, anything older than 6 years is ancient ...
My friend, to use "ancient" about things from some 30 or so years ago is also a way to climb the scale. In any case, I got a good answer to my question. We can meet up and discuss the rest sometime, somewhere.