Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Direct Ethernet access to Unraid server stops working after 6.12

Featured Replies

(I'm still kinda new to most of this, so apologies)
My server has dual ethernets, ones is plugged into router and the other is directly connected to windows machine.
After upgrading to 6.12.0 or 6.12.1 I cannot access the server or GUI through the dedicated ethernet.  (the standard router address works)

reverting back to 6.11.5 solves the issue

 

The syslog on 6.11.5 has this line switching the interface on: 

"avahi-daemon[3277]: Joining mDNS multicast group on interface eth1.IPv4 with address 169.254.***.***"

on 6.12 it no longer does and only has it for the router address

 

I'm pretty sure its something simple I have to allow eth1 somewhere in a config 

Solved by bonienl

According your description, you set eth1 allocate IP by DHCP, but as no DHCP in that network, so finally it will assign 169.254.*.*

 

I haven't test does 6.12.x will do same thing, but in general won't setting in that way.

 

Pls simple assign static IP and Subnet to eth1 ( gateway in blank ), for example if router network in 192.168.1.1 with 255.255.255.0 then set eth1 in 192.168.2.X with 255.255.255.0 and windows machine in 192.168.2.Y 255.255.255.0 ( also gateway in blank ) should solve your problem.

  • Author

The pc and server are directly connected hence the local link IP address range.

 

They are set as static on both sides, the settings all come over fine on the update.

 

on 6.12.0/1 it just isn’t listening on eth1.

 

I wonder if it’s something with avahi-daemon. (Like eth1 is set to disabled) But I can’t seem to find where it’s config is

Does Unraid and Windows can ping each other in eth1 network ? Pls post Unraid diagnostic zip file as usual.

  • Author

Now for the newbie element from me, how exactly to I ping each of them?

 

I’ll post the diagnostic file tomorrow morning.

6 minutes ago, Viscounto said:

Now for the newbie element from me, how exactly to I ping each of them?

 

I’ll post the diagnostic file tomorrow morning.

OK.

 

For Unraid, open web terminal then ping Windows IP

 

image.png.c36cd5e38611afb01c9c9c38e0f8980c.png

169.254.117.248 is eth1 IP, you need ping Windows IP.

 

BTW, just simple test, as mention before, pls assign a static IP & subnet at Unraud eth1 and Windows

 

image.png.1f51b42b0551bb7f7f447d7f4b0d4552.png

 

At least it should work with 6.12.1

 

lsof | grep 192.168.2
sshd        520                       root    4u     IPv4            1550800       0t0        TCP 192.168.2.10:ssh (LISTEN)
smbd        577                       root   32u     IPv4            1545181       0t0        TCP 192.168.2.10:microsoft-ds (LISTEN)
smbd        577                       root   33u     IPv4            1545182       0t0        TCP 192.168.2.10:netbios-ssn (LISTEN)
rpcbind     631                        rpc    8u     IPv4            1549725       0t0        UDP 192.168.2.10:sunrpc 
ntpd        808                        ntp   17u     IPv4            1556567       0t0        UDP 192.168.2.10:ntp 
ntpd        808   811 ntpd             ntp   17u     IPv4            1556567       0t0        UDP 192.168.2.10:ntp 
nginx       929                       root   19u     IPv4            1550959       0t0        TCP 192.168.2.10:http (LISTEN)
nginx       929                       root   20u     IPv4            1550960       0t0        TCP 192.168.2.10:https (LISTEN)
nginx      4866                       root   19u     IPv4            1550959       0t0        TCP 192.168.2.10:http (LISTEN)
nginx      4866                       root   20u     IPv4            1550960       0t0        TCP 192.168.2.10:https (LISTEN)

 

  • Author

So if I set eth1 as static I get the warning "Interface Ethernet Port 1 is down. Check cable!"
 

Ping still works though.

Capture.PNG

When you change network settings, interface will up and down, and you need waiting Windows side link up too.

 

If you " lsof | grep 169.254 " haven't found service listening on that, you must set static IP.

  • Author

yeah, still not working.  I've added eth1 to include listening (new setting on 6.12)

Capture.PNG

Capture2.PNG

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.