Excellent explanation Thore, many thanks.
I had VLAN ID1 marked as tagged on this port. I just added experimentally VLAN
ID99 as untagged (1,2,7 as before tagged). That immediately solved the problem
:-).
I was not aware that I can mix tagged and untagged ids on one port. But that
is a nice fe
Am Samstag, 22. Januar 2022, 07:26:01 CET schrieb Merlin Büge:
> Hi,
>
> you probably missed this part (quoted from your link):
> > Then export the environment variable
> > SSH_AUTH_SOCK="$XDG_RUNTIME_DIR/ssh-agent.socket" in your login shell
> > initialization file, such as ~/.bash_profile or ~/.
Hi,
I think your issue might be that you seem to have DHCP enabled for the
enp2s0.network *and* enp2s0.1 which appear to be in the same layer 2
domain.
Usually VLAN id 1 is implicit as untagged/default.
So if you configured the switch port to add VLAN ids 2 and 7 in tagged
mode, VLAN id 1 likely
Hi,
I configured my network with multiple VLANs. I started with the description at
https://wiki.archlinux.org/title/VLAN#systemd-networkd
My current configuration:
[n3150 ~]# cat /etc/systemd/network/enp2s0.network
[Match]
Name=enp2s0
[Link]
ActivationPolicy=Manual
[Network]
Description=The
Hello Uwe,
funnily, I did reboot my system, being aware of such issues. I did have to
update a few user utilities once again, because a lot of dependency updates
were happening at the same time upstream, but those were just python stuff and
some networking libraries, as required for my mail pro
HI Jeanette,
I suppose you updated you system but did not reboot before trying to mount that
filesystem?
Then the behaviour is easily explained: during the update of the kernel (the package is named linux) all files belonging
to the running kernel are removed and replaced with new files under
After a further reboot FAT filesystems can now be mounted, which is strange. I
found a side note about that somewhere. I did reboot after installing the new
kernel.
Best wishes,
Jeanette
Jan 22 2022, David Rosenstrauch via arch-general has written:
On 1/22/22 5:30 AM, Jeanette C. via arch
On 1/22/22 5:30 AM, Jeanette C. via arch-general wrote:
Hey hey,
I just updated my system yesterday and now I can't mount a VFAT filesystem.
Installed packages:
linux 5.16.2.arch1-1
util-linux 2.37.2-5
There is no mount.vfat or mount.fat program/script and apparently no kernel
module install
Hey hey,
I just updated my system yesterday and now I can't mount a VFAT filesystem.
Installed packages:
linux 5.16.2.arch1-1
util-linux 2.37.2-5
There is no mount.vfat or mount.fat program/script and apparently no kernel
module installed that contains "fat" in its name.
Is there a change in th
Hi,
you probably missed this part (quoted from your link):
> Then export the environment variable
> SSH_AUTH_SOCK="$XDG_RUNTIME_DIR/ssh-agent.socket" in your login shell
> initialization file, such as ~/.bash_profile or ~/.zprofile.
Regards,
Merlin
--
Merlin Büge
> https://wiki.archlinux.org/title/SSH_keys#Start_ssh-agent_with_systemd_user
>
> It seems that SSH_AUTH_SOCK does not get set although it is in the user unit
> file.
>
> $ systemctl --user status ssh-agent.service
> ● ssh-agent.service - SSH key agent
> Loaded: loaded (/home/rd/.config/system
11 matches
Mail list logo