problem setting up a secondary network cnnection.

huhn · 2025-11-11 15:18:51

this post is in violation of the general posting rules.

PACMAN -Syu can not be run and the current system is very outdated running this will disable the function of the system cause ZFS. it will stop working and that's the only reason i'm not doing it. anyway...

yuanley AQC113-x1 (they use marvel AQC113 driver on windows)

i just got my self 10 gb cards and i want to do a direct connection with another windows pc.
it seems to be plug and play i now have these.

1: lo: <LOOPBACK,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: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mo                                                                                                                                                             de DEFAULT group default qlen 1000
    link/ether a8:a1:59:07:dd:d1 brd ff:ff:ff:ff:ff:ff
3: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT gro                                                                                                                                                             up default qlen 1000
    link/ether 1a:4b:24:c6:c6:80 brd ff:ff:ff:ff:ff:ff

enp6s0 should be the new card and no new driver seems to be needed nice

enps9s0 uses this:

/etc/netctl/ethernet-dhcp
Description='A basic dhcp ethernet connection'
Interface=enp9s0
Connection=ethernet
IP=dhcp
sDHCPClient=dhcpcd
#DHCPReleaseOnStop=no
## for DHCPv6
#IP6=dhcp
#DHCP6Client=dhclient
## for IPv6 autoconfiguration
#IP6=stateless

and this works fine

i tried enps6s0 with this:

/etc/netctl/10gb
Description='crossover'
Interface=enp6s0
Connection=ethernet
IP=static
Address=('192.168.1.101/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')

1by1 copy with a changed ip address

this is supposed to be a simple crossover connection no DHCP no switch no nothing.

so i run this

systemctl status netctl@10gb.service
× netctl@10gb.service - Networking for netctl profile 10gb
     Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
     Active: failed (Result: exit-code) since Tue 2025-11-11 15:17:52 UTC; 20s ago
       Docs: man:netctl.profile(5)
    Process: 933 ExecStart=/usr/lib/netctl/network start 10gb (code=exited, status=1/FAILURE)
   Main PID: 933 (code=exited, status=1/FAILURE)
        CPU: 248ms

Nov 11 15:17:47 Gundam2 systemd[1]: Starting Networking for netctl profile 10gb...
Nov 11 15:17:47 Gundam2 network[933]: Starting network profile '10gb'...
Nov 11 15:17:52 Gundam2 network[933]: No connection found on interface 'enp6s0' (timeout)
Nov 11 15:17:52 Gundam2 network[933]: Failed to bring the network up for profile '10gb'
Nov 11 15:17:52 Gundam2 systemd[1]: netctl@10gb.service: Main process exited, code=exited, status=1/FAILURE
Nov 11 15:17:52 Gundam2 systemd[1]: netctl@10gb.service: Failed with result 'exit-code'.
Nov 11 15:17:52 Gundam2 systemd[1]: Failed to start Networking for netctl profile 10gb.

so i'm assuming now that enp6s0 is not the new card but something different.
i need to install drivers which is going to be interesting.
crossover connection needs special setup or are not supported by netctl the netctl arch wiki page doesn't have the word crossover.
the information that the cards can do auto crossover like any adapter produce in the last 10 years is false and i need a crossover cable.

any ideas?

huhn · 2025-11-11 18:55:13

[root@Gundam2 Linux]# make
make -j4 -C /lib/modules/6.6.29-1-lts/build M="/mnt/huhn/netdriver/Linux" module                                     s
make[1]: Entering directory '/mnt/huhn/netdriver/Linux'
make[1]: *** /lib/modules/6.6.29-1-lts/build: No such file or directory.  Stop.
make[1]: Leaving directory '/mnt/huhn/netdriver/Linux'
make: *** [Makefile:36: all] Error 2
[root@Gundam2 Linux]# pacman -S  linux-headers

warning: linux-headers-6.17.7.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-headers-6.17.7.arch1-1

