-
Posts
3,699 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Vr2Io
-
-
8 minutes ago, SeRiusMe said:
No, by now there's no interface with an empty gateway.
Then it look like no problem on docker system now.
14 minutes ago, SeRiusMe said:I change the order for the DNS at the host and put the 10.1.5.251 at the top, The container at VLAN5 resolves DNS. BUT ALSO OTHER ONE IN VLAN2. (But it takes a while, I suppose because is trying 10.1.5.251 first?
All DNS server must accessible by all subnet, client will randomly resolve on all DNS server according the setting, not 1st one then 2nd then 3rd.
-
3 minutes ago, SeRiusMe said:
RESOLUTION IN CONTAINER IN VLAN5 WORKS IF DNS OF VLAN5 IS FORCED INSTEAD OF THE DEFAULT (10.1.3.251)
Interesting, but don't know why 10.1.3.251 not work, because eth0 no gateway ?
This also the difference on my setup, my private DNS ( Pihole ) was on eth0.2, not the router or public DNS. But my private DNS endup also lookup on a public DNS.
-
After start docker service
Still no gateway at eth0 ?
Unraid routing table look nornal ?
-
19 minutes ago, SeRiusMe said:
Can you please explain me how did the other guy solved it?
In fact I am not sure OP really fix or not, but no matter how I change the network setting, I couldn't reproduce OP's docker problem.
I store docker in /tmp ( ram file system ), so each reboot will redownload all docker ( only need restore appdata ) and I never do extra docker setting, that may be help always keep docker system clean up and so no trouble at all.
-
2 minutes ago, SeRiusMe said:
Restarting docker brings this two errors, that I found online tht are related to trying to create routes and failing because they exist.
# /etc/rc.d/rc.docker restart stopping dockerd ... ... Waiting to die. starting dockerd ... RTNETLINK answers: File exists RTNETLINK answers: File existsYes, problem pointing to docker system instead network or network setting.
You may try start from scratch by remove docker image / folder to fix it.
-
Your dig result haven't answer session, anyway depends on docker itself, my HA docker have dig and nslookup. The DNS translate also 127.0.0.11
I am not sure how to diagnostic if DNS resolve not work in docker.
-
/boot/config/parity-checks.log
-
16 hours ago, SeRiusMe said:
I bet that the server is trying to serve all the DNS requests through the 10.1.3.xx gateway/route, and it's failing. (It must be the default route)
No, for 10.1.2.xx or 10.1.5.xx, if DNS was 10.1.3.xx it should direct route through router.
For example,
traceroute in Unraid console, 192.168.9.x subnet route through 192.168.9.9 gateway
traceroute 192.168.2.5 traceroute to 192.168.2.5 (192.168.2.5), 30 hops max, 60 byte packets 1 192.168.9.9 (192.168.9.9) 0.115 ms 0.107 ms 0.229 ms 2 * * * 3 * * *traceroute in docker console, 192.168.68.x subnet route through 192.168.68.9 gateway
traceroute 192.168.2.5 traceroute to 192.168.2.5 (192.168.2.5), 30 hops max, 46 byte packets 1 192.168.68.9 (192.168.68.9) 0.088 ms 0.099 ms 0.089 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * -
22 hours ago, SeRiusMe said:
And I can't change the empty gateway in eth0.2. And you can see that it's not creating a custom network for eth0.
This indicate problem on docker system, I have reach a case, the OP have similar problem, always can't found the custom network, finally OP mark the case resolve by remove other previous docker network. So pls check does other create network left and remove it by "docker network rm xxxxx". Also perform some check on all existing docker network.
That's also / may be why we change all network setting and problem still occur.
Sometimes, docker network like a black box, when you confirm your physical network haven't issue, but always got trouble. Then you may need further verify by VM network first.
For DNS problem, do you confirm not problem on router routing ? For me, all docker could reach private DNS and internet, also other subnet.
docker network ls NETWORK ID NAME DRIVER SCOPE 669a79230488 bridge bridge local 61f4b403738e eth0 macvlan local a5af90fcb721 eth0.2 macvlan local e4473591c365 eth0.666 macvlan local a642478c8a6d host host local 33db889adf1b none null localdocker network inspect a5af90fcb721 [ { "Name": "eth0.2", "Id": "a5af90fcb721b1133c84995351c516a77c6d3464c66a60b0a505047507bd8ef4", "Created": "2024-05-18T10:51:40.796286014+08:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.2.0/24", "Gateway": "192.168.2.9" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "1e404021ac2b09835323d92888db216c69b46dfe26a213c33a4599fce449e1a9": { "Name": "Pihole", "EndpointID": "7489add3c1bc4b7eacc43bb65541a914b39a4a63ae40ef1acfdeb08265bf0564", "MacAddress": "02:42:c0:a8:02:05", "IPv4Address": "192.168.2.5/24", "IPv6Address": "" }, "cfaa6db42d9c4023309fa94ef10458b77d3cb184d7b5eb03b4c064f8996fed66": { "Name": "NTP", "EndpointID": "7009d52484bc8ca96171d088b7f1fbe592a6c435753448952d51b560b1369c2e", "MacAddress": "02:42:c0:a8:02:06", "IPv4Address": "192.168.2.6/24", "IPv6Address": "" }, "d7ffa44f7c40585d323f540599adf7880750480881f2d1163bfb43541dbba245": { "Name": "Syslogserver2", "EndpointID": "8d800260429264b6278caf086f5a77be0cade18ab7bfd9028155ac6f9037fee0", "MacAddress": "02:42:c0:a8:02:07", "IPv4Address": "192.168.2.7/24", "IPv6Address": "" } }, "Options": { "parent": "vhost0.2" }, "Labels": {} } ]19 hours ago, SeRiusMe said:You mean that set the Id to an unused/fake vlan so traffic doesn't go anywhere?
Yes. Each interface have a PVID, so if you don't want untag traffic going to a port, then you can assign an unuse PVID to it.
-
14 hours ago, SeRiusMe said:
With the configuration posted above, but with vlan disabled at eth0, I'm at a somewhat working state. But the interface eth0 is losing communication periodically.
Enable / disable vlan on eth0 won't cause problem, but best set to "no". As mention, I don't found problem on your UnraId setting, I just try to provide some change to troubleshoot.
14 hours ago, SeRiusMe said:The eth2 interface is rock solid, and I can attach docker containers to each vlan and they're accesible. But they don't resolve DNS queries.
That's a good sign, for DNS queries problem, if you use router / public DNS, then all subnet should be access without problem. If you use private DNS ( like me ) then you need do some routing at router to make DNS accessible. You don't need setting docker config., all docker will use Unraid setting DNS. For example, my docker on different vlan just need set the IP, that's all and no any special tuning.
13 hours ago, SeRiusMe said:I think I guess where must be the problem. The eth2 interface LACKS configuration in the base "interface". And it doesn't have VLAN 3 configured. I bet that unraid is sending some packets untagged though it and my router is giving that interface an address in the VLAN 3 segment. My previous sever had one there and it was the same ip that eth0 currently uses. Summarizing: The mellanox MAC previously had the 10.1.3.20 address. So could be a problem with DHCP, ARP or ROUTES.
What do you think?
I don't think above have problem.
13 hours ago, SeRiusMe said:As for 802.1Q VLAN configuration, first every port has the id of an VLAN, that's mandatory:
I understand , my bad. for more detail : set that switch port ( connect to eth2 ) with a new vlan id then vlan3 won't go there.
Pls also setting as below. If still got problem, pls also try ipvlan.
-
54 minutes ago, SeRiusMe said:
The ports on the lower graph (tagged) will be also tagged in other VLANS, but the ones above (access ports) can only be untagged in one. F.Ex 3, 5 and 7 are the ports for the APs. They are tagged also in the other vlans they serve through dedicated SSIDs. If that wasn't configured that way IOT devices could never use wifi unless I had a physical AP for IOT.
I don't found the graph. You mean you have three AP to serve three different vlan ? anyway this fine.
But if you connect three port to a AP then it usually form some looping.
A more elegant solution were use single AP and different ssid corresponding to different vlan, my AP support eight ssid, and different ssid bond to different vlan, then tag all to single ethernet port only.
-
20 hours ago, MAM59 said:
Also, i have to repeat once more: THERE SHOULD BE ONLY ONE DEFAULT GATEWAY. Not one for every card, only for the card that really has internet access.
This incorrect, OP have different subnet, so each subnet have their gateway is normal. And you use port-base vlan and untag all at access port, this is completely different setup as OP.
21 hours ago, SeRiusMe said:I'm a developer, not a networking technician.
21 hours ago, SeRiusMe said:I'm afraid that it is not possible to disable inter-vlan routing at my router. My systems would stop working.
People always think use vlan to seperate things but in other way think they need communicate each other .....
Your Unraid setup haven't problem, just your network environment have problem ( likely looping ) so network down. If you want simple separate stuff, pls try not use tag-base vlan and use port-base vlan + single subnet only.
For me I apply tag-base + port-base + different subnet.
-
11 hours ago, SeRiusMe said:
As you can see, I have to leave the eth2 interface disabled, because when it is online, all network connections reset after some seconds.
This odd, I have similar config. but only use one interface, management subnet were untag and others subnet were tag.
Edit : Pls try don't untag vlan 2 to eth2.
Pls also ensure, no bridge or inter vlan routing between different subnet at router side for troubleshooting.
-
192.168.1.x address block and is now a 192.168.50.x
Pls provide network config. file, it likely DHCP wasn't set to yes, or if you remember the original IP address 192.168.1.x, then manual config the access client to 192.168.1.x and try to access.
Also check does a diagnostics ( recent ) file already automatic save on USB stick.
-
Check does the LED on network card and router/switch have change, it show link / speed status.
If you have keyboard monitor attach to Unraid , then access it local and provide the diagnostics ( tools -> diagnostics ) file here.
-
It indicate a station STA:16:d8:85:1a:91:0c connect to router through WiFi but reject.
As Unraid doesn't support WiFi connection, so those shouldn't relate to Unraid.
-
-
Just try something, I surprise HA could get those CPU & disk temperature directly. I use HA docker and under HA console, you can easy got the reading as below. So, don't need MQTT.
/config # cat /sys/class/hwmon/hwmon3/temp1_input 41000 /config # cat /sys/class/hwmon/hwmon1/temp1_input 44850 /config # cat /sys/class/hwmon/hwmon1/temp1_input 44850 /config # cat /sys/class/hwmon/hwmon1/temp1_input 45850 /config # cat /sys/class/hwmon/hwmon1/temp1_input 44850 /config # cat /sys/class/hwmon/hwmon1/temp1_input 44850 /config # cat /sys/class/hwmon/hwmon0/temp1_input 47125 /config # cat /sys/class/hwmon/hwmon0/temp1_input 46875 /config # cat /sys/class/hwmon/hwmon0/temp1_input 46625 /config # cat /sys/class/hwmon/hwmon0/temp1_input 46500When you type sensors in Unraid console, it will show something as below
root@5600H:~# sensors amdgpu-pci-0500 Adapter: PCI adapter vddgfx: 1.02 V vddnb: 781.00 mV edge: +45.0°C PPT: 13.00 W k10temp-pci-00c3 Adapter: PCI adapter Tctl: +46.8°C drivetemp-scsi-2-0 Adapter: SCSI adapter temp1: +41.0°C nvme-pci-0100 Adapter: PCI adapter Composite: +45.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +45.9°C (low = -273.1°C, high = +65261.8°C)Below is the methods how you know the path
https://www.baeldung.com/linux/hdd-ssd-temperature
And last is convert it to sensors
https://www.home-assistant.io/integrations/command_line/
-
2 hours ago, Lucid_Enemy said:
The 10G port is straight out of my firewall's bridge as I don't have a 10G switch yet
igc means 2.5G and ix1 is 10G ? But why ix1 was linkdown ?
Does mlx4 00:02:c9:56:8c:1e show in router ?
# PCI device 0x15b3:0x6750 (mlx4_core)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:56:8c:1e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"If you can access Unraid locally and make test on 10g have pass some network test, i.e. ping other client and router, then problem likely opensense relate.
-
1
-
-
2 hours ago, Lucid_Enemy said:
The weird thing is that Unraid Connect shows it’s online
Does still on-line even 2.5g port plug-out ? Your switch is manage 10G switch ?
To simplify troubleshoot, disable bonding, put ConnecX-2 be eth0, disconnect eth1 ( also don't setting eth0,eth1 in same subnet), disable array auto-start until you solve the problem.
Also temporary setting "use SSL/TLS" to "no".
-
On 5/6/2024 at 3:06 AM, Gyration5904 said:
The issue is strictly with my Mac device, no others.
Connect in wire or WiFi ? Pls also try both.
-
3 hours ago, izone said:
在 路由器上那2個網口沒有做橋接？
沒有, 我是全部設備接上交換器, 路由器 lan 是單口.
-
17 minutes ago, spike32 said:
I can't turn that off because Unraid uses USB to boot.
Oh .... Yes 😝 Is it possible disable by port or different USB controller. Pls also try assign device on different controllers and apply different BIOS setting.
Edit : Pls also try different USB boot emulation BIOS setting.
-
你試下禁止"主機訪問自定義網絡", 看看有否不同. 另外亦試下刪除那個 emby 自定義網絡.
另外, 軟路由可以做到雙 WAN 吧, 那樣不用兩隻軟路由, LAN + vlan 行一個網口就可.
Help with multiple network adapters configuration.
in General Support
Posted
OMG 🫠