pioupiou

Hi, thanks for the answer ! Yes "eth0 is 1Gb interface and eth1 is a 10Gb interface". I succeed to manage the Unraid part. Not the docker part. For unraid I needed to set bond to false for both interfaces, like that br0 use eth0 and br1 is create to use eth1. I also set the Metric like : IPv4 default 10.10.10.1 via br0 1 IPv4 default 10.10.20.1 via br1 2 IPv4 10.10.10.0/24 br0 1 IPv4 10.10.20.0/24 br1 2 Now the contenair I use is from Hotio, from some week now, the images has integrate a client vpn in it (wiregard in my case). I tried to set the network to br1 and bind the port 8080 to the eth0 interface. But that didn't works. I bind it using -p 10.10.10.2:8080:8080 (10.2 is the ip of unraid, so eth0 ip). I think there is something I am missing but don't know what

Hello, Context : I have two interfaces on my unraid server (6.12.5), I would like to have : - one interface (eth0) for dockers, web api access, that can access from my private network (1Gbits/s) . - and one (eth1) that will be use by a container to access internet with a VPN (with a 10Gbits/s). My private network has already Vlans but have switch and router limited to . The first test I want to do, is to force the container with theVPN to pass in a specific Vlan on eth1. In a close future, eth1 would be on a completely separate network. Concrete case: On my private network I have a Vlan Server: 10.10.10.1/24 and a Vlan Fast : 10.10.20.1/24 If both eth (0 and 1) are one 10.10.10.1 (ex : eth0 = 10.10.10.2 and eth1 = 10.10.10.3) I can connect to Unraid but when I change eth1 to 10.10.20.2, I can't acess the web ui anymore. Actually (both interface on the same subnet) they are like : PROTOCOL ROUTE GATEWAY METRIC IPv4 default 10.10.10.1 via eth1 0 IPv4 10.10.10.0/24 br0 1 IPv4 10.10.10.0/24 eth1 1 I think it is weird that the default is "via eth1" Looking for an answers, I seen a post indicating that metric on route need to be modified. Maybe it should be like : IPv4 default 10.10.10.1 via br0 0 IPv4 default 10.10.10.1 via eth1 1 IPv4 10.10.10.0/24 br0 1 IPv4 10.10.10.0/24 eth1 1 And in if I change the subnet to eth1 : IPv4 default 10.10.10.1 via br0 0 IPv4 default 10.10.20.1 via eth1 1 IPv4 10.10.10.0/24 br0 1 IPv4 10.10.20.0/24 eth1 1 Am I wrong on that supposition ?

Hello, I have a Debian VM configure French keyboard. On the Debian VM, I set the French keyboard and when I display the keyboard, all key are display well and in their place. The keyboard local is fr_FR.UTF-8. I tried to use RealVnc, TinyVnc or the default viewer of unraid and can't do an '@' (Alt-gr + 0). I tried others, only Alt-gr + 9 works to display ^. All others (2->0) don't works. Is Someone has the solution to this problem ?

Ok for me that was an error of gateway (copy/paste is evil) . For example, if you have a vlan on a subnet 10.80.51.0/24 be sure to set 10.80.51.1 as gateway.

Hello, I am new and have installed an Unraid 6.12.5 server on 192.168.80.100 (with a nginx manager container and a pihole container). On it, I have created a VM with Debian. The network configuration is br0 that give it an IP 192.168.80.4. On the Debian VM, I have Nginx that uses a local DNS (thanks pihole) to redirect space.local (no https) to 127.0.0.1:8084 that is a container for jetbrains space on-promise. Inside the VM, I can access of the webgui using space.local, so the Nginx works and the container too. But If I try to access it from my local network, it fail with a ERR_CONNECTION_TIMED_OUT (This site can’t be reached) To answer some questions : When I installed debian first, I could use Nomachine. After installing docker and nginx, I can't use it anymore. I try to recreate a debian to check which one could cause that, but after installing docker, Nomachineopen then close after 1 seconde. But with RealVnc it works great. I can ping the VM from the network from a Linux computer (on Windows, I tried too add a rule on the firewall, I could ping another machine on the network but not the VM). I cant' install the docker-compose directly on Unraid, for an unknown reason, it make my Unraid disconnect of the network, and from the console on the server, after trying to stop docker, restart the network interface and unmount array, I restart the server and my disk (XFS) is corrupt and I need to repair it or format it (I try this twice, same problem. I had it too with a docker-compose of a simple Rabbitmq service). But this is another problem ! Using simple container works great, but the one from jetbrain space is a little more complex to convert in a bash script using docker run. So I used a vm to run the docker compose. Since I connect from RealVnc using the 192.168.80.100:5009, is there something to do for the VM ? It has an Ip but maybe unraid block the port forwarding ? I hope that someone can help me with that. It makes me crazy to not understand why it doesn't work.