Total Installed Size:  251.51 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                     [######################] 100%
(0/1) checking package integrity                   [----------------------]   0%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) reinstalling linux-headers                   [######################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating module dependencies...
[root@Gundam2 Linux]#
[root@Gundam2 Linux]# pacman -S  linux-headers-lts
error: target not found: linux-headers-lts
[root@Gundam2 Linux]# pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra                                       8.0 MiB  14.5 MiB/s 00:01 [#######################################] 100%
 archzfs is up to date
:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "zfs-utils=2.3.2", a dependency of "zfs-linux-lts"
warning: cannot resolve "linux-lts=6.12.29-1", a dependency of "zfs-linux-lts"
:: The following package cannot be upgraded due to unresolvable dependencies:
      zfs-linux-lts

:: Do you want to skip the above package for this upgrade? [y/N]

so pacman just installs stuff for a kernel it knows i do not have making the install impossible without bricking my system at least temporary.
it wants a package called build-essential which is maybe base-devel because we can not have nice things i guess.

Building and Installation
=========================

To manually build this driver:
------------------------------------------------------------
1. Make sure you have all the packages required to build a standalone kernel
   module.
   On a debian-based systems you should at least install the following packages:

	sudo apt install linux-headers build-essential

2. Move the base driver tar file to the directory of your choice.
   For example, use /home/username/aquantia.
   Untar/unzip archive:

	cd ~/aquantia
	tar zxf Aquantia-AQtion-x.y.z.tar.gz

3. Change to the driver src directory:

	cd Aquantia-AQtion-x.y.z/

NB! Make sure that pathname doesn't contain whitespaces and special characters
    (e.g. brackets), because kernel build system doesn't support such paths
    unfortunately and the build will fail.

4. Compile the driver module:
	make

5. Unload the driver, if an older version is in use:
	sudo rmmod atlantic

5. Load the dependencies and the module itself:
	sudo make load

7. Install the driver
	sudo make install

the driver with that instruction is in atlantic.tar.gz not what ever they talk about and the decompressed archive is in Linux not what ever they talk about.

Last edited by huhn (2025-11-11 18:55:47)

huhn · 2026-01-08 12:19:24

i replaced the card with a Intel X550-T2

ip link show
1: lo: <LOOPBACK,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: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:07:dd:d1 brd ff:ff:ff:ff:ff:ff
3: enp10s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 50:7c:6f:5e:e8:1c brd ff:ff:ff:ff:ff:ff
4: enp10s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 50:7c:6f:5e:e8:1d brd ff:ff:ff:ff:ff:ff

tried my luck in the level one forum and it seems like my question has sadly yet again no answer.

my problem now is that i want to do a crossover connection with another PC and at best host a DHCP server on nas arch system only for the intel nic.
i can't find anything about crossover connection in netctl and this is an insanely rare setup these days. so i do not even know where to start.

on windows i define a ip put a cable in and that's it.

seth · 2026-01-08 15:23:28

Address=('192.168.1.101/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')

You configured a gateway in a different segment than the assigned static IP…
Is there even a DNS or gateway on 10.1.10.1 ?

What is the plan here (in layman terms you understand)?
Do you want the system to be connected to two different networks (one being the router and the other being some isolated host)?
Do you want to share the internet from one system with the other?
What is the IP of the windows host (see "ipconfig /all")?
Does 192.168.1.101/24 overlap w/ the range of the other nic?

ip a; ip r

huhn · 2026-01-08 16:50:43

seth wrote:

Address=('192.168.1.101/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')
You configured a gateway in a different segment than the assigned static IP…
Is there even a DNS or gateway on 10.1.10.1 ?

that is just an test to get the old new nic working which has been removed this isn't used anymore all of this is just copied directly from the wiki:

Interface=enp1s0
Connection=ethernet
IP=static
Address=('10.1.10.2/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')

i couldn't even get the driver to install. zfs kernel linux header firmware conflict just ignore it the new intel nic works out of the box. the 10 gb can come later if that isn't working

What is the plan here (in layman terms you understand)?

i want to do this: https://en.wikipedia.org/wiki/Crossover_cable
no router no nothing just 2 PC directly connected like with a crossover cable.

Do you want the system to be connected to two different networks (one being the router and the other being some isolated host)?

yes

Do you want to share the internet from one system with the other?

no smb only

What is the IP of the windows host (see "ipconfig /all")?

nothing it is on DHCP request and i want the DHCP server on the arch linux nas if possible.

ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-FK9CR8I
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell AQtion 10Gbit Network Adapter
Physical Address. . . . . . . . . : 1A-4B-24-B6-76-77
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7a3b:4c57:4cd9:5f67%3(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.145.69(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 52054820
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2F-8C-8A-9B-A8-A1-59-4C-02-CC
DNS Servers . . . . . . . . . . . : 2a02:908:2:b::1
2a02:908:2:a::1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter 1000mb:
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : A8-A1-59-4C-02-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:908:d12:*(Preferred)
Temporary IPv6 Address. . . . . . :2a02:908:d12:*(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:908:d12:*(Deprecated)
Link-local IPv6 Address . . . . . : fe80::314b:f6fb:9ea0:e0e6%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, 8 January 2026 17:30:59
Lease Expires . . . . . . . . . . : Thursday, 8 January 2026 18:30:58
Default Gateway . . . . . . . . . : fe80::3a43:7dff:fe12:f866%15
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 94937433
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2F-8C-8A-9B-A8-A1-59-4C-02-CC
DNS Servers . . . . . . . . . . . : 2a02:908:2:b::1
2a02:908:2:a::1
192.168.0.1
2a02:908:2:b::1
2a02:908:2:a::1
NetBIOS over Tcpip. . . . . . . . : Enabled

the marvel 10 gb was connected to the router for a test that's why there is stuff in there it isn't anymore.

Does 192.168.1.101/24 overlap w/ the range of the other nic?

that profile isn't used anymore.

ip a; ip r

ip a; ip r~
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether a8:a1:59:07:dd:d1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.45/24 brd 192.168.0.255 scope global dynamic noprefixroute enp9s0
       valid_lft 2780sec preferred_lft 2330sec
    inet6 2a02:908:d12:7a40:aaa1:59ff:fe07:ddd1/64 scope global dynamic mngtmpaddr proto kernel_ra
       valid_lft 73189sec preferred_lft 73189sec
    inet6 fe80::aaa1:59ff:fe07:ddd1/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
3: enp10s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 50:7c:6f:5e:e8:1c brd ff:ff:ff:ff:ff:ff
4: enp10s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 50:7c:6f:5e:e8:1d brd ff:ff:ff:ff:ff:ff
Object "r~" is unknown, try "ip help".

Last edited by huhn (2026-01-08 20:53:34)

seth · 2026-01-08 20:23:54

The lines w/ "2a02:908:d12:*" expose a globally routable IPv6 (Germany, football club is a bee hive) - you want to obfuscate those.
---------------------

Object "r~" is unknown, try "ip help".

You typo'd a "~" in there…

i couldn't even get the driver to install

What "driver" are you talking about? The NICs showing up in "ip a" suggest they generally work.
You could try to connect to your router w/ one of them to establish their principal functionality.

that is just an test to get the old new nic working which has been removed … that profile isn't used anymore.

Then what is the actual config you're currently attempting?
Cause

Interface=enp1s0
Connection=ethernet
IP=static
Address=('10.1.10.2/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')

certainly doesn't match your HW (there's no enp1s0)

The windows host also has two NICs
The realtek one is also in the 192.168.0.1/24 segment, the marvell one only has link local IPs and no affiliation w/ the 10.1.10.1/24 segment.

------------
Ftr, this here https://en.wikipedia.org/wiki/Ethernet_crossover_cable is no longer a (special) thing w/ GBit connections, I hope you didn't plug a cat4 crosslink cable between them

huhn · 2026-01-08 20:52:16

seth wrote:

The lines w/ "2a02:908:d12:*" expose a globally routable IPv6 (Germany, football club is a bee hive) - you want to obfuscate those.

i don't have a static ip and i'm not a football club either shouldn't be to bad. but sure why not.

Object "r~" is unknown, try "ip help".
You typo'd a "~" in there…

was copy past so hmmmm

ip a; ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether a8:a1:59:07:dd:d1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.45/24 brd 192.168.0.255 scope global dynamic noprefixroute enp9s0
       valid_lft 3307sec preferred_lft 2857sec
    inet6 2a02:908:d12:7a40:aaa1:59ff:fe07:ddd1/64 scope global dynamic mngtmpaddr proto kernel_ra
       valid_lft 81072sec preferred_lft 81072sec
    inet6 fe80::aaa1:59ff:fe07:ddd1/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
3: enp10s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 50:7c:6f:5e:e8:1c brd ff:ff:ff:ff:ff:ff
4: enp10s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 50:7c:6f:5e:e8:1d brd ff:ff:ff:ff:ff:ff
default via 192.168.0.1 dev enp9s0 proto dhcp src 192.168.0.45 metric 1002
192.168.0.0/24 dev enp9s0 proto dhcp scope link src 192.168.0.45 metric 1002

i couldn't even get the driver to install
What "driver" are you talking about? The NICs showing up in "ip a" suggest they generally work.
You could try to connect to your router w/ one of them to establish their principal functionality.

the card isn't in the PC anymore: https://www.marvell.com/content/dam/mar … 2.5.12.zip
edit: they don't like these links so: https://www.marvell.com/support/downloads.html
aqc113 i have Linux_2.5.12 here which doesn't exist anymore and Linux_2.5.14 is already 8 month old so i don't know how i did that...

i just wrote that because i like to answer question if i can you should still absolutely ignore that. /edit

IGNORE IT this was the original issue. the card was shown but not working and the driver couldn't be compiled.
which as you may now noticed is a bit much for me.

that is just an test to get the old new nic working which has been removed … that profile isn't used anymore.
Then what is the actual config you're currently attempting?

none i don't know how to do a netctl config for a connection providing DHCP and having an IP.

best guess is just typing any IP in there as i pleases and go from there. and i have absolutely no clue how to provide DHCP none.

Cause
Interface=enp1s0
Connection=ethernet
IP=static
Address=('10.1.10.2/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')
certainly doesn't match your HW (there's no enp1s0)

that's 1to1 from the wiki mine has enp6s0 which doesn't exist anymore. and can be ignored now.

The windows host also has two NICs
The realtek one is also in the 192.168.0.1/24 segment, the marvell one only has link local IPs and no affiliation w/ the 10.1.10.1/24 segment.

192.168.0.x is the internet router.
the marvell is currently directly connected to the nas intel 10 GB card nothing in-between.
where it got "Autoconfiguration IPv4 Address. . : 169.254.145.69(Preferred)" from is beyond me.
my router can't even go outside of 192.168.0.x utter mystery to me.

the marvel should be blank for now until the intel nic works and has a DHCP server.

Ftr, this here https://en.wikipedia.org/wiki/Ethernet_crossover_cable is no longer a (special) thing w/ GBit connections, I hope you didn't plug a cat4 crosslink cable between them

normal cat 7 i know that:-). but i still own a 25 year old crossover cable somewhere!

Last edited by huhn (2026-01-08 21:00:46)

seth · 2026-01-08 21:38:27

Where in https://bbs.archlinux.org/viewtopic.php … 4#p2282064 did you copy "ip r~"?

and i have absolutely no clue how to provide DHCP none.

https://wiki.archlinux.org/title/Kea - but you don't want to introduce a second dhcp server.
Certainly not into the same segment (192.168.0.0/24) and it's over-complicating the secondary connection (you'll have to select which NIC to use for what dhcp request and I don't even know whether that's possible on windows)
Configure (different) static IPs for the same segment (10.1.10.0/24 would be fine) on the windows and linux host and make sure traffic to that segment is routed via those NICs

