Can see host but nil to peers

[SJAndrew]

The header says it all.

I have a new router (D-Link DIR-655). I don't know if it's the router or the latest FAF update (today). I could play fine with my old WRT54G router, but this new one (combined with the new FAF update) does not work/

I don't have trouble connecting to FAF games, but when I do I'm nil to all other players besides the host.

I have the proper ports forwarded, I have tried DMZ without luck. I have the same client settings as I had before this router.

Any ideas??????

[thygrrr]

Most likely the router. Can't be entirely sure, though.

Connect to a game where you have a bunch of nil-Pings, leave the game, and use the BETA->Report A Bug feature to send the logs.

[SJAndrew]

I'm pretty sure it's the router too.

I changed more settings and now have been able to see peers just fine.

For what it's worth, I have the DIR-655 router. I changed the following to get it to work:

1) I changed the port forwarding to forward to an IP within the DHCP range. This should have nothing to do with anything, but I read somewhere that it's necessary

2) I changed NAT to be port and IP non-specific (this differs from the defaults).

I think #2 might be what helped, but to be honest, this router sucks so who knows. It's feature rich but very idionsyncratic and buggy.

[thygrrr]

You need to port forward to the exact IP of the computer you want to play on with that port.

You can usually configure DHCP to hand out fixed permanent leases to certain PCs. It's what causes issues for many people, sometimes their smartphone or digital video recorder grabs their PC's DHCP lease and all the port forwarding in the world won't help them if they're forwarding to the wrong address.

[SJAndrew]

I understand.

I've been port forwarding for 10+ years.

They way I used to do it was to have my main machine (192.168.1.100) as a static IP (client based) and the DHCP pool as 192.168.1.150-192.168.1.199. This will not work (apparently) with this router when trying to forward outside of your pool.

This setup worked with every other router I've ever used.

I now have the pool as 192.168.1.50-192.168.1.50 with a DHCP reservation for my main machine and my main machine setup for DHCP (i.e. automoatically obtain IP etc). That change. combined with the small NAT tweaks I described earlier, have it working (for now).

Whether the client IP is handed out via DHCP or static client side (so long as there is not a conflict via DHCP), this should not affect port forwarding.

I know this is not a PC issue as I had the same PC behing the WRT54GS without issue (eg it's not a software firewall issue or something like that).

This is just a goofball router.

[thygrrr]

Sorry, it just wasn't clear from your previous message.

[Ze_PilOt]

Can you add that to the wiki (with your router brand,....) ?

[SJAndrew]

The router brand is d-link.

I will take some screenshots over the weekend and post.

I know other people have had issues with this router and FAF. Check out here:

viewtopic.php?f=3&t=288&start=0