Recluse,

I tried almost every combination I could think of and the best it got was to the 2 bars before entering the cockpit. My host was behind the DL router firewall, and the client was a dialup.

I tried the GAMING only scenario with:
- GAMING (port ranges forwarded to a LAN IP)
192.168.0.109 26210 TCP/UDP
192.168.0.109 47624 TCP/UDP
192.168.0.109 2300-2400 TCP/UDP
- result was the two bars

and tried the above and differnt combos of triggering ports:(trigger input ports to input ports on all LAN computers)

- SPECIAL APPLICATIONS
TCP/UDP 26210 TCP/UDP 2300-2400
TCP/UDP 47624 TCP/UDP 2300-2400
- results are too many triggers and rotating clock icon will lock up.

Thats why Im asking Reverant to translate what he has. His set up seems to be like DLINK's GAMING pass through section where 3 port ranges are defined, then mapped to his LAN address. I dont see triggering at all in his setup.

AV8R,

the DLINK setup that matches mine is:

- GAMING (port ranges forwarded to a LAN IP)
192.168.0.109 26210 TCP/UDP
192.168.0.109 47624 TCP/UDP
192.168.0.109 2300-2400 TCP/UDP

Heh! This is why I think it is 'MAGIC'. Some Routers just don't seem to work, while others do even though Port Forwarding is setup identically.

As we have observed, several SMC routers fail even on DMZ, as does MY Netgear router while Reverant's works.

D-Link seems to work sometimes on DMZ but not with Port Fwd.

I am hoping that the great success enjoyed by Linksys owners will be shared by my upcoming Linksys WRT54G...but I don't really know WHICH models have worked for others...

Recluse

Im taking the new $150 buck DLG-4300 Gaming Dlink router back to the store. Its WORSE than my older Dlink DI-614+ for both LB2 and even VPN to my work.

OK folks fess up, if youre router works behind the firewall, list your models. Im gunna buy one that works. Im done beta testing them myself.

At least I can host in the DMZ and behind ZoneAlarm. And can be a client behind the router firewall. At no additional costs!

How was the Linksys routers? Did they all work or only specific models?

Mine is a Netgear FR328S . It works. ;-)

I have a DI-614, DI-604 and a Netscreen 5XT, none of them work.

Now what I did was buy a hub, put it between my Cable Modem and Home Firewall.

I have TWO NICs in my PC, one on the hub, one on the firewall. I simply switch between the two when I want to host stubborn games. Luckily my ISP dishes out TWO IP's from the modem. You could always check, some do.

ARRRGHHHH!! Connected the Linky,

Dialed up on on LAN machine, hosted through the Linky...

THE DREADED 2 BULLETS!!

Tried DMZ...

THE DREADED 2 BULLETS!!

Gonna have to find a successful Linksys owner and see if there are some other settings that need to be on. This is very odd!!

I know the ports were being fwded because first I tried without the ports properly fwd'ed (tried to trigger them) and the client couldn't even FIND the host. After I fwd'ed the ports, the client linked up immediately...but locked up on FLY..

Now I am pissed


Recluse

I know your pain Recluse.

Your Dlink 614 doesnt let you go to the DMZ like I do?

I say we go recon mode and steal Reverants router


Rev,
I think this will be my next router victim...
http://www.netgear.com/products/details/WPNT834.php

I don't have a D-Link... it's a LINKSYS. It DOES have DMZ mode, but it didn't help with LB2

I just upgraded to the latest official Linksys Firmware, and maybe I will try again. I intend to upgrade to some 3rd Party firmware which, among other things, gives more Port Forwarding entries.

Interesting how different Router manufacturer's do things! My old SMC and the current Linksys WRT54G have only limited slots for port forwarding, though the Linksys can use RANGES. The Linksys only has 10 entries. The Netgear seemed pretty much unlimited..I had 26 configured.

Recluse

Found a router of the same model as Reverant for 20 bucks.
Looks aint everything...



If that dont work, Im sticking with the DMZ method.

AV8R

