I set up an old PC I had with Zorin. Everything is working great and I want to use the system with no monitor and only RDP into system.
I can do this with hardwired connection but I can only use wi-fi to connect once I have already logged in.
I see my system does get an IP on wifi adapter when first booted but I am not sure why I can't log in using RDP unless I am hardwired and connect to that to first log in.
I would like to not have it hardwired and use wi-fi only but how can I enable wi-fi to start on boot and not have to log in.
Welcome to the Forum!
Did You checked Your BIOS for Wifi Settings?
Wifi works fine once I am booted and logged in what setting would I check in BIOS?
That is not directly unified. Should be something like ''Wake on''.
Need to test some more but seems to be fixed by doing the following.
Documentation: Fixing Zorin OS RDP via Kernel Route Rebinding
The Problem
When both Wi-Fi and Ethernet are connected, Zorin OS enables Strict Reverse Path Filtering (rp_filter) by default. If an RDP request comes in on the Wi-Fi IP address, the kernel looks at its routing table, sees that the Ethernet card is the "preferred/fastest" route out, and tries to reply through the Ethernet cable.
Because the request came in on Wi-Fi but the reply tried to go out via Ethernet, the kernel senses an asymmetric routing loop, flags it as a security risk (spoofing), and drops the packets. The Wi-Fi RDP connection only works if the Ethernet cable is plugged in to complete that mismatched loop.
The Solution: Loose Path Rebinding
By changing the rp_filter value from 1 (Strict) to 2 (Loose), we tell the Linux kernel to rebind and validate the paths loosely. As long as the return path is reachable via any active interface on the machine (including the Wi-Fi card), it allows the connection to succeed independently.
File to Edit
/etc/sysctl.conf (The system control configuration file)
The 3 Lines of Code
`Plaintextnet.ipv4.conf.all.rp_filter = 2
net.ipv4.conf.default.rp_filter = 2
net.ipv4.route.flush = 1`