Author Topic: Multi WAN (Connection) Support  (Read 2386 times)

Offline TheGreatVirus

  • Contributor
  • ***
  • Posts: 12
Multi WAN (Connection) Support
« on: December 08, 2007, 11:05:57 am »
Multi WAN (Connection) Support

--------------------------------------------------------

A simple way to simply designate server threads to different ethernet/wireless adapters thus allowing the use of multi WAN IPs.

Intergrated & Designated to Alt.Binz thus eliminating the need for OS intergration.

Reconfigured connection status displays for Multi WAN support.

Distinguished adapter colors for speed graph thus allowing distinction between connections. Possible Settings option to enable combined stat instead of colored multi-lined stat.

Connections Panel needs new column to display real adapter name or the designated user given name.

Offline pilotsnipes

  • Contributor
  • ***
  • Posts: 32
Re: Multi WAN (Connection) Support
« Reply #1 on: December 08, 2007, 01:37:14 pm »
Excellent request. +1

As long as I can assign different servers to each LAN that would be brilliant.

Offline TheGreatVirus

  • Contributor
  • ***
  • Posts: 12
Re: Multi WAN (Connection) Support
« Reply #2 on: March 13, 2008, 07:09:35 am »
bump.

I would be really happy if you guys would consider this. At least offer a way to set which adapter to bind to and maybe I can launch two sessions for mult wan.

Offline DM8Mydog

  • Contributor
  • ***
  • Posts: 48
Re: Multi WAN (Connection) Support
« Reply #3 on: April 02, 2008, 01:10:17 am »
a potential workaround for this can be windows 'route' (cmd> route help for details),
the thing is you'd have to be using a service that has two different target IPs for the server
example:
Code: [Select]
Name:    news.usenetserver.com
Addresses:  208.49.82.187
          208.49.82.220
          208.49.80.60
          208.49.80.124
          208.49.80.188
          208.49.82.28
when I used to use this I had two valid gateways on my LAN, gateway1 (10.100.100.71) and gateway2 (10.100.100.51), (they where linked over a metro WLAN)
the cmds are something like this:
route add ip1 gateway1
route add ip2 gateway2
or for instance:
route add 208.49.82.220 10.100.100.71
route add 208.49.80.60 10.100.100.51

I was on XP SP2 when I was doing that and it seemed to forget the manual set route every few hours or at least once every two days, dunno specifically why, but to workaround that I created a scheduled task that would run a batch script containing those two lines ( plus an "@echo off" line at the top so it'd be silent)
same thing should work in windows Vista, and perhaps even win2k.

to remove a route use: route delete IP
to see current/active routes use: route print
Note, some NSPs don't allow connection over multiple IPs, ie: the Giganews Unmetered package only allows a user to connect from one IP at any given time.