[SOLVED] Gigabit Direct Ethernet Connection to Nas

Io · 2020-12-10 07:37:01

Hello everybody,

I am setting up a NAS at a new place and am treating it as an external drive with a direct Gigabit connection to my home arch installation

It is an old MyCloud 2TB NAS I got in 2016 or so but is humming along just fine. The light is blue indicating that it has a network connection.

DHCP appears to have assigned the ethernet port an IPv6 address:

Dec 10 01:52:46 komodo dhcpcd[538]: enp0s31f6: carrier acquired
Dec 10 01:52:46 komodo dhcpcd[538]: enp0s31f6: IAID c2:0e:ef:66
Dec 10 01:52:46 komodo dhcpcd[538]: enp0s31f6: adding address fe80::497f:6081:c327:87c7
Dec 10 01:52:47 komodo dhcpcd[538]: enp0s31f6: soliciting a DHCP lease
Dec 10 01:52:47 komodo dhcpcd[538]: enp0s31f6: soliciting an IPv6 router
Dec 10 01:53:00 komodo dhcpcd[538]: enp0s31f6: no IPv6 Routers available

This ip shows up in `ip -6 route` too though the "No IPv6 Routers" line seems suspect.

smbtree -b gives no output.

nautilus does not see it.

Am unsure what to do from here as all the hardware appears happy and able to speak to one another.

I've tried all this with a switch too and its approximately the same output

when its connected to the router proper, I can mount it with cifs

Thanks

Last edited by Io (2020-12-28 03:33:08)

paulkerry · 2020-12-10 10:57:45

Io wrote:

I am setting up a NAS at a new place and am treating it as an external drive with a direct Gigabit connection

Does that particular NAS support doing that? NAS units tend to have nfs, samba, etc sharing capabilities that you setup on the NAS itself.
You've not really said what the issue is and how this relates to Arch Linux. Are you saying you installed Arch on the NAS or you are using Arch to connect to the NAS and something is not working?

Cheers
Paul.

Io · 2020-12-11 18:57:41

some related resources i've found snooping around here

https://bbs.archlinux.org/viewtopic.php?id=118845

For My Cloud devices, is really straight forward on windows and mac -- plug and play -- so it should be feasible on arch

Io · 2020-12-14 04:09:59

So I've got it to connect by following some really nice instructions I found on reddit for setting up a private network

It was an issue of not having an router to hand out ip's. The instructions essentially just slaps an IPv4 address on my computers ethernet interface and then configures the dhcp server to use that interface.
This also requires installation of the server, dhcpd, not the client, dhcpcd. The client is already running on the NAS waiting to be handed an ip.

Problem is once i have the dhcp server up, my actual internet router rejects all my packets. I am on wifi so its a different interface. There must be some crossover behavior that I am not aware of.

I'm new to all this networking lingo so please correct my usage if it is glaringly incorrect.

Io · 2020-12-28 03:19:12

Ive figured out a bit more.
So its not really necessary to do all that ipv4 stuff.

There is a link-local unicast ipv6 address negotiation that is done automatically through two dhcp clients. That is what was present in the first post.

So i went and did this
https://wiki.archlinux.org/index.php/IP … _discovery
and found the ip. And then I pinged it and saw the little green light flicker on my NAS's ethernet port.

I learned about this after reading Villapx's reference to the spec on this ubuntu stack exchange question
and reading about 169.254.0.0/16 addresses in general and extrapolating to ipv6 and the state of my ip tables.

The dhcp server i had running was on a Google nest network and there is very little i can do to configure the nest router as it looks pretty locked down. the two servers (nest router and my own dhcp server) i guess were fighting with each other.

Now I'm trying to figure out what the correct mount command is.
so far I have

sudo mount -v -t cifs //fe80::290:a9ff:fed0:4bce/Public /mnt/NAS

This command worked before on previous routers as a proper NAS setup, same computer, using an ipv4 address.
now it just says

quanta@komodo ~ % sudo mount -v -t cifs //fe80::290:a9ff:fed0:4bce/Public /mnt/NAS [0]
Password for root@//fe80::290:a9ff:fed0:4bce/Public:
mount.cifs kernel mount options: ip=fe80::290:a9ff:fed0:4bce,unc=\\fe80::290:a9ff:fed0:4bce\Public,user=root,pass=********
mount error(2): No such file or directory

and dmesg says

quanta@komodo ~ % journalctl -xe
[ . . .]
Dec 27 22:13:17 komodo kernel: CIFS: Attempting to mount //fe80::290:a9ff:fed0:4bce/Public
Dec 27 22:13:17 komodo kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers>
Dec 27 22:13:17 komodo kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Dec 27 22:13:17 komodo kernel: CIFS VFS: cifs_mount failed w/return code = -2

changed smb version to 1.0 accomplishes the same thing.

Last edited by Io (2020-12-28 03:38:22)

progandy · 2020-12-28 03:26:51

for link-local addresses (fe80::) you have to append the network device.

//fe80::290:a9ff:fed0:4bce%enp0s31f6/Public

Io · 2020-12-28 03:30:51

Ah thank you. I am now connected. Marking as solved.

progandy · 2020-12-28 03:38:02

To set up the dhcp server you'll have to configure it to only listen on the ethernet connection, not wifi.

Otherwise you can set up IPv4LL as a dhcp fallback. https://wiki.archlinux.org/index.php/Av … IP_address (windows does that by default) If you use another network management tool, then maybe it has some other options to enable it.

Last edited by progandy (2020-12-28 03:39:37)

Io · 2020-12-28 04:58:45

Ah to anyone wondering how to do this using dhcp, the instructions on reddit were enough.

I had to add one line to my /etc/dhcpd.conf

option subnet-mask 255.255.255.0;
# same IP address assigned to the network interface
option routers 192.168.4.100;
# configure DHCP to assign IP addresses between 192.168.4.50 and 192.168.4.99
subnet 192.168.4.0 netmask 255.255.255.0 {
interface enp4s0;
range 192.168.4.50 192.168.4.99;
}

Note the "interface enp4s0"

I added this as according to the redhat linux doc

If more than one network interface is attached to the system, but the DHCP server should only listen for DHCP requests on one of the interfaces, configure the DHCP server to listen only on that device. The DHCP daemon will only listen on interfaces for which it finds a subnet declaration in the /etc/dhcp/dhcpd.conf file.

Sidenote, it looks like the ipv6 address is sticky throughout reboots of the computer, but probably not the NAS. Next problem to solve is to build a set up which is a robust through reboots.

Is there a benefit to using a dhcp server in a link-local set-up?

Arch Linux

#1 2020-12-10 07:37:01

[SOLVED] Gigabit Direct Ethernet Connection to Nas

#2 2020-12-10 10:57:45

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#3 2020-12-11 18:57:41

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#4 2020-12-14 04:09:59

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#5 2020-12-28 03:19:12

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#6 2020-12-28 03:26:51

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#7 2020-12-28 03:30:51

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#8 2020-12-28 03:38:02

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

#9 2020-12-28 04:58:45

Re: [SOLVED] Gigabit Direct Ethernet Connection to Nas

Board footer