• February 24, 2025, 11:06:05 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: WAN2 routing problem  (Read 6235 times)

ryan

  • Level 1 Member
  • *
  • Posts: 2
WAN2 routing problem
« on: December 01, 2009, 08:24:56 PM »

I have setup WAN1, and that is passing data through(http/https) but I can't get any data through WAN2 (SFTP - TCP 22).

The log is returning:

2009-12-02 14:54:28   Warning      ARP 300049   Default_Access_Rule   wan2   [Gateway_IP][Wan2_IP]   invalid_arp_sender_ip_address drop
hwsender=00-09-0f-09-00-05 hwdest=ff-ff-ff-ff-ff-ff arp=request srcenet=00-09-0f-09-00-05 destenet=00-00-00-00-00-00

I have set up as much as I can to match WAN1:


The SAT rule the Destination IP is going to a internal IP address.  The website and webservice traffic (Wan1) was using https://ip:port/ because I have not setup multiple ips per port yet, which I will do.

Any thoughts?

Thanks.
Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: WAN2 routing problem
« Reply #1 on: December 02, 2009, 09:43:53 AM »

If you want to forward services over a interface which is not used for your default route you will need to set up a routing table where that interface's default route comes first and write a routing rule where incoming traffic for that interface uses your new secondary routing table for it's return traffic.

BTW, nice 1600!
Logged
non progredi est regredi

ryan

  • Level 1 Member
  • *
  • Posts: 2
Re: WAN2 routing problem
« Reply #2 on: December 02, 2009, 03:01:24 PM »

Keeping the above settings I tried a few different options with the routing table and routing rules.  None worked - still got the same log message.  Currently I have the following setup with the above settings:



Which part of my setup is wrong?

Thanks.
Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: WAN2 routing problem
« Reply #3 on: December 07, 2009, 11:21:15 AM »

I don't see any immediate problems.  Call this in, I don't want to put you through any more down time than is needed, and this is going to get nitty gritty quick.
Logged
non progredi est regredi