enp6s0 which doesn't exist anymore. and can be ignored now.

No, but enp10s0f0 and enp10s0f1 do

where it got "Autoconfiguration IPv4 Address. . : 169.254.145.69(Preferred)" from is beyond me.

https://en.wikipedia.org/wiki/Link-local_address

huhn · 2026-01-08 22:11:16

seth wrote:

Where in https://bbs.archlinux.org/viewtopic.php … 4#p2282064 did you copy "ip r~"?

i copied your command and it was defiantly not there.
and i have a german keyboard i can't do a ~ without alt... on top of that i used putty where paste is right mouse sooooo let's just move on.

and i have absolutely no clue how to provide DHCP none.
https://wiki.archlinux.org/title/Kea - but you don't want to introduce a second dhcp server.
Certainly not into the same segment (192.168.0.0/24) and it's over-complicating the secondary connection (you'll have to select which NIC to use for what dhcp request and I don't even know whether that's possible on windows)
Configure (different) static IPs for the same segment (10.1.10.0/24 would be fine) on the windows and linux host and make sure traffic to that segment is routed via those NICs

you completely understand my problem that's why i didn't even played around with that.

for windows that shouldn't be an issue because that's the client and each card can have a different server by default.
but for the linux system the DHCP server has be limited to the intel nic and nothing else.
and that's why i can not just try it out the second DHCP server could mess the system up and even the network.

