Lars Rustand writes:
> Sure, this is what I have at the moment:
>
> (service static-networking-service-type
> (list (static-networking
> (links
> (list (network-link
> (name "dmz")
>
Hi Lars,
On Thu, Dec 07 2023, rustand.l...@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 c
Wojtek Kosior 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 it
> 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
Hi Lars,
On Sun, Dec 03 2023, rustand.l...@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 c
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-n
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 inadverten
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 lin
Lars Rustand writes:
[…]
> Sure, this is what I have at the moment:
>
> (service static-networking-service-type
> (list (static-networking
> (links
> (list
> ;; ...
> (network-l
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
Hello,
Lars Rustand 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 l
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
12 matches
Mail list logo
