Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - paxonsk

#1
18.7 Legacy Series / Re: Bug NAT whith multi WAN
June 21, 2018, 11:49:13 PM
Hi,

thank you for reply

seems to be familiar, but I think not, because I was try all combinations of Sticky connections,Shared fowarding, Default gw switching and so on, but only update to 18.7dev solve whole issue.
#2
18.7 Legacy Series / Re: Bug NAT whith multi WAN
June 08, 2018, 01:37:13 PM
Hi,

I had similar issue wit multiWAN with two uplinks.
I have configured all corretly with policy based routing over GW group.
If I had disabled Shared forwarding, than multiWAN works(if one uplink down, takeover to second and vice versa), BUT inbound port forward  _not_ works, only if I add default route to system table, but works only for this one uplink which I set in default route.
If I enable Shared forwarding, than multiWAN _not_ works, same as port forward.  This is on version 18.1.x
I take days (2weeks) of testing where I am made something wrong, troubleshooting on opnsense/freebsd level(hacking pf rules, router etc.) and today I test update to development 18.7 version and ALL works perfectly, with or without Shared forwarding, mutliWAN with inboud portforward works over both WAN links.

I read in 18.7 milestones this:
o improved default route handling
o improved default gateway switching

This is related probably to this, or  can you send link to github, where this problem fixed between 18.1 and 18.7 ?
Thank you :) and again THANK you for perfect project and all work around ;)


@eginfo: try update opnsense :)