From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Subject: Re: static-networking-service-type: Using a static network bridge
Date: Wed, 22 Mar 2023 07:24:01 +0100 [thread overview]
Message-ID: <66E59A8E-82D0-4CE0-B37B-EA4C91A5FA2A@lepiller.eu> (raw)
In-Reply-To: <20230322013248.7299a393@primary_laptop>
You specified type twice, with #f the last time. Maybe that's tge issue?
Le 22 mars 2023 01:32:48 GMT+01:00, Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> a écrit :
>Hi,
>
>Is it possible to do something like that in a system configuration?:
>> ip link add lan0 type bridge
>> ip link set dev eth0 master lan0
>> ip addr add 192.168.1.5/24 dev lan0
>> ip route add default via 192.168.1.1 dev lan0
>
>I've tried it with something like that (with the IP addresses and "eth0"
>changed):
>> (service static-networking-service-type
>> (list
>> (static-networking
>> (addresses (list (network-address
>> (device "lan0")
>> (value "192.168.1.5/24"))))
>> (links (list (network-link (name "lan0")
>> (type 'bridge)
>> (arguments '()))
>> (network-link
>> (name "eth0")
>> (type #f)
>> (arguments '("master" "lan0")))))
>> (name-servers '("192.168.10.1"))
>> (routes (list (network-route (destination "default")
>> (gateway "192.168.1.1")))))))
>but the issue is that the bridge isn't even created.
>
>Did I do something wrong, or is that configuration not supported?
>
>Denis.
next prev parent reply other threads:[~2023-03-22 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 0:32 static-networking-service-type: Using a static network bridge Denis 'GNUtoo' Carikli
2023-03-22 6:24 ` Julien Lepiller [this message]
2023-03-23 23:08 ` Denis 'GNUtoo' Carikli
2023-03-24 17:14 ` Julien Lepiller
2023-03-27 17:37 ` Denis 'GNUtoo' Carikli
2023-03-29 18:27 ` Julien Lepiller
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=66E59A8E-82D0-4CE0-B37B-EA4C91A5FA2A@lepiller.eu \
--to=julien@lepiller.eu \
--cc=GNUtoo@cyberdimension.org \
--cc=help-guix@gnu.org \
/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).