• February 22, 2025, 03:15:23 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DFL-800 using 2 wan ports, but not as failover  (Read 4189 times)

ivpdxb

  • Level 1 Member
  • *
  • Posts: 2
DFL-800 using 2 wan ports, but not as failover
« on: July 04, 2013, 12:06:59 AM »

I need to connect to a provider that is giving us two blocks of fixed IP's (both /29s)

They will provide 2 separate network feeds, one for the 1st block and one for the 2nd block.

How can I configure the DFL-800 to use both of these blocks, where any request that comes in over wan1 must respond back out of wan1, and any that arrives on wan2 must respond back out of wan2

Internally there will be a mix of SAT and NAT between the public IP's and the internal systems.

The map needs to be something like this:

Wan 1 IP 1 = SAT to/from internal server 1, and NAT from any internal IP not covered by SAT rules
Wan 1 IP 2 = SAT to/from internal server 2
Wan 1 IP 3 = SAT to/from internal server 3

Wan 2 IP 1 = SAT to/from internal server 4
Wan 2 IP 2 = SAT to/from internal server 5
Wan 2 IP 3 = SAT to/from internal server 6
Logged

sergiomnt

  • Level 1 Member
  • *
  • Posts: 13
Re: DFL-800 using 2 wan ports, but not as failover
« Reply #1 on: September 06, 2013, 11:28:50 AM »

Hello,

By default all those coming from an interface around the same interface, you have to define by which WAN to your LAN will leave. Sample SAT rule:

# Name Action Source interface Source network Destination interface Destination network Service
1 SAT_WAN1 SAT wan all-nets core IP_WAN1 all_services
2 Allow_SAT Allow wan all-nets core IP_WAN1 all_services

New IP Address you put the server IP.

Thank you.
Sérgio de Souza
sergio@masternet.com.br
Logged

chechito

  • Level 3 Member
  • ***
  • Posts: 193
Re: DFL-800 using 2 wan ports, but not as failover
« Reply #2 on: September 07, 2013, 01:26:01 PM »

sounds like a routing problem to me.

For incoming connections you must have a routing table and corresponding routing rule to each traffic incoming connections.

Logged