Would this DDR4 3200 Samsung RAM work with the Wyse 5070?
Samsung M471A1K43DB1-CWE is an 8GB DDR4 3200Mbps 1Rx8 260-Pin SODIMM Laptop Notebook RAM Memory Module. Find more specifications and information.
It says 1RX8 (single rank) which would be a no but it suggests they have dual rank options. It looks like the 16GB+ (NOT 8GB) sticks are dual rank which would work.Would this DDR4 3200 Samsung RAM work with the Wyse 5070?
Samsung M471A1K43DB1-CWE is an 8GB DDR4 3200Mbps 1Rx8 260-Pin SODIMM Laptop Notebook RAM Memory Module. Find more specifications and information.semiconductor.samsung.com
Rank doesn't matter for speed -- it will run any faster memory at 2400 MHz regardless. All of my sticks are 2666 MHz but configured speed in `dmidecode -t 17` is all 2400 MT/s.Interesting. So as long as its single rank ddr4, it can be faster than 2400 MHz.
The thought has crossed my mind, but I haven’t tried it yet.Anybody tried soldering PCIe connector to the thin client?
I've tried this in the past and it didn't work for me. I ended up bricking the motherboard when I took it out of the case after to diagnose the issue and the bottom of the board scraped against the case and dislodged a few resistors and capacitors. If you're going to undertake this, I high recommend getting a photo of an extended motherboard so that you might be able to identify if there's a specific resistor arrangement to enable the PCIe port. Also, keep in mind that the solder they use to fill the gap has a very high melting point. It's a good idea to flow with lead solder beforehand to help kick start things.Looking at pictures of extended and thin client MOBOs I can see that thin just lacks PCIE connector and all surrounding elements are soldered in. Anybody tried soldering PCIe connector to the thin client? Extended ones are very hard to get in my country.
Extended mobo: https://d1grq5ng0vix8v.cloudfront.net/original/2X/c/ca81deb1d6482e2096c727598eaa734b6507a045.jpeg
I used a non-dell secondary realtek ethernet and I found that I needed to install the Official Realtek drivers (realtek-re-kmod) in pfsense to get 2 realtek ethernets working. Had problems similar to what you describe (one working, other not DHCP'ing). The driver is in the repo for 2.6, but needs to be installed and configured.I wonder if anyone else is having this issue. I installed a secondary RJ45 (Dell manufactured, Realtek chipset probably the same as the integrated NIC) on my Wyse 5070 and loaded Pfsense...
THANK YOU! Link in case anyone else is curious. PFSense doesn't hang at at resolving WAN and LAN on boot anymore either. Saves a good 30 seconds.I used a non-dell secondary realtek ethernet and I found that I needed to install the Official Realtek drivers (realtek-re-kmod) in pfsense to get 2 realtek ethernets working. Had problems similar to what you describe (one working, other not DHCP'ing). The driver is in the repo for 2.6, but needs to be installed and configured.
That is interesting. I haven't scoured all 22 pages, but wondering if anyone has put 2.5gbe on the LAN side. My cable modem is gigabit, but if 2.5 or 10 could get adopted, that'd be intriguing. Someone was mentioning the Cromwell stuff earlier in the posts. As for 2.5:Snip
Problem is that’s a B+M connector.
There are now rtl8125b a+e m.2 cards on eBay (and others). Various vendors. Look very similar to older realtek 8111 cards. Like:That is interesting. I haven't scoured all 22 pages, but wondering if anyone has put 2.5gbe on the LAN side. ...
Dell Wyse 5070 Ethernet Adapter by examiner (3D printed mount)That is interesting. I haven't scoured all 22 pages, but wondering if anyone has put 2.5gbe on the LAN side. My cable modem is gigabit, but if 2.5 or 10 could get adopted, that'd be intriguing. Someone was mentioning the Cromwell stuff earlier in the posts. As for 2.5:
Interesting! Have you tried vyos? The current development branch (1.4.x) supports running containers via podman, and no licensing fees. I also like the cli interface.I've been playing with this a bit more. I bought this ethernet adapter addon (New OEM Dell WYSE 5070 RJ 45 Port Daughter board w/ cable - 442XR 565JP 9DJC4 | eBay) it's a DELL OEM for the Wyse 5070. You can definitely get cheaper ones on Aliexpress and 3d print a mount for it but it's not that much cheaper. It's a Realtek 8111 chipset just like the onboard NIC.
I've tested PfSense and OPNsense on it. Pfsense requires you to install the Realtrek drivers while OPNsense has that prepackaged. OPNSense seems to provide better performance when using the DNS Resolver (uses Unbound). Performance on the Realtek NIC is about 5-10% less than that of an Intel NIC (I do not think CPU is a problem and Realtek NICs have been known to have slightly lower performance). I tested performance using iperf vs an old Xeon network appliance with Intel NICs.
The real gem happens when I tried out Mikrotik's RouterOS v7.5 x86 (installed bare metal and not CHR in a VM) with a demo license. I haven't tested the NIC performance yet, but it can't be worse than OPNsense. The real beauty is that RouterOS v.7.5 supports docker (Mikrotik has an abstraction layer on top for management). With the free demo license, I am able to run Unbound and PiHole and the DNS performance of that is far better than that on OPNsense or PfSense (we're talking about ms so you won't notice, but the numbers are there). I ran benchmarks using DNS Bench.
I think this is going to be my new router/firewall setup. At the end of the day, the firewall in Mikrotik's RouterOS is pretty damn good and the OS is pretty fast. The system boots and comes back online in about 30 seconds vs PFsense around a minute. Plus PFsense and OPNsense seem to have issues with their DNS resolver setup where saving changes will cause Unbound service to crash and restart.
A demo license for Mikrotik's RouterOS seems to fit the bill for me since it doesn't seem to have any bandwidth restrictions, and I don't use most of the features with restrictions. Although docker does take up 1 of the VETH interface afforded by the license.
Lastly, USB tethering with Android hotspots works as well. The device shows up as an LTE interface on RouterOS. I'll have to test this further. I'm currently using a T-Mobile Franklin T-9 with Google Fi as my failover. The issue I have with the device is that the DHCP lease seems to drop from time to time with PFSense and OPNsense and they do not automatically renew. I can write a script to bring it back up but I'll have to see if the same problem occurs with RouterOS. You'll have to tether using one of the USB-A ports instead of USB-C. The USB-C port doesn't seem to work on RouterOS. Could be chipset support related since the USB-C also doubles as a display out.
Things I've noticed:
- Hardware monitoring doesn't work, so no temps.
- The USB-C port doesn't work. You can probably get around this by using ESXI and the CHR version of RouterOS and doing a passthrough for the USB-C.
- Onboard EMMC storage is not recognized by the OS installer. You'll need to connect a SATA M.2 (probably better in the long run anyway).
- Mikrotik community support sucks! This is just a personal experience as a networking and Mikrotik RouterOS novice.
- Docker (Containers) does not behave the way that you are used to with traditional installs. For example, no port mapping support. It's also designed so that you'll have to create 1 VETH per container. For me running both Unbound and PiHole required that I create and mount a custom configuration for the unbound container to use port 5053 instead of 53 so that it doesn't conflict with PiHole since both are on the same VETH. Containers do not autostart on bootup and you have no control over container restart policies. I use netwatch (built in feature of RouterOS) start the containers on bootup using an http-get on Pihole for a 200 response. There's also a netwatch config to failover DNS to cloudflare's 220.127.116.11 if PiHole doesn't respond. The better way would be to poll PiHole's response on port 53 instead, I'll have to figure out how to do this, maybe a ping test with netwatch.
I think that will be the next test. So far this is working out pretty well and Mikrotik seems to be extremely low overhead. I'm sure VyOS is even more so without needing a web interface.Interesting! Have you tried vyos? The current development branch (1.4.x) supports running containers via podman, and no licensing fees. I also like the cli interface.
That makes sense. I did notice an IP change right after the reboot. I wasn't sure if it was coincidental that the lease expired. It must be the Realtek NIC. A similar issue happens with OPN/PFsense as well where the NIC would stop functioning and I would need to manually issue link down / up, but this only happened once before I moved onto Mikrotik.I'm with Comcast and the way mine works is the modem will only issue an ip address to the router once. It will not do it again unless you reboot the modem. This is by design. But I do agree that in your case Realtek could be the problem.