i would still like to do that but kinda niche isn't it?
so static try 10.1.10.2/24 and 10.1.10.3/24 and see what happens?

after that i can figure the 10 gb stuff out it is currently 1 on the arch system even through i do not like that setup at all.

enp6s0 which doesn't exist anymore. and can be ignored now.
No, but enp10s0f0 and enp10s0f1 do

yes and that tells me the intel is at least partial working!

where it got "Autoconfiguration IPv4 Address. . : 169.254.145.69(Preferred)" from is beyond me.
https://en.wikipedia.org/wiki/Link-local_address

i see.

edit:

systemctl status netctl
○ netctl.service - (Re)store the netctl profile state
     Loaded: loaded (/us
r/lib/systemd/system/netctl.service; disabled; preset:
disabled)
     Active: inactive (dead)
       Docs: man:netctl.special(7)
[root@Gundam2 ~]# systemctl status netctl@10gb.service
× netctl@10gb.service - crossover
     Loaded: loaded (/u
sr/lib/systemd/system/netctl@.service; enabled; preset:
disabled)
    Drop-In: /etc/systemd/system/netctl@10gb.service.d
             └─
               le.confprofile.conf
     Active: failed (Result: exit-code) since Thu 2026-01-08 22:22:11
 UTC; 3min 47s ago
   Duration: 748ms
       Docs: man:netctl.profile(5)
    Process: 767 ExecStart=/usr/lib/netctl/network start 10gb (code=exit
ed, status=1/FAILURE)
   Main PID: 767 (code=exited, status=1/FAILURE)
        CPU: 198ms

