Show Posts
1
18.1 Legacy Series / 18.1.2_2 Won't route traffic to differant subnets
« on: February 19, 2018, 08:40:26 pm »
I recently updated (after testing at home) a system to 18.1.2_2 and now am faced with issues routing internet traffic (internal traffic routes fine) to a remote subnet. The subnet that the system in question sits on is 10.1.0.0/24 and the subnet that it no longer will route internet traffic to is 10.3.0.0/24. Keep in mind, this is a network that has been up and running for years. No changes where made besides updating from 18.1 to 18.1.2_2.
What is curious is that ALL other traffic (any type of internal traffic) works fine. I can ping, tracert, RDP, use internal webpages etc between the two parts of the network. The OpenVPN works fine, the IPsec VPN that ties the network to my house (for remote backups of our VMware system) works fine. Devices from the 10.1.0.0/24 subnet can access the internet fine as well.
Does anyone know if there is a bug with static routes or if some portion of their setup changed due to the update? I can (and will) provide any logs necessary to help trouble shoot this thing.
What is curious is that ALL other traffic (any type of internal traffic) works fine. I can ping, tracert, RDP, use internal webpages etc between the two parts of the network. The OpenVPN works fine, the IPsec VPN that ties the network to my house (for remote backups of our VMware system) works fine. Devices from the 10.1.0.0/24 subnet can access the internet fine as well.
Does anyone know if there is a bug with static routes or if some portion of their setup changed due to the update? I can (and will) provide any logs necessary to help trouble shoot this thing.