That should work pretty o' well!

Its only a firewall...

So I have to get it to work with my other hardware:

-> Cable Modem -> NetGear Firewall -> DLink Wireless Router -> USB Wireless Access Point -> PC

So I guess... that means putting the PC that will be running LB2 into the DLink's DMZ so that its firewall is out of the loop, but in the path of the NetGear firewall. This right Rev?

Else, is there a way to turn off the FW for the DLink router altogether?

I have both a Linksys WRT54G wireless/router combo and the Linksys BEFSR41 EtherFast Cable/DSL Router with 4-Port Switch, along with 4 EZXS55W EtherFast 10/100 5-port Auto-Sensing Switches on my home network ( 12 systems...don't ask.LOL ).
I will try and test to see if I can host/client behind my BEFSR41 router tonight, but I need to know what to do to test this? Can someone write down what I need to do to test for host settings?

Let me know if it works with the WRT54G as well...
I have a V3 currently running the latest Linksys firmware 4.20.7. Haven't yet tried it with the new firmware, but it failed with the older 3.30(?) firmware.

Basically:

Open ports

26210 TCP
47624 TCP
2300-2400 TCP/UDP

Set up a host. Connect to the host with a client. Make sure the HOST and CLIENT are not on the same network subnet and preferably with an Internet WAN address for the HOST.

The issue seems to relate to the fact that LB2 HOSTS after the initial synch up, tell the CLIENTS to connect to their LAN IP rather than a WAN IP that made the initial connection. Some routers seem to survive this translation while others fail as the clients bang away a Class C address never getting anywhere..

LAN connections all on the same subnet behind a router have no issues...just where there is some NAT going on.

You are probably more network Savvy than I am given your configuration, so you can probably simulate this all within your LAN and Subnets.

The initial Synch and all the mission planning goes fine..when the FLY helmet is pressed, the fun begins

You can shortcut the process by trying the DEATHMATCH icon..this accomplishes the same thing.

So:

Create a mission, any way you want and try the FLY helmet...with or without any mission planning steps.

Alternatively just try the DEATHMATCH helo icon.

If you get into flight, things are fine. If the screen stops at 2 progress 'bullets' and hangs for awhile, then the HOST gets into the cockpit and the CLIENT crashes to desktop, things are not working

Try DMZ mode as well. Some folks (AV8R) get it to work in DMZ but not port fwding (perhaps other ports are needed?) but most of us can't get it to work with Port Fwd OR DMZ.

Hehe maybe you can run ETHEREAL on your machine, or stick in a HUB and use promiscuous mode on another machine and trace the traffic too!

Recluse

Ok ran ethereal and found that the two systems communicating also used the following ports when not using the router:
TCP:
1196
26210
1248

UDP:
1203
1233
26210
But when I added the router and tried to host from behind it, I got the 2 bullets and thats it. Furthermore, I noticed you cant move pilots from one helo to another in the mission planner behind the router vs being able to join the same AH64 with two of my systems without the router.
Not being able to move around in the mission planner let me know that something at this point was not syncing up.
Tonight I tried the Linksys BEFSR41 router. Tomorrow I will try the WRT54GS router to see how it responds.

Interesting! My NETGEAR router didn't distinguish between UDP/TCP and always opened both, so the 26210 piece was taken care of. Not sure where the other ports are coming from. Can you tell if they are 'standard' or randomly allocated? Are the opened OUTBOUND from the HOST or INBOUND?

Never ran into the issue with joining the same chopper or any other issues in the MISSION PLANNER except for the limitation that the HOST always needed to be the PILOT and could not be CP/G.

Thanks for taking the time and effort to test!!

Recluse

You can try running this program on your host.

http://www.sysinternals.com/Utilities/TcpView.html

It will help you identify what software has auxillary ports open on the PC.

I will be doing some more testing of this tonight to try and nail down whats going on.

Lets also be clear as to the following when doing the port sniffing:

- LAN or Dialup or Internet (broadband)
- Host or Client information
- What ports were open before LB2 was invoked