Jan 08 22:22:04 Gundam2 systemd[1]: Starting crossover...
Jan 08 22:22:04 Gundam2 network[767]: Starting network profile '10gb'...
Jan 08 22:22:10 Gundam2 systemd[1]: Started crossover.
Jan 08 22:22:10 Gundam2 resolvconf[881]: Failed to set D
NS configuration: Could not activate remote peer 'org.freedesktop.resolve1': act
ivation request failed: unknown unit
Jan 08 22:22:10 Gundam2 systemd[1]: netctl@1
0gb.service: Got notification message from PID 881, but reception only permitted
 for main PID 767
Jan 08 22:22:10 Gundam2 systemd[1]: netctl@1
0gb.service: Got notification message from PID 881, but reception only permitted
 for main PID 767
Jan 08 22:22:11 Gundam2 network[767]: Failed to bring th
e network up for profile '10gb'
Jan 08 22:22:11 Gundam2 systemd[1]: netctl@10gb.service:
 Main process exited, code=exited, status=1/FAILURE
Jan 08 22:22:11 Gundam2 systemd[1]: netctl@1
0gb.service: Failed with result 'exit-code'.

systemctl status netctl@10gb2.service
× netctl@10gb2.service - crossover
     Loaded: loaded (/u
sr/lib/systemd/system/netctl@.service; enabled; preset:
disabled)
    Drop-In: /etc/systemd/system/netctl@10gb2.service.d
             └─
               ile.confprofile.conf
     Active: failed (Result: exit-code) since Thu 2026-01-08 22:22:10
 UTC; 4min 12s ago
       Docs: man:netctl.profile(5)
    Process: 768 ExecStart=/usr/lib/netctl/network start 10gb2 (code=exi
ted, status=1/FAILURE)
   Main PID: 768 (code=exited, status=1/FAILURE)
        CPU: 160ms

