StephanS1984 schreef op donderdag 12 oktober 2023 @ 21:03:
[...]
Dit ondertussen aangepast:
eth9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.200.2 netmask 255.255.255.0
broadcast 192.168.200.255
inet6 fe80::d221:f9ff:fe88:aeae prefixlen 64 scopeid 0x20<link>
ether d0:21:f9:88:ae:ae txqueuelen 10000 (Ethernet)
RX packets 7203 bytes 518110 (505.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4700 bytes 367742 (359.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Helaas nog geen ping of telnet naar de Zaram op 192.168.200.1 met mijn UDM SE.
root@Dream-Machine-Special-Edition:~# ping 192.168.200.1
PING 192.168.200.1 (192.168.200.1) 56(84) bytes of data.
From 192.168.200.2 icmp_seq=1 Destination Host Unreachable
From 192.168.200.2 icmp_seq=2 Destination Host Unreachable
From 192.168.200.2 icmp_seq=3 Destination Host Unreachable
From 192.168.200.2 icmp_seq=4 Destination Host Unreachable
From 192.168.200.2 icmp_seq=5 Destination Host Unreachable
root@Dream-Machine-Special-Edition:~# telnet 192.168.200.1
Trying 192.168.200.1...
telnet: Unable to connect to remote host: No route to host
root@Dream-Machine-Special-Edition:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth8
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
192.168.200.0 0.0.0.0 255.255.255.0 U 0 0 0 eth9
Settings for eth9:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
MDI-X: Unknown
Supports Wake-on: umb
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
De Zaram is in orde want die werkt (Delta IP. inclusief telnet 192.168.200.1) in een ACT Gigabit SFP+ Media Converter. Het zit dus in de UDM SE hiervoor heb ik ook een support ticket aangemaakt. Ze zien problemen met de Speed/Duplex in de log maar na 2 dagen troubleshooten gaat het al snel naar een niet ondersteunde SFP in hun ogen.