mirror of https://github.com/pikvm/pikvm.git
usb-ethernet: instructions for windows (#609)
Co-authored-by: Maxim Devaev <mdevaev@gmail.com>
This commit is contained in:
parent
994f826959
commit
2a65be03a6
|
|
@ -81,6 +81,9 @@ By default, `kvmd-otgnet` will configure network connection between PiKVM and th
|
|||
```
|
||||
|
||||
5. Don't forget to `reboot`.
|
||||
|
||||
|
||||
=======
|
||||
|
||||
??? example "An example of what the config would look like if you wanted the target to have inet access (Please edit to suit your needs):"
|
||||
```
|
||||
|
|
@ -96,3 +99,35 @@ By default, `kvmd-otgnet` will configure network connection between PiKVM and th
|
|||
- /usr/bin/ip
|
||||
net: 10.65.0.0/28
|
||||
```
|
||||
|
||||
|
||||
=======
|
||||
## Working with Windows Computers
|
||||
This has been proven to work with Windows:
|
||||
1. Set the driver type to `rndis` (see above)
|
||||
2. Download this driver on the Windows machine and unzip it somewhere: [https://modclouddownloadprod.blob.core.windows.net/shared/mod-rndis-driver-windows.zip]
|
||||
3. Open the devices manager \
|
||||

|
||||
4. Select `Properties` of the `Composite KVM Device` \
|
||||

|
||||
5. Select the `RNDIS Device` and click properties \
|
||||

|
||||
6. Switch to the "Driver" Tab and then click "Update driver"
|
||||
7. Click "Browse my computer for driver software" \
|
||||

|
||||
8. Click "Let me pick from a list of available drivers on my Computer" \
|
||||

|
||||
9. From the list of available hardware types, scroll down and select "Network adapters", then click next \
|
||||

|
||||
10. Click "Have disk" \
|
||||

|
||||
11. Click Browse, navigate to the folder where you've stored the driver and select the `RNDIS.inf`, press Open and then OK \
|
||||

|
||||
12. Select "Acer Netchip RNDIS/Ethernet Gadget" and click Next \
|
||||

|
||||
13. Dismiss the warning about non-compatible drivers by clicking "Yes" \
|
||||

|
||||
14. You're done - the device should now be recognized. \
|
||||

|
||||
15. Verify the card is working by pinging your piKVM in a console: `ping 169.254.0.1` \
|
||||

|
||||
|
|
|
|||
Loading…
Reference in New Issue