Jan 08 22:22:04 Gundam2 systemd[1]: Starting crossover...
Jan 08 22:22:04 Gundam2 network[768]: Starting network profile '10gb2'...
Jan 08 22:22:10 Gundam2 network[768]: No connection foun
d on interface 'enp10s0f1' (timeout)
Jan 08 22:22:10 Gundam2 network[768]: Failed to bring th
e network up for profile '10gb2'
Jan 08 22:22:10 Gundam2 systemd[1]: netctl@10gb2.service
: Main process exited, code=exited, status=1/FAILURE
Jan 08 22:22:10 Gundam2 systemd[1]: netctl@1
0gb2.service: Failed with result 'exit-code'.
Jan 08 22:22:10 Gundam2 systemd[1]: Failed to start cros
sover.--

both 10gb and 10gb2 are this cause i don't know which is which
edit not really:

Description='crossover'
Interface=enp10s0f0
Connection=ethernet
IP=static
Address=('10.1.10.2/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')

10gb2

Description='crossover'
Interface=enp10s0f1
Connection=ethernet
IP=static
Address=('10.1.10.2/24')
Gateway='10.1.10.1'
DNS=('10.1.10.1')

Last edited by huhn (2026-01-08 22:21:26)

huhn · 2026-01-08 23:15:01

fixed it i just had to remove the gateway and DNS.

i will keep this thread open for now and change it to solved in a week or so and hope someone will figure out how to do the DHCP stuff till then.

cryptearth · 2026-01-09 00:26:43

for zfs: https://github.com/archzfs/archzfs
if you don't use any of the official kernels go for the dkms (don't forget to install dkms and tge headers for your kernel)

seth · 2026-01-09 08:19:07

someone will figure out how to do the DHCP stuff till then

What "dhcp stuff"?
You can install kea and run a dhcp server on arch, the linked wiki has a minimal example (you'd have to adapt for the 10.1.10.1/24 segment and enp10s0f0/enp10s0f1)

The main problem you need to be prepared for is that any dhcp client in the system will now find two dhcp servers via two NICs and you'll have to configure the dhcp clients on either system accordingly.
For netctl see https://wiki.archlinux.org/title/Netctl … HCP_client - both dhcpcd and dhclient will accept the interface to use (enp9s0) as parameter.

huhn · 2026-01-09 09:02:15

cryptearth wrote:

for zfs: https://github.com/archzfs/archzfs
if you don't use any of the official kernels go for the dkms (don't forget to install dkms and tge headers for your kernel)

that's not the problem zfs is running as it should be.
and the old bug was more about linux header and the current used kernel.
and that i really don't want to update zfs and the kernel to compile a nic driver.

seth wrote:

