rz8168
join:2002-04-28
Arcadia, CA
 ·altrio
edit:
March 16th, @09:05PM
| [Help Me] DI-LB604 MSN contacts problem/WAN binding problem
When in load balancing mode, msn messenger unable to load contacts. Contact list is empty.... but once I bind any destination server ip to one of the WAN port, contacts appear without any problem. Another issue I have is, if I bind any server IP - for example: yahoo.com IP - to one of WAN port, and then once my computer connect to yahoo.com in web browser, router will bind all connections from my computer to that WAN port, therefore, load balancing will fail to function properly on my computer.
FYI: LB604 is using latest version 1.0.1 firmware.
Does anyone have same issue with destination IP - WAN port binding? |
|
slpip
join:2007-02-20
Springfield, VA | You put too much IP binding limitation on the router filter caused the problems. You should just use the web site filter, such as yahoo.com, instead of IP address for your firwall filter. |
|
rz8168
join:2002-04-28
Arcadia, CA
·altrio
| reply to rz8168
I'm not trying filter anything. I'm just setting an example of binding a connection. And obviously I'm not putting too much IP binding limitation on the router, and IP-Port binding doesn't not function to filter the connection out, it is to bind a connection to a certain WAN port by the rules that I specify. Besides, where do you see that I mention "filter" in first post? |
|
Wcool
join:2007-03-24
00000
| I have a DI-LB604 as well and similar problems.
Maybe we can help each other.
Load balancing is off for me but it seems sometimes it take WAN1 sometimes WAN2 (that is normal I guess).
I guess what happens is: you connect to MSN messenger, let's say via WAN1, and a little later when a new connection is opened (for your contact list), WAN2 is used. Thus you get another external IP. And MSN Messenger fails.
I am a bit confused what you mean with binding, I have no PPPoE (2 cable modems here basically) thus do not know if it works.
I tried to solve it by using static routing. Did you try that?
For instance, if Yahoo = 200.201.202.203, add this rule in Static routing:
Destination: 200.201.202.203
Mask: 255.255.255.255
Gateway: Your ISP's gateway (for WAN1 or WAN2)
Interface: WAN1 (or WAN2)
This is my setup (x for anonymity):
Interface IP Address Subnet Mask Gateway DNS IP Address
WAN 1 83.x.x.x 255.255.255.0 83.x.x.1 83.x.x.x
WAN 2 10.15.144.2 255.255.255.128 10.15.144.1 195.x.x.x
Interface IP Address Subnet Mask
LAN 192.168.0.1 255.255.255.0
Ok and now my problem: I expect this to work but it doesn't
I wanted to redirect all 10.x.x.x packets to WAN2 (an amateur wifi network)
So I added:
Destination: 10.0.0.0
Mask: 255.0.0.0
Gateway: 10.15.144.1
Interface: WAN2
Now I CANT ping any 10.* address anymore. Before I added the rule, sometimes I can ping a 10.* address, sometimes not.
It is almost as if the router has a split personality, sometimes using WAN1, sometimes WAN2. Even if you tell it NOT to!
I think this is a BIG bug in the DLink and I already wrote 4 times to Dlink support. BUT THEY DON'T REPLY!
If you could help me buy explaining what binding exactly does (what is the difference here with routing?), I will give it a try and report back. Maybe you can try the routing?
Thanks, Jeroen |
|
rz8168
join:2002-04-28
Arcadia, CA
·altrio
edit:
March 31st, @05:55PM
| I tested the static route but no success. I went back to v1.00 firmware and MSN messenger works fine. reflash v1.01 to router, msn messenger contact list is gone again.
Port binding is similar to static route that you set up.
It's located in Tools>Misc>Set Protocol and Port Binding.
If I try to bind a connection going to Yahoo to WAN1,
src address=192.168.0.100
dst address=200.201.202.203
protocol=all
port range=0-65535
Port=WAN1
Suppose what it does is bind all connections from 192.168.0.100 to 200.201.202.203 to WAN1, but instead, it binds ALL connections from 192.168.0.100 to WAN1 regardless what dst address is. Contacted DLink, they suggested me to contact DLink Business Support. I will call them next week and see what are they going to do about it. |
|
Wcool
join:2007-03-24
00000 | Funny, I got the exact same answer from DLink: call Business support. Haven't done so yet.
I will try the binding tomorrow and let you know. It's late here |
|
DILB604_Help
join:2006-08-21
| reply to rz8168
Hello,
For all the binding rules, try not setting the port value 0 (start from 1), port value 0 implies an unspecified source or destination.
Regarding the static routing and https web sites issues, the latest firmware has fixed it you might get it from me, just leave your email on the IM. |
|
Wcool
join:2007-03-24
00000
| That would be great DILB604_Help, I sent you my details...
@rz8168: I tried this:
Protocol & Port Binding
Enable : X
Source IP : 192.168.0.2 (my desktop computer)
Dest. IP : 66.94.234.13 (yahoo.com)
Subnet Mask :255.255.255.0 (this should bind all addresses in the 66.94.234.X range
Protocol : ALL
Port Range : 1 - 65535
WAN : WAN2
Now, I have nothing at the moment on WAN2 (it didn't work  , so I would expect I can't ping yahoo.com now anymore, but anything else I should.
After creating the rule, I can't ping ANYTHING anymore.
Looks like it confirms your problem  |
|
BustANut
join:2003-01-01
North Tonawanda, NY
edit:
April 2nd, @10:59AM
| reply to DILB604_Help
I have major HTTPS problems using the v1.01 firmware, December '06 build. The HTTPS problems are entirely performance-related; for example, when making a purchase at »https://www.every-single-damn-https-website.com, the pages either do not load (due to connection failures) or they load VEEERRRRRY slowly. This problem is *only* exhibited by the December 2006 v1.01 firmware build. The beta firmware (v1.01 from August 2006) does not have these HTTPS problems. Binding to a specific WAN port does not resolve the HTTPS problems with v1.01 (Dec. 06 build), but this always seems to be the textbook answer D-Link provides for fixing this issue. D-Link, STOP assuming that port binding is the be all, end all for fixing HTTPS issues. It is your firmware, NOT port binding configuration!!!
I am stuck using a beta version of 1.01 (August 2006 build) with the LB604, and just recently (within the past week or so) the router has begun crashing regularly (UPnP is DISABLED!!!), requiring a power cycle to get things back up and running again. Crashing from a router is absolutely intolerable and should NEVER occur. The crashing behavior is consistent with the latest 1.01 (December 2006 build) as well (reflashed just last week), so I am beginning to think that either both firmware versions are flawed (beyond just the HTTPS issues), or I am experiencing hardware failure with this router.
Not to step on D-Link too much, but having access to my home LAN (remotely) is critical, so I wound up purchasing a Netgear FVS124G load balancing router as I could no longer tolerate the crashing of the LB604. Just a tip for D-Link -- the Netgear FVS124G has a bind by protocol feature that seems absolutely necessary for *any* load balancing multi-WAN router, especially for those IP-sensitive apps, such as VPN/PPTP, and RSA TokenID authenticator-based websites. When BIND by protocol is configured on the FVS124G, I have no problems whatsoever with VPN, PPTP, or any IP-sensitive HTTPS websites. Not allowing "bind by protocol" within the LB604 configuration is a HUGE drawback, the omission of this feature absolutely neuters the functionality of the LB604. D-Link needs to step it up and add this functionality if the LB604 is to be a viable option for dual WAN load balancing.
I'd love to be able to send the FVS124G back if D-Link had firmware that would solve both the crashing and HTTPS issues, so feel free to send the firmware to omni360 at gmail dot com if there is any hope of me ever using the LB604 again... |
|
Wcool
join:2007-03-24
00000
| At the moment I don't use WAN2 anymore. and https works perfectly.
I never used 2 WAN ports long enough to notice any problem with https.
I got an answer from D-Link asking me to try a couple of things. I will pay some attention to this https problem as well, and see if I can reproduce it. |
|
BustANut
join:2003-01-01
North Tonawanda, NY
| I'm testing out a new firmware now...so far it is working great. Completely changed my tune regarding performance of the DI-LB604. Also noticed the port/protocol binding area under "Misc.", I did not know that existed up until yesterday (not sure if this feature was in the original firmware). At any rate, the beta of 1.02 looks promising for the DI-LB604, as long as it can stay crash-free for the next few weeks, I will be returning the Netgear FVS124G. |
|
Wcool
join:2007-03-24
00000
| Well the new firmware didn't solve my problem
It was meant to solve the HTTPS problem, so I am not surprised. I tried binding as well as static routing but it didn't work.
D-Link told me that the router is "not designed" for what I want to do
I managed to solve my problems by using a 2nd router and I have a rule that directs all 10.X.X.X traffic to that gateway.
So basically I bought an expensive Dual Wan router that I use as a normal router and had to buy a 2nd router. Waste of money. Ah well, can't win them all. |
|
DILB604_Help
join:2006-08-21
| Hello Wcool,
Just what exactly is your scenario ? As I told you in the mail I've succeeded in reproducing your problem and it's been working ok with the latest firmware. Is there anything I've overlooked ? would you mind mailing me your deteails ? I don't know which DLink branch tech support you've contacted but I do know the only thing DLink America tech support do is to put your call on hold because they don't have a least idea about networking especially for dual wan devices, that's why I am here to help ! |
|
DILB604_Help
join:2006-08-21
| reply to Wcool
By the way, did you notice that the static routing rule on the latest firmware has the options to set the routing mode to meet your need (NAT mode to change the source IP address, Transparent mode to do just pure routing withour replacing IP) have you tried that too ? |
|
Wcool
join:2007-03-24
00000
| Thanks for the offer.
Well, NAT or Transport didn't make any difference.
I guess Transport mode is what we want here
Basically, I want to direct any 10.X.X.X ip packet to WAN2 interface. Still didn't work. If I set up the routing, NO packet in the 10.x range can be sent.
I sent you some more details. |
|
rz8168
join:2002-04-28
Arcadia, CA | @Wcool
I haven't got the latest firmware yet, but as soon as I received it, I will test it out and see if the problem still persist.
@DILB604
I've sent you an IM with my email address, thanks. |
|
rz8168
join:2002-04-28
Arcadia, CA | reply to rz8168
I flashed the beta firmware into LB604. Port binding problem appeared to be fixed. But the router GUI interface is slower than previous firmware. But stability is what I concern the most.... it rebooted itself after 12 hours using the new firmware. |
|
DILB604_Help
join:2006-08-21 | rz8168,
You might need to do a factory reset and MANUALLY input your original settings all over again it seemed to be a corrupted config file to me. you actually can take a look at the config file yourself see if there is any weired values in it. |
|
rz8168
join:2002-04-28
Arcadia, CA
·altrio
| I think it was the power, probably a flicker or something. After that reboot, I left it up and running, so far so good. It's been up for 3 days. Looks solid. Hope it'll outperforms RV082 and Xincom in stability and performance. Anyway, thanks for the latest firmware.... |
|
Wcool
join:2007-03-24
00000
| reply to rz8168
Well, I got more instructions from DILB604_Help and I got it to work.
The binding actually does work it seems.
This is what I entered to route 10.x over WAN2
The static routing rules have been removed.
Protocol & Port Binding List
Source IP Destination IP / Subnet Mask Protocol Port Range WAN
0.0.0.0 10.0.0.0/255.0.0.0 ALL 0~0 WAN 2
Thanks a lot for your help, DILB604_Help, I wish D-Link got employees like you, as they couldn't resolve it. |
|
