* Re: Setting up multiple NICs
@ 2023-11-29 6:26 Lars Rustand
2023-11-29 7:39 ` Oleg Pykhalov
2023-12-07 20:22 ` Lars Rustand
0 siblings, 2 replies; 12+ messages in thread
From: Lars Rustand @ 2023-11-29 6:26 UTC (permalink / raw)
To: help-guix
[-- Attachment #1: Type: text/plain, Size: 4058 bytes --]
On 23/11/24 06:08AM, Oleg Pykhalov wrote:
> Hello,
>
> Could you show the configuration, please?
Sure, this is what I have at the moment:
(service static-networking-service-type
(list (static-networking
(links
(list (network-link
(name "dmz")
(type 'vlan)
(arguments '((id . 3)
(link . "enp4s0f1"))))
(network-link
(name "home")
(type 'vlan)
(arguments '((id . 4)
(link . "enp4s0f1"))))
(network-link
(name "iot")
(type 'vlan)
(arguments '((id . 5)
(link . "enp4s0f1"))))
(network-link
(name "server")
(type 'vlan)
(arguments '((id . 6)
(link . "enp4s0f1"))))
(network-link
(name "management")
(type 'vlan)
(arguments '((id . 2)
(link . "enp4s0f1"))))))
(addresses
(list (network-address
(device "enp2s0")
(value "192.168.10.2/24"))
(network-address
(device "dmz@enp4s0f1")
(value "10.0.3.1/24"))
(network-address
(device "home@enp4s0f1")
(value "10.0.4.1/24"))
(network-address
(device "iot@enp4s0f1")
(value "10.0.5.1/24"))
(network-address
(device "server@enp4s0f1")
(value "10.0.6.1/24"))
(network-address
(device "management@enp4s0f1")
(value "192.168.0.2/24")))))))
> Also, a list of the networking
> devices with ‘ip -one link’ and ‘ip -one address’ command would be
> helpful for cathing an error.
lars@router ~$ ip -one link
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000\ link/ether 00:1d:60:cb:15:5b brd ff:ff:ff:ff:ff:ff
3: enp4s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000\ link/ether 28:80:23:a3:0f:80 brd ff:ff:ff:ff:ff:ff
4: enp4s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000\ link/ether 28:80:23:a3:0f:81 brd ff:ff:ff:ff:ff:ff
5: enp4s0f2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000\ link/ether 28:80:23:a3:0f:82 brd ff:ff:ff:ff:ff:ff
6: enp4s0f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000\ link/ether 28:80:23:a3:0f:83 brd ff:ff:ff:ff:ff:ff
lars@router ~$ ip -one address
1: lo inet 127.0.0.1/8 scope global lo\ valid_lft forever preferred_lft forever
1: lo inet6 ::1/128 scope host \ valid_lft forever preferred_lft forever
2: enp2s0 inet 192.168.10.2/24 scope global enp2s0\ valid_lft forever preferred_lft forever
2: enp2s0 inet6 fe80::21d:60ff:fecb:155b/64 scope link \ valid_lft forever preferred_lft forever
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Setting up multiple NICs
2023-11-29 6:26 Setting up multiple NICs Lars Rustand
@ 2023-11-29 7:39 ` Oleg Pykhalov
2023-11-29 8:38 ` Lars Rustand
2023-12-07 20:22 ` Lars Rustand
1 sibling, 1 reply; 12+ messages in thread
From: Oleg Pykhalov @ 2023-11-29 7:39 UTC (permalink / raw)
To: Lars Rustand; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 4694 bytes --]
Lars Rustand <rustand.lars@gmail.com> writes:
[…]
> Sure, this is what I have at the moment:
>
> (service static-networking-service-type
> (list (static-networking
> (links
> (list
> ;; ...
> (network-link
> (name "management")
> (type 'vlan)
> (arguments '((id . 2)
> (link . "enp4s0f1"))))))
> (addresses
> (list (network-address
> (device "enp2s0")
> (value "192.168.10.2/24"))
> ;; ...
> (network-address
> (device "management@enp4s0f1")
> (value "192.168.0.2/24")))))))
I think this "management@enp4s0f1" syntax is not what is expected by the
configuration.
You mentioned that you tried a development version manual. Did you try
configuration similar to the example in that manual?
https://guix.gnu.org/en/manual/devel/pt-br/html_node/Networking-Setup.html
--8<---------------cut here---------------start------------->8---
(static-networking
(links (list (network-link
(name "bond0")
(type 'bond)
(arguments '((mode . "802.3ad")
(miimon . 100)
(lacp-active . "on")
(lacp-rate . "fast"))))
(network-link
(mac-address "98:11:22:33:44:55")
(arguments '((master . "bond0"))))
(network-link
(mac-address "98:11:22:33:44:56")
(arguments '((master . "bond0"))))
(network-link
(name "bond0.1055")
(type 'vlan)
(arguments '((id . 1055)
(link . "bond0"))))))
(addresses (list (network-address
(value "192.168.1.4/24")
(device "bond0.1055")))))
--8<---------------cut here---------------end--------------->8---
So your configuration would be like:
--8<---------------cut here---------------start------------->8---
(service static-networking-service-type
(list (static-networking
(links
(list (network-link
(name "enp4s0f1.3")
(type 'vlan)
(arguments '((id . 3)
(link . "enp4s0f1"))))
(network-link
(name "enp4s0f1.4")
(type 'vlan)
(arguments '((id . 4)
(link . "enp4s0f1"))))
(network-link
(name "enp4s0f1.5")
(type 'vlan)
(arguments '((id . 5)
(link . "enp4s0f1"))))
(network-link
(name "enp4s0f1.6")
(type 'vlan)
(arguments '((id . 6)
(link . "enp4s0f1"))))
(network-link
(name "enp4s0f1.2")
(type 'vlan)
(arguments '((id . 2)
(link . "enp4s0f1"))))))
(addresses
(list (network-address
(device "enp2s0")
(value "192.168.10.2/24"))
(network-address
(device "enp4s0f1.3")
(value "10.0.3.1/24"))
(network-address
(device "enp4s0f1.4")
(value "10.0.4.1/24"))
(network-address
(device "enp4s0f1.5")
(value "10.0.5.1/24"))
(network-address
(device "enp4s0f1.6")
(value "10.0.6.1/24"))
(network-address
(device "enp4s0f1.2")
(value "192.168.0.2/24")))))))
--8<---------------cut here---------------end--------------->8---
Also, may try without ‘(network-address (device "enp2s0") (value
"192.168.10.2/24"))’ block.
[…]
Regards,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Setting up multiple NICs
2023-11-29 7:39 ` Oleg Pykhalov
@ 2023-11-29 8:38 ` Lars Rustand
2023-12-02 23:34 ` rustand.lars
0 siblings, 1 reply; 12+ messages in thread
From: Lars Rustand @ 2023-11-29 8:38 UTC (permalink / raw)
To: Oleg Pykhalov; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 4812 bytes --]
On 23/11/29 10:39AM, Oleg Pykhalov wrote:
> I think this "management@enp4s0f1" syntax is not what is expected by the
> configuration.
I think this is the normal naming convention used for VLAN interfaces, at least
in normal distros. It is also what the interface gets named in the output of
`ip link` when I create a `network-link` called "management".
> You mentioned that you tried a development version manual. Did you try
> configuration similar to the example in that manual?
>
> https://guix.gnu.org/en/manual/devel/pt-br/html_node/Networking-Setup.html
>
> --8<---------------cut here---------------start------------->8---
> (static-networking
> (links (list (network-link
> (name "bond0")
> (type 'bond)
> (arguments '((mode . "802.3ad")
> (miimon . 100)
> (lacp-active . "on")
> (lacp-rate . "fast"))))
>
> (network-link
> (mac-address "98:11:22:33:44:55")
> (arguments '((master . "bond0"))))
>
> (network-link
> (mac-address "98:11:22:33:44:56")
> (arguments '((master . "bond0"))))
>
> (network-link
> (name "bond0.1055")
> (type 'vlan)
> (arguments '((id . 1055)
> (link . "bond0"))))))
> (addresses (list (network-address
> (value "192.168.1.4/24")
> (device "bond0.1055")))))
> --8<---------------cut here---------------end--------------->8---
Yes, that is the example I have based my config on.
> So your configuration would be like:
> --8<---------------cut here---------------start------------->8---
> (service static-networking-service-type
> (list (static-networking
> (links
> (list (network-link
> (name "enp4s0f1.3")
> (type 'vlan)
> (arguments '((id . 3)
> (link . "enp4s0f1"))))
> (network-link
> (name "enp4s0f1.4")
> (type 'vlan)
> (arguments '((id . 4)
> (link . "enp4s0f1"))))
> (network-link
> (name "enp4s0f1.5")
> (type 'vlan)
> (arguments '((id . 5)
> (link . "enp4s0f1"))))
> (network-link
> (name "enp4s0f1.6")
> (type 'vlan)
> (arguments '((id . 6)
> (link . "enp4s0f1"))))
> (network-link
> (name "enp4s0f1.2")
> (type 'vlan)
> (arguments '((id . 2)
> (link . "enp4s0f1"))))))
> (addresses
> (list (network-address
> (device "enp2s0")
> (value "192.168.10.2/24"))
> (network-address
> (device "enp4s0f1.3")
> (value "10.0.3.1/24"))
> (network-address
> (device "enp4s0f1.4")
> (value "10.0.4.1/24"))
> (network-address
> (device "enp4s0f1.5")
> (value "10.0.5.1/24"))
> (network-address
> (device "enp4s0f1.6")
> (value "10.0.6.1/24"))
> (network-address
> (device "enp4s0f1.2")
> (value "192.168.0.2/24")))))))
> --8<---------------cut here---------------end--------------->8---
Thanks, I tried that but it gave the same type of error. When trying to start
the networking service I get an error "#<&netlink-response-error errno: 17>",
which, from what I can tell, means file exists.
I think it might have problems creating multiple VLAN interfaces on the same NIC
for some reason.
Also, when using your config above, only one of the VLAN interfaces are created,
and it is named "enp4s0f1.3@enp4s0f1" in the output of `ip link`.
> Also, may try without ‘(network-address (device "enp2s0") (value
> "192.168.10.2/24"))’ block.
I can't do that, since this is the interface I use to log in to the machine.
And, this part is actually working, so there should be no reason to remove it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Setting up multiple NICs
2023-11-29 8:38 ` Lars Rustand
@ 2023-12-02 23:34 ` rustand.lars
2023-12-03 2:49 ` Felix Lechner via
0 siblings, 1 reply; 12+ messages in thread
From: rustand.lars @ 2023-12-02 23:34 UTC (permalink / raw)
To: Oleg Pykhalov; +Cc: help-guix
Now I changed it to a more minimal configuration like below, using only
real interfaces and no VLANs, but it still doesn't work. I get the same
error 17 like before.
--8<---------------cut here---------------start------------->8---
(service static-networking-service-type
(list (static-networking
(addresses
(list (network-address
(device "enp2s0")
(value "192.168.10.2/24"))
(network-address
(device "enp4s0f0")
(value "10.0.3.1/24"))
(network-address
(device "enp4s0f1")
(value "10.0.4.1/24"))
(network-address
(device "enp4s0f2")
(value "10.0.5.1/24"))
(network-address
(device "enp4s0f3")
(value "192.168.0.2/24")))))))
--8<---------------cut here---------------end--------------->8---
However, after a reboot all the IP addresses are set correctly, even
though the networking service has status failed.
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Setting up multiple NICs
2023-12-02 23:34 ` rustand.lars
@ 2023-12-03 2:49 ` Felix Lechner via
2023-12-03 4:43 ` Wojtek Kosior via
0 siblings, 1 reply; 12+ messages in thread
From: Felix Lechner via @ 2023-12-03 2:49 UTC (permalink / raw)
To: rustand.lars, Oleg Pykhalov; +Cc: help-guix
Hi Lars,
On Sun, Dec 03 2023, rustand.lars@gmail.com wrote:
> Now I changed it to a more minimal configuration like below, using only
> real interfaces and no VLANs, but it still doesn't work. I get the same
> error 17 like before.
On Linux, the static-network-service-type should create a file containing
"set-up-network" in its name [1]. Will you please locate it with
ls -ld /gnu/store/*set-up-network*
and post it here?
Kind regards
Felix
[1] https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/base.scm#n2881
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Setting up multiple NICs
2023-12-03 2:49 ` Felix Lechner via
@ 2023-12-03 4:43 ` Wojtek Kosior via
2023-12-07 7:50 ` rustand.lars
0 siblings, 1 reply; 12+ messages in thread
From: Wojtek Kosior via @ 2023-12-03 4:43 UTC (permalink / raw)
To: Felix Lechner via; +Cc: Felix Lechner, rustand.lars, Oleg Pykhalov
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
> On Linux, the static-network-service-type should create a file containing
> "set-up-network" in its name [1]. Will you please locate it with
>
> ls -ld /gnu/store/*set-up-network*
Btw, it might be even more convenient to do `ls -lhdct`. This will
list the items in order from newest to oldest (by real modification
time, not the fake one used by guix daemon)
Best :)
Wojtek
-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile
♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)
On Sat, 02 Dec 2023 18:49:55 -0800 Felix Lechner via <help-guix@gnu.org> wrote:
> Hi Lars,
>
> On Sun, Dec 03 2023, rustand.lars@gmail.com wrote:
>
> > Now I changed it to a more minimal configuration like below, using only
> > real interfaces and no VLANs, but it still doesn't work. I get the same
> > error 17 like before.
>
> On Linux, the static-network-service-type should create a file containing
> "set-up-network" in its name [1]. Will you please locate it with
>
> ls -ld /gnu/store/*set-up-network*
>
> and post it here?
>
> Kind regards
> Felix
>
> [1] https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/base.scm#n2881
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Setting up multiple NICs
2023-12-03 4:43 ` Wojtek Kosior via
@ 2023-12-07 7:50 ` rustand.lars
2023-12-07 16:56 ` Felix Lechner via
0 siblings, 1 reply; 12+ messages in thread
From: rustand.lars @ 2023-12-07 7:50 UTC (permalink / raw)
To: help-guix; +Cc: Felix Lechner, Oleg Pykhalov, Wojtek Kosior
Wojtek Kosior <koszko@koszko.org> writes:
>> On Linux, the static-network-service-type should create a file containing
>> "set-up-network" in its name [1]. Will you please locate it with
>>
>> ls -ld /gnu/store/*set-up-network*
>
> Btw, it might be even more convenient to do `ls -lhdct`. This will
> list the items in order from newest to oldest (by real modification
> time, not the fake one used by guix daemon)
Sure here is the list of files:
--8<---------------cut here---------------start------------->8---
-r--r--r-- 1 root root 1.3K Dec 7 08:44 /gnu/store/g64r168i3v4yiqb0cd32pc7yqggx56wr-set-up-network
-r--r--r-- 1 root root 1.9K Dec 7 08:44 /gnu/store/y0r29f5i9qzhykvx42w9ddwccsv9f2mc-set-up-network
-r--r--r-- 1 root root 2.1K Dec 7 08:44 /gnu/store/2v6q6r2qybdz36sfdpiv9ll2k411wwfv-set-up-network-builder
-r--r--r-- 1 root root 936 Dec 7 08:44 /gnu/store/7vn4rdsln9kr60j8fj3afadkrj9254fj-set-up-network.drv
-r--r--r-- 1 root root 1.3K Dec 7 08:39 /gnu/store/2fal9d49xlwfisicp59kbvk6qgryawyh-set-up-network
-r--r--r-- 1 root root 1.6K Dec 3 01:05 /gnu/store/viakdpgib14a0acsvaqb1wiiny38x7vd-set-up-network
-r--r--r-- 1 root root 1.9K Dec 3 00:49 /gnu/store/748zg4c04r716wfdzr46rrgf1p0rh3gp-set-up-network
-r--r--r-- 1 root root 2.0K Dec 3 00:08 /gnu/store/95nwcggb4si3ni714jajm8dwvmchfrlm-set-up-network-builder
-r--r--r-- 1 root root 936 Dec 3 00:08 /gnu/store/f49na8slabsx66xmwbbgmn7siaqd7cwf-set-up-network.drv
-r--r--r-- 1 root root 2.1K Dec 3 00:02 /gnu/store/3gpmwcymbyawy798x9jh5c50yq9l1lpa-set-up-network
-r--r--r-- 1 root root 2.2K Dec 3 00:02 /gnu/store/qrpy1m7v2nhpsrmhssv92b4qq5042ia2-set-up-network-builder
-r--r--r-- 1 root root 936 Dec 3 00:02 /gnu/store/41gww72b45kwqi5gda8r0l2j75nl3x7b-set-up-network.drv
-r--r--r-- 1 root root 1.5K Nov 29 10:04 /gnu/store/njnka38xz6wpg7yrkl9fzbhhnz5fggmy-set-up-network
-r--r--r-- 1 root root 1.6K Nov 29 09:51 /gnu/store/f6j5cca8d0spl66q80r5yvv4p8iiy02j-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 29 09:51 /gnu/store/dq0x3nlybh3vf79zm23hphxagib839vz-set-up-network.drv
-r--r--r-- 1 root root 2.1K Nov 29 09:46 /gnu/store/gdkzqpiqk9xc3z0n0cq1vvmznm1cl3rs-set-up-network
-r--r--r-- 1 root root 2.2K Nov 29 09:45 /gnu/store/8d2cy47462nc1ngn8vwpa6n2ydkl8zf0-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 29 09:45 /gnu/store/h5hiaxm9vxlvfm22d1p218l8jlqjg03s-set-up-network.drv
-r--r--r-- 1 root root 2.8K Nov 29 09:12 /gnu/store/vyq6sbny5g0kb4d29jgj4lvrk2wiars9-set-up-network
-r--r--r-- 1 root root 2.9K Nov 29 09:11 /gnu/store/qcxq1ki3ajyjghc6hrj9jc7cxdj3gszp-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 29 09:10 /gnu/store/wk6k6mn6ihip2cv043b3c9hlhfkqgwys-set-up-network.drv
-r--r--r-- 1 root root 2.5K Nov 23 19:48 /gnu/store/frmq7p9fqkifp6k4zag21zz7qn1jvb64-set-up-network
-r--r--r-- 1 root root 2.7K Nov 23 19:48 /gnu/store/vkg6079rr3k8rdyacqyr6fhwjx06gdfx-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 19:48 /gnu/store/967zsmd46wyvahb4gp54h23j88nnxh7x-set-up-network.drv
-r--r--r-- 1 root root 2.1K Nov 23 19:47 /gnu/store/sazxsclh6fj4475xsxck48yrrfr5jadz-set-up-network
-r--r--r-- 1 root root 2.3K Nov 23 19:46 /gnu/store/dzfiyqx3wsx70hn0jdf1bkdmnn6bi0s5-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 19:46 /gnu/store/0pzwyvlkhx0ayk1d6vh3bagixi440cvj-set-up-network.drv
-r--r--r-- 1 root root 1.5K Nov 23 19:44 /gnu/store/amppm2x57hv3b295qamj9mnnpny2pqf8-set-up-network
-r--r--r-- 1 root root 1.6K Nov 23 19:44 /gnu/store/fqcpbwwjq22imylnwl5axjn4hk73w9s7-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 19:44 /gnu/store/1k4h2mjdrxlaxvcg2c5wcn7c943pd5xl-set-up-network.drv
-r--r--r-- 1 root root 1.5K Nov 23 19:41 /gnu/store/5ssj3xpnyya8l087plv7kn9iddjiyi5l-set-up-network
-r--r--r-- 1 root root 1.6K Nov 23 19:40 /gnu/store/1s82g30dr2mpc45awsaqpvb3dz6dwyih-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 19:40 /gnu/store/l8lw2cfp4caylrwl1ynmmrn2xp3w64s0-set-up-network.drv
-r--r--r-- 1 root root 1.6K Nov 23 19:39 /gnu/store/9rppan8sc1mkmlhwjfpq9b9mv25gia41-set-up-network
-r--r--r-- 1 root root 1.7K Nov 23 19:39 /gnu/store/cs4mlsncckmnbi2p73s6ih7n1d3rwfxp-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 19:39 /gnu/store/l92yy1xacsj01p768smxq2wfwvlgpm19-set-up-network.drv
-r--r--r-- 1 root root 1.6K Nov 23 19:33 /gnu/store/nipniyr23x74n33sww7q212lwd51v240-set-up-network
-r--r--r-- 1 root root 1.8K Nov 23 19:33 /gnu/store/3pnsqw2yky6f5nh2jq8v1ajkp9zp5fsx-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 19:33 /gnu/store/4cqh9fypw9qwq9imw3mngcmvw6p4ql0k-set-up-network.drv
-r--r--r-- 1 root root 1.8K Nov 23 11:08 /gnu/store/p2qv18daak55nrgjf4n4n1w4d7pjd5rj-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 11:07 /gnu/store/9n7nci7c448jlcfqfka2hcjv6f105a0q-set-up-network.drv
-r--r--r-- 1 root root 1.5K Nov 23 09:40 /gnu/store/ba25d8yv1qa5mvml5j2db7541x5f2vjf-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 09:40 /gnu/store/3lxb8p3iqgb9fvir8hqbzkyq9b0mvs20-set-up-network.drv
-r--r--r-- 1 root root 2.8K Nov 23 09:34 /gnu/store/9d9my2yrizxc79l84vvplrnajcdnqcg2-set-up-network
-r--r--r-- 1 root root 2.9K Nov 23 09:28 /gnu/store/2vqr58kayx910xz3rsvlc7lj3rz0l0i5-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 23 09:28 /gnu/store/6jkanggpg3r1s2j268hp2vb6fpdvjvba-set-up-network.drv
-r--r--r-- 1 root root 2.7K Nov 23 09:21 /gnu/store/3pkaka6wq19swgi2yxrb0lri8nlqwxi5-set-up-network
-r--r--r-- 1 root root 918 Nov 23 00:00 /gnu/store/fk6slzbvqwfvg7ici782sic0yp05b4nf-set-up-network
-r--r--r-- 1 root root 2.1K Nov 23 00:00 /gnu/store/pckmy79lban5fh6nin51says81jlhj9w-set-up-network
-r--r--r-- 1 root root 2.3K Nov 22 23:58 /gnu/store/mqvv4amw0lj7za3bg9n8vcz0r5j7ky5s-set-up-network-builder
-r--r--r-- 1 root root 1.1K Nov 22 23:58 /gnu/store/f1ahmarg3nzhq3dk7848vn8pzw1znccp-set-up-network-builder
-r--r--r-- 1 root root 930 Nov 22 23:43 /gnu/store/j1lpfpz1ksbxyg8ykwyjgxg855n66raj-set-up-network.drv
-r--r--r-- 1 root root 930 Nov 22 23:43 /gnu/store/y5bi5a1pwd2qkw0aznfc87g7f13zm819-set-up-network.drv
-r--r--r-- 1 root root 936 Nov 22 22:02 /gnu/store/i16kkanalxhddszqyy931lnkz7r1wh27-set-up-network.drv
-r--r--r-- 1 root root 936 Nov 22 22:02 /gnu/store/jpxr76hv6w6if52j9l7vgfi0y80rr3s0-set-up-network.drv
-r--r--r-- 1 root root 1.4K Nov 22 21:16 /gnu/store/qm7kk3msk6rd12q2ssviqay1jmvrc81w-set-up-network-builder
-r--r--r-- 1 root root 2.9K Nov 22 21:16 /gnu/store/y6rmw1wdi8xj6yll6hkfdflgakd9a1rm-set-up-network-builder
-r--r--r-- 1 root root 936 Nov 22 21:01 /gnu/store/ggcg18gpac9zd4l183617jb188y4gasy-set-up-network.drv
-r--r--r-- 1 root root 936 Nov 22 21:01 /gnu/store/17gqgb342ynid20h0p0zmiwnrp6kxlbm-set-up-network.drv
-r--r--r-- 1 root root 884 Nov 21 21:56 /gnu/store/4j8vdqrxsbfjxqcl62kn4xl4fdp9ysc1-set-up-network
--8<---------------cut here---------------end--------------->8---
And this is the contents of the newest one:
--8<---------------cut here---------------start------------->8---
(eval-when (expand load eval) (let ((extensions (quote ("/gnu/store/1wg092wqd4041n7k11g17machlmpb5w0-guile-netlink-1.2.1"))) (prepend (lambda (items lst) (let loop ((items items) (lst lst)) (if (null? items) lst (loop (cdr items) (cons (car items) (delete (car items) lst)))))))) (set! %load-path (prepend (cons "/gnu/store/9970qxhisnrr8cq4rq25zrc4698b037b-module-import" (map (lambda (extension) (string-append extension "/share/guile/site/" (effective-version))) extensions)) %load-path)) (set! %load-compiled-path (prepend (cons "/gnu/store/pp2cqdcpaxvw3fka3d6d16c0q9yz37d5-module-import-compiled" (map (lambda (extension) (string-append extension "/lib/guile/" (effective-version) "/site-ccache")) extensions)) %load-compiled-path))))(begin (use-modules (ip addr) (ip link) (ip route) (srfi srfi-1) (ice-9 format) (ice-9 match)) (define (match-link-by field-accessor value) (fold (lambda (link result) (if (equal? (field-accessor link) value) link result)) #f (get-links))) (define (alist->keyword+value alist) (fold (match-lambda* (((k . v) r) (cons* (symbol->keyword k) v r))) (quote ()) alist)) #f (begin (wait-for-link "lo" #:blocking? #f) (addr-add "lo" "127.0.0.1/8" #:ipv6? #f) (link-set "lo" #:multicast-on #t #:up #t))
--8<---------------cut here---------------end--------------->8---
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Setting up multiple NICs
2023-12-07 7:50 ` rustand.lars
@ 2023-12-07 16:56 ` Felix Lechner via
0 siblings, 0 replies; 12+ messages in thread
From: Felix Lechner via @ 2023-12-07 16:56 UTC (permalink / raw)
To: rustand.lars, help-guix; +Cc: Oleg Pykhalov, Wojtek Kosior
Hi Lars,
On Thu, Dec 07 2023, rustand.lars@gmail.com wrote:
> And this is the contents of the newest one:
Actually, I think we need the output of that code when it is being
evaluated. Unfortunately, I do not know how to do that.
Alternatively, we could perhaps look for the output file, if you can
find it. Or maybe it's a goose chase, and someone else can help you
better instead.
Kind regards
Felix
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Setting up multiple NICs
2023-11-29 6:26 Setting up multiple NICs Lars Rustand
2023-11-29 7:39 ` Oleg Pykhalov
@ 2023-12-07 20:22 ` Lars Rustand
1 sibling, 0 replies; 12+ messages in thread
From: Lars Rustand @ 2023-12-07 20:22 UTC (permalink / raw)
To: help-guix
Lars Rustand <rustand.lars@gmail.com> writes:
> Sure, this is what I have at the moment:
>
> (service static-networking-service-type
> (list (static-networking
> (links
> (list (network-link
> (name "dmz")
> (type 'vlan)
> (arguments '((id . 3)
> (link . "enp4s0f1"))))
> (network-link
> (name "home")
> (type 'vlan)
> (arguments '((id . 4)
> (link . "enp4s0f1"))))
> (network-link
> (name "iot")
> (type 'vlan)
> (arguments '((id . 5)
> (link . "enp4s0f1"))))
> (network-link
> (name "server")
> (type 'vlan)
> (arguments '((id . 6)
> (link . "enp4s0f1"))))
> (network-link
> (name "management")
> (type 'vlan)
> (arguments '((id . 2)
> (link . "enp4s0f1"))))))
> (addresses
> (list (network-address
> (device "enp2s0")
> (value "192.168.10.2/24"))
> (network-address
> (device "dmz@enp4s0f1")
> (value "10.0.3.1/24"))
> (network-address
> (device "home@enp4s0f1")
> (value "10.0.4.1/24"))
> (network-address
> (device "iot@enp4s0f1")
> (value "10.0.5.1/24"))
> (network-address
> (device "server@enp4s0f1")
> (value "10.0.6.1/24"))
> (network-address
> (device "management@enp4s0f1")
> (value "192.168.0.2/24")))))))
I tried the above configuration on a different machine and it worked
slightly better there. All the VLAN interfaces were created, but no
addresses were set up. The networking service hangs indefinitely on restart.
So, it seems that there is at least some problem with one of my
machines, and I am unsure whether there is any error in the
configuration. Could anyone test if they are able to apply a similar
configuration on their machine?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Setting up multiple NICs
@ 2023-11-23 9:11 Lars Rustand
2023-11-24 3:08 ` Oleg Pykhalov
2023-11-29 17:33 ` Felix Lechner via
0 siblings, 2 replies; 12+ messages in thread
From: Lars Rustand @ 2023-11-23 9:11 UTC (permalink / raw)
To: help-guix
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Hello!
I'm trying to set up Guix on my "router", but I'm not able to get my networking
setup to work. What I need is one upstream NIC, and one downstream NIC which is
split into multiple VLANs.
I've tried to different approaches:
1. Have everything inside of one `static-networking` form.
2. Have one `static-networking` form for each VLAN.
If I specify multiple `static-networking` forms I get the error "guix system:
error: service 'networking' provided more than once".
If I instead put them all in the same `static-networking` form, at least the
system happily reconfigures, but I instead get failures of the networking
service.
I found one example of a more advanced networking config in the devel version of
the manual, but this one does not show multiple VLANs, but it does show multiple
links in the same `static-networking` to build a bond interface.
So, what is the correct way to setup a multi NIC networking with multiple VLANs?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Setting up multiple NICs
2023-11-23 9:11 Lars Rustand
@ 2023-11-24 3:08 ` Oleg Pykhalov
2023-11-29 17:33 ` Felix Lechner via
1 sibling, 0 replies; 12+ messages in thread
From: Oleg Pykhalov @ 2023-11-24 3:08 UTC (permalink / raw)
To: Lars Rustand; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hello,
Lars Rustand <rustand.lars@gmail.com> writes:
[…]
> If I instead put them all in the same `static-networking` form, at least the
> system happily reconfigures, but I instead get failures of the networking
> service.
Could you show the configuration, please? Also, a list of the networking
devices with ‘ip -one link’ and ‘ip -one address’ command would be
helpful for cathing an error.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Setting up multiple NICs
2023-11-23 9:11 Lars Rustand
2023-11-24 3:08 ` Oleg Pykhalov
@ 2023-11-29 17:33 ` Felix Lechner via
1 sibling, 0 replies; 12+ messages in thread
From: Felix Lechner via @ 2023-11-29 17:33 UTC (permalink / raw)
To: Lars Rustand, help-guix
Hi Lars,
On Thu, Nov 23 2023, Lars Rustand wrote:
> the correct way to setup a multi NIC networking
On a tangent, you may be interested in my patch allowing MAC-bases
interface names in GNU Guix. [1]
A fixed naming scheme that is independent of BIOS enumeration could help
prevent the inadvertent exposure of your network after making unrelated
hardware changes.
Kind regards
Felix
[1] https://issues.guix.gnu.org/63508#3
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2023-12-07 20:28 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-29 6:26 Setting up multiple NICs Lars Rustand
2023-11-29 7:39 ` Oleg Pykhalov
2023-11-29 8:38 ` Lars Rustand
2023-12-02 23:34 ` rustand.lars
2023-12-03 2:49 ` Felix Lechner via
2023-12-03 4:43 ` Wojtek Kosior via
2023-12-07 7:50 ` rustand.lars
2023-12-07 16:56 ` Felix Lechner via
2023-12-07 20:22 ` Lars Rustand
-- strict thread matches above, loose matches on Subject: below --
2023-11-23 9:11 Lars Rustand
2023-11-24 3:08 ` Oleg Pykhalov
2023-11-29 17:33 ` Felix Lechner via
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).