someone will figure out how to do the DHCP stuff till then
What "dhcp stuff"?
You can install kea and run a dhcp server on arch, the linked wiki has a minimal example (you'd have to adapt for the 10.1.10.1/24 segment and enp10s0f0/enp10s0f1)
The main problem you need to be prepared for is that any dhcp client in the system will now find two dhcp servers via two NICs and you'll have to configure the dhcp clients on either system accordingly.
For netctl see https://wiki.archlinux.org/title/Netctl … HCP_client - both dhcpcd and dhclient will accept the interface to use (enp9s0) as parameter.

ok let me understand this if i use this:
directly from the wiki

{
    "Dhcp4": {
        "interfaces-config": {
            "interfaces": [ "eth0/192.168.0.253" ],
            "dhcp-socket-type": "raw"
        },

        "subnet4": [
            {
                "id": 1,
                "subnet": "192.168.0.0/24",
                "pools": [ { "pool": "192.168.0.100 - 192.168.0.199" } ],
                "option-data": [
                    {
                        "name": "routers",
                        "data": "192.168.0.254"
                    },
                    {
                        "name": "domain-name-servers",
                        "data": "192.168.0.1"
                    }
                ]
            }
        ]
    }
}

and the eth0 is just another alias for enp0 or something?
and as long as i don't use enp9s0 there will be no 2 DHCP server on the same network?

seth · 2026-01-09 12:35:28

and the eth0 is just another alias for enp0 or something?

https://wiki.archlinux.org/title/Networ … face_names

if i use this: directly from the wiki

You'll run into problems because this *generic example* operates on 192.168.0.0/24 - ie the same segment your router is maintaining and providing dhcp for.

seth wrote:

you don't want to introduce a second dhcp server.
Certainly not into the same segment (192.168.0.0/24) and it's over-complicating the secondary connection

Why do you want to use dhcp here if the only goal is to have a P2P connection between two hosts (what also is already working)
What do you think the benefits would be?

huhn · 2026-01-09 14:56:41

seth wrote:

and the eth0 is just another alias for enp0 or something?
https://wiki.archlinux.org/title/Networ … face_names

to bad i still saw a rename of the onboard nic using the new names where i had to reconfigurate the system. wasn't fun.

so

{
    "Dhcp4": {
        "interfaces-config": {
            "interfaces": [ "enp10s0f0/192.168.200.110" ],
            "dhcp-socket-type": "raw"
        },

        "subnet4": [
            {
                "id": 1,
                "subnet": "192.168.200.0/24",
                "pools": [ { "pool": "192.168.200.100 - 192.168.200.199" } ],
                "option-data": [
                    {
                        "name": "nas",
                        "data": "192.168.200.111"
                    },
                    {
                        "name": "domain-name-servers",
                        "data": "192.168.0.1"
                    }
                ]
            }
        ]
    }
}

will only expose a DHCP server to the intel card and the other connection know nothing about that?
the final 10gb is this:

Description='crossover'
Interface=enp10s0f0
Connection=ethernet
IP=static
Address=('192.168.200.110/24')

i can change this back to 1 so it is outside the range if needed same for the server
the domain name sever can be removed right?

if i use this: directly from the wiki
You'll run into problems because this *generic example* operates on 192.168.0.0/24 - ie the same segment your router is maintaining and providing dhcp for.
seth wrote:
you don't want to introduce a second dhcp server.
Certainly not into the same segment (192.168.0.0/24) and it's over-complicating the secondary connection
Why do you want to use dhcp here if the only goal is to have a P2P connection between two hosts (what also is already working)
What do you think the benefits would be?

so i can just put a cable into enp0s0f1 using a dhcp client searching device like everything is by default and it should work?
i still need a cable check that runs the profiles when a cable/connection is detected but that's it?

also this is a windows system it will without a doubt mess the connection up sooner or later and with DHCP it will just work.

btw. windows is defaulting to 10 gb and ignoring the 1 gb connection good job microsoft something that works...

Last edited by huhn (2026-01-09 14:58:57)

Arch Linux

#1 2025-11-11 15:18:51

problem setting up a secondary network cnnection.

#2 2025-11-11 18:55:13

Re: problem setting up a secondary network cnnection.

#3 2026-01-08 12:19:24

Re: problem setting up a secondary network cnnection.

#4 2026-01-08 15:23:28

Re: problem setting up a secondary network cnnection.

#5 2026-01-08 16:50:43

Re: problem setting up a secondary network cnnection.

#6 2026-01-08 20:23:54

Re: problem setting up a secondary network cnnection.

#7 2026-01-08 20:52:16

Re: problem setting up a secondary network cnnection.

#8 2026-01-08 21:38:27

Re: problem setting up a secondary network cnnection.

#9 2026-01-08 22:11:16

Re: problem setting up a secondary network cnnection.

#10 2026-01-08 23:15:01

Re: problem setting up a secondary network cnnection.

#11 2026-01-09 00:26:43

Re: problem setting up a secondary network cnnection.

#12 2026-01-09 08:19:07

Re: problem setting up a secondary network cnnection.

#13 2026-01-09 09:02:15

Re: problem setting up a secondary network cnnection.

#14 2026-01-09 12:35:28

Re: problem setting up a secondary network cnnection.

#15 2026-01-09 14:56:41

Re: problem setting up a secondary network cnnection.

Board footer