DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

2850 - Having trouble forcing fixed Ip to use WAN 2

  • wildoat
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 Feb 2013 17:15 #75168 by wildoat

sicon wrote: have you unticked the "Auto failover to other"



Yes I have.

Please Log in or Create an account to join the conversation.

  • wildoat
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 Feb 2013 18:14 #75171 by wildoat

Voodle wrote: try using a firewall filter rule to do the load balance instead? I don't know if they work off of the same system or different but they achieve the same thing, maybe it works better?



Ok trying that now - have unticked 'enabled' in load balance policy to test this method and set a Firewall > Filter SetUp > Set 3 (Set 1 is already titled Default Call Filter and Set 2 is already titled Default Data Filter) > Filter Rule 1 as source IP 192.168.0.24 & Load Balance Policy as WAN2 - all other things left alone - is this right?. Will see how that works as I can try update the software on the TalkTalk box and if it works it means it has used WAN2 - will report back.

W.

PS Thanks for all the tips much appreciated as unplugging WAN1 seems a poor solution!

Please Log in or Create an account to join the conversation.

  • wildoat
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 Feb 2013 18:44 #75172 by wildoat
Certainly didnt work initially - have rebooted and it did allow an update to TalkTalk via WAN2 but it may just have been luck that it selected to use WAN2 at that time rather than the Firewall filter I have put in - looking at the NAT Sessions Table I am doubtful that it has worked as that IP address appears to be still using WAN1 intermittently. Maytbe I need to set in load balance and firewall?

Any advice gratefully received. W.

Please Log in or Create an account to join the conversation.

  • wildoat
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
13 Feb 2013 07:40 #75173 by wildoat
Well that didnt work:

192.168.0.24 22141 56445 8.8.8.8 53 WAN1
192.168.0.24 38841 40377 213.248.112.138 80 WAN2
192.168.0.24 38842 40378 213.248.112.138 80 WAN2
192.168.0.24 22395 56699 8.8.8.8 53 WAN1

This morning used WAN1 to update itself and take on its BT Vision persona! Is this a bug or am I being thick? Any ideas gratefully received but in the meantime back to unplugging WAN1!!

W.

Please Log in or Create an account to join the conversation.

More
13 Feb 2013 09:51 #75176 by sicon
ON filter Set2 did you tell it to go to filter set 3 as the next in the logical look up otherwise it wont process the rules in filter set 3

Please Log in or Create an account to join the conversation.

  • wildoat
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
13 Feb 2013 10:20 #75177 by wildoat

sicon wrote: ON filter Set2 did you tell it to go to filter set 3 as the next in the logical look up otherwise it wont process the rules in filter set 3



Hi sicon,

Many thanks for your time. No - how do I find that setting? I looked at Set 1 to use that as a template as I assumed that it would tell it to go to Set 2 but cannot see anything that says that.

Is it Firewall >> Filter Setup >> Edit Filter Set 2 and then at the bottom select 'Next Filter Set' = Set#3? If so why does Set 1 (Default Call Filter) have next filter set as 'None' rather than point to Set#2?

Sorry for being thick on this! W.

Please Log in or Create an account to join the conversation.

Moderators: Sami