clubsprint
Technical User
G'day all
I just installed R65 as a new Firewall. We previously had NGX which had corrupted the rulebase so I took the opportunity to do an upgrade. After setting up all the rules/objects etc. and setting up the DNS server part I moved into production but couldn't get it to work properly. Pinging anything that wqsn't directly connected to the interfaced got a "network unreachable error".
I check the routes against the old FW and found some differences. These weren't in the manually enterered persistent routes though. It appeared that the Firewall wasn't "learning" the routes. I manually added the route table from the old FW and everything them appeared to be fine but this was unnessesary on the old FW. I flushed the route cache but this didn't help. What am I missing?
FW has 4 interfaces Internet, LAN, DMZ and private net to other business.
I just installed R65 as a new Firewall. We previously had NGX which had corrupted the rulebase so I took the opportunity to do an upgrade. After setting up all the rules/objects etc. and setting up the DNS server part I moved into production but couldn't get it to work properly. Pinging anything that wqsn't directly connected to the interfaced got a "network unreachable error".
I check the routes against the old FW and found some differences. These weren't in the manually enterered persistent routes though. It appeared that the Firewall wasn't "learning" the routes. I manually added the route table from the old FW and everything them appeared to be fine but this was unnessesary on the old FW. I flushed the route cache but this didn't help. What am I missing?
FW has 4 interfaces Internet, LAN, DMZ and private net to other business.
But if the firewall is to learn routes to newly discovered networks,