View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001334 | Windows and other desktop OS | OpenVPN | public | 2020-09-19 07:34 | 2023-12-04 15:26 |
| Reporter | DigitalMy | ||||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Summary | 0001334: Routing fails for some OpenVPN hosts | ||||
| Description | Several hosts in server network are available for OpenVPN clients, but others not. Target: any host is routed properly and tracert must show OpenVPN step | ||||
| Tags | No tags attached. | ||||
| FinishDate | |||||
| StartDate | |||||
| WasteTime | 0 | ||||
| PriorityIndex | 3 | ||||
| LaboriousnessIndex | 1 | ||||
|
|
Edit OpenVPN\config\ipp.txt file in server, set each line names to be in quotes, like: "DM",10.3.1.2 |
|
|
OpenVPN server log has the following error on connection to "faulty" local host: MULTI: bad source address from client [10.89.224.163], packet dropped |
|
|
since there is tun interface type set , it is recommended to assign 4 addresses for each client, like .4 .8 .12 .16 |
|
|
Found problem that server has only routes to client networks through another server, there is no route directly (which should be primary way). used scripts in server: script-security 2 client-connect /etc/openvpn/connect.sh client-disconnect /etc/openvpn/disconnect.sh inside script do: if [ "$CLIENT" = "PC01" ]; then echo "set route..." ip route add table main 10.1.146.0/24 via 10.1.150.146 metric 50 dev tun1; fi; now it works good |
|
|
Found that Windows clients have not routed ping from VPN to internal. regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters If not already there, create a new REG_DWORD value named IPEnableRouter. Set IPEnableRouter to 1 and reboot. Packet forwarding should now be enabled (if adapter has connected status with link up). Now it pings. |