unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
Cc: help-guix@gnu.org
Subject: Re: A seed for the concept of a network router
Date: Fri, 26 Jul 2024 12:33:35 +0900	[thread overview]
Message-ID: <87frrwvncg.fsf@gmail.com> (raw)
In-Reply-To: <84bk31bz2w.fsf@marekpasnikowski.pl> ("Marek Paśnikowski"'s message of "Sat, 13 Jul 2024 08:11:51 +0200")

Hi Marek,

Marek Paśnikowski <marek@marekpasnikowski.pl> writes:

> Dear All
>
> I am struggling to identify the most basic information to take the first
> step towards building a Guix-based network router.  I would like to ask
> for a minimal service configuration to meet the following goal:

I think you'd be best served by the "bare-bones.tmpl" template which can
be found in the Guix sources under gnu/system/examples/bare-bones.tmpl.

Be aware that it is not exactly light in terms of disk space: the last
time I generated a disk image from this configuration, it weighed more
than a GiB!

> I have a fanless mini-computer with two ETH interfaces.  It currently
> sits under a proper router device like all the other devices in my LAN.
> I wish to be able to physically hook it up between the router and the
> WAN modem in such a way, that all incoming traffic (except one SSH port)
> gets immediately forwarded to the router, as if there was nothing else
> between the modem and the router.  Bonus points if it is possible to
> fake the MAC address.
>
> The underlying idea is that I would then be able to experiment with all
> the available options and concepts without fear of bricking my learning
> process.  Thanks to the machine being an actual computer, I have the
> ability to connect a display and a keyboard to really break the concept
> of routing down to its atoms and come back safely to a previously
> working configuration.

Your other questions appear to be more related to networking than to
Guix itself; there are many resources out there detailing how to do this
kind of thing in various ways -- your would probably use some command
line interface such as 'ip' to setup route and networks.

Once the required command line is known, a one shot Shepherd service can
run it at boot to persist the network configuration.

-- 
Thanks,
Maxim


      parent reply	other threads:[~2024-07-26  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13  6:11 A seed for the concept of a network router Marek Paśnikowski
2024-07-15 16:22 ` Felix Lechner via
2024-07-21 13:29   ` Marek Paśnikowski
2024-07-26  3:33 ` Maxim Cournoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87frrwvncg.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=marek@marekpasnikowski.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).