Skip to main content

archlinux switch to bridge network

Switch from normal networking to bridged

Just after installation, you need to run networking on a traditional way in order to make initial setup (some needed packages like SSH, netctl,...)

"Traditional networking" is here to use the "ethN" or "enoZZZZZ" interface and assign an IP to that interface.

But if you want to switch to bridged one, you need to disable that traditional setting and activate the bridged one.

Traditional setting

  • Interface name: eth0
  • Address assignation: static
/etc/systemd/network/wired.network

[Match]
Name=eth0
[Network] 
DNS=192.168.128.108
[Address]
Address=192.168.129.148/23
[Route]
Gateway=192.168.128.108

Start "systemd-networkd.service"
# systemctl start systemd-networkd

To enable it at boot,
# systemctl enable systemd-networkd

Switch to bridged setting

# pacman -S netctl

/etc/netctl/lxcbridge
Description="LXC bridge"
Interface=br0
Connection=bridge
BindsToInterfaces=('eth0')
IP=static
Address=192.168.129.148/23
Gateway='192.168.128.1'
DNS=('192.168.128.150','192.168.128.108')

To disable traditional networking at boot,
# systemctl disable systemd-networkd

Enable the bridge
# netctl enable lxcbridge

Enable (also) the bridge
# systemctl enable netctl-auto@br0.service


Comments

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Gnome VNC Grey Checkboxes

When setting up VNC server in Gnome, I get a grey screen (or a black one) and the checkboxes to "Accept clipboard from viewers", "Send clipboard to viewers", "Send primary selection to viewers". I'm setting up a VNC server on a Debian 10 machine that has Gnome environment. A zillion articles can be found on Internet, they have the same global path: Install Gnome and GDM Install TigerVNC Setup the VNC Server: password + startup Run the server Connect from the client One of them is this TeknoTut how-to I took inspiration from. The tutorial is good, but I needed to complete it with extra steps in order to make it work: If the current user has already a running Gnome session, I just get the "grey screen with the checkboxes". It is good to know that: The "grey screen" is due to the "xsetroot" command that can be seen in some howtos The checkboxes are due to the "vncconfig -iconic &" command