OPNsense Forum
Archive => 17.7 Legacy Series => Topic started by: the_wolf on July 28, 2017, 01:56:14 am
-
follow the manual below: ... https://docs.opnsense.org/manual/how-tos/multiwan.html is to only turn on and to navigation. Already redid the settings 3 times. Not vavega nothing. Neither the captive portal. For everything. But I can ping the fixed IP. So the problem this in the dns. Someone's a light ??
-
...
-
...
-
...
-
i have been working on this for over a year to get it working.
what is your Trigger Level Explained ?
-
sorry I did not understand.
-
Can you show your routing info?
who is doing the dns? the firewall or some internal dns server ?
-
It looks like a DNS issue, how are your severs set up under System: Settings: General ?
-
Sorry for the delay
The routes are these.
Opn is doing dns
-
Sorry for the delay
I put a valid dns and are browsing the other vlans. But in vlan with captive portal does not ask user and password.
-
I'm not using proxy.
using version 17.7
-
I did everything again but this time I just cleared the default route in the gateway settings and the route rules left everything default. Now it's working. But I could not test if failover is working. Will it work ?????
-
Its should works
I know it was a routinge issue as I've faced the same issue couple of days ago
If you follow the documentations you should get things working
-
thank you. I'll try and notice .
-
using dnsmasq dns instead of unbound works for me.
-
using dnsmasq dns instead of unbound works for me.
Can you explain more what do you mean exactly ?
what does works and not ?
-
using dnsmasq dns instead of unbound works for me.
Can you explain more what do you mean exactly ?
what does works and not ?
There are two options for dns: unbound dns and dnsmasq dns. I disabled unbound dns and enabled dnsmasq. Previously, I had unbound enabled and dnsmasq disabled.
I also followed wiki how-to for multiwan. It works without any problems, at least in my case.