F5F Stay Refreshed Power Users Networks Routing Problems on the Network Issue with data transmission paths Connectivity challenges affecting performance

Routing Problems on the Network Issue with data transmission paths Connectivity challenges affecting performance

Routing Problems on the Network Issue with data transmission paths Connectivity challenges affecting performance

T
Trustywolf
Junior Member
Find
42
08-03-2016, 12:57 AM
#1
You're experiencing an issue where traffic from your dedicated OVH box (IP: 145.xxx.xxx.xxx/24) through Proxmox isn't reaching the correct network segments. The problem lies in how your OpenVPN and pfSense configurations are set up. Since all traffic goes through pfSense, you're seeing the WAN adapter ping the proxy address but not from inside the VM or local network. When you disconnect the VPN, the issue disappears, indicating the VPN is likely blocking access to the 145.xxx.xxx.xxx/24 range. To resolve this, verify your firewall rules on pfSense for the correct subnet and ensure the OpenVPN client is properly configured to use the right IP ranges. You may also need to check if the proxy settings in OpenVPN are correctly pointing to the intended server.
Reply
Reply
T
Trustywolf
08-03-2016, 12:57 AM #1

You're experiencing an issue where traffic from your dedicated OVH box (IP: 145.xxx.xxx.xxx/24) through Proxmox isn't reaching the correct network segments. The problem lies in how your OpenVPN and pfSense configurations are set up. Since all traffic goes through pfSense, you're seeing the WAN adapter ping the proxy address but not from inside the VM or local network. When you disconnect the VPN, the issue disappears, indicating the VPN is likely blocking access to the 145.xxx.xxx.xxx/24 range. To resolve this, verify your firewall rules on pfSense for the correct subnet and ensure the OpenVPN client is properly configured to use the right IP ranges. You may also need to check if the proxy settings in OpenVPN are correctly pointing to the intended server.

Reply
Reply
A
ASAAD_3D
Member
Find
199
08-07-2016, 11:18 PM
#2
Are you sure you have those configurations? I'm not using them for a private network. Is the /24 subnet set up under NAT? Have you connected the static routers to the PFSS for the virtual machines?
Reply
Reply
A
ASAAD_3D
08-07-2016, 11:18 PM #2

Are you sure you have those configurations? I'm not using them for a private network. Is the /24 subnet set up under NAT? Have you connected the static routers to the PFSS for the virtual machines?

Reply
Reply
M
Mettaton728
Junior Member
Find
25
08-21-2016, 08:15 AM
#3
145.xxx.xxx.xxx is the IP address of my Proxmox and the main dedicated machine, which I own. The 192.168.1.0/24 network is behind a NAT. It seems like the traffic might be trying to get back through it, though I'm not entirely sure. Static routers? The static route from pfSense only covers local devices on the gateway.
Reply
Reply
M
Mettaton728
08-21-2016, 08:15 AM #3

145.xxx.xxx.xxx is the IP address of my Proxmox and the main dedicated machine, which I own. The 192.168.1.0/24 network is behind a NAT. It seems like the traffic might be trying to get back through it, though I'm not entirely sure. Static routers? The static route from pfSense only covers local devices on the gateway.

Reply
Reply
T
The_D3mon
Senior Member
Find
694
08-21-2016, 09:27 AM
#4
Confirming? Are all these IPs open to the public? Verify the owner via WHOIS and see how the route appears on a client using traceroute.
Reply
Reply
T
The_D3mon
08-21-2016, 09:27 AM #4

Confirming? Are all these IPs open to the public? Verify the owner via WHOIS and see how the route appears on a client using traceroute.

Reply
Reply
P
proboy25
Junior Member
Find
17
08-21-2016, 04:08 PM
#5
Certainly, the issue seems to be with reaching them when using the VPN or on local access. I can connect easily without the VPN and via regular internet. The path looks like client → OpenVPN server → PFSense gateway → OVH gateway → ? Then after reaching the gateway it doesn’t seem to act or forward properly. I think the problem is that IP routing leaves the gateway without proper forwarding, whereas I expect it to send traffic straight from PFSense to the proxy IP if that’s the goal.
Reply
Reply
P
proboy25
08-21-2016, 04:08 PM #5

Certainly, the issue seems to be with reaching them when using the VPN or on local access. I can connect easily without the VPN and via regular internet. The path looks like client → OpenVPN server → PFSense gateway → OVH gateway → ? Then after reaching the gateway it doesn’t seem to act or forward properly. I think the problem is that IP routing leaves the gateway without proper forwarding, whereas I expect it to send traffic straight from PFSense to the proxy IP if that’s the goal.

Reply
Reply
J
jinxyourown
Junior Member
Find
48
08-24-2016, 01:37 AM
#6
This sounds like a kludgy mess bro. A diagram would probably help. You likely need a return route for traffic in your VM space, you could verify by testing from the pfSense LAN side address/itnerface.
Reply
Reply
J
jinxyourown
08-24-2016, 01:37 AM #6

This sounds like a kludgy mess bro. A diagram would probably help. You likely need a return route for traffic in your VM space, you could verify by testing from the pfSense LAN side address/itnerface.

Reply
Reply