Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[war59312]

Hi,

Well just great. Been on 1.11 since forever and figured I'd update finally on my home router and now xbox 360 no longer works.

Wow, just wow!

Code: [Select]

[INFO] Fri Jan 29 23:11:19 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:19 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:17 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:17 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:15 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:15 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:13 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:13 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:11 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:11 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:08 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:08 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:08 2010 Blocked incoming TCP packet from 70.29.130.243:62694 to me:53346 as RST:ACK received but there is no active connection
[INFO] Fri Jan 29 23:11:06 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:06 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:04 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:04 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:02 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:02 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Fri Jan 29 23:11:00 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.1.110:3074 to 65.55.42.180:3074
[INFO] Fri Jan 29 23:11:00 2010 Dropped packet from 192.168.1.110 to 65.55.42.180 (IP protocol 17) as unable to create new session
Now I'm ticked..

Will

[Sammydad1]

Hi,

How do you have your 360 connected ?  Did you use DNS Relay or something maybe you forgot to re-set after the upgrade ?

SD1

[war59312]

Nope same exact settings. I took screen shots of every page before I upgraded.

Anyways, I turned on Universal Plug and Play (UPnP) to see if that would do anything.

And wtf do you know xbox 360 works just fine now. So does that mean port forwarding is broke, about to test.

Update: O.K thank god its just the xbox 360 that had the problem, all other ports that I have forwared are working just fine. Confirmed using http://www.canyouseeme.org/ .

[avigar]

Nope same exact settings. I took screen shots of every page before I upgraded.

Anyways, I turned on Universal Plug and Play (UPnP) to see if that would do anything.

And wtf do you know xbox 360 works just fine now. So does that mean port forwarding is broke, about to test.

Update: O.K thank god its just the xbox 360 that had the problem, all other ports that I have forwared are working just fine. Confirmed using http://www.canyouseeme.org/ .

Have you tried to assign a static IP to your XBox360, then place it in the DMZ? BTW, has your connection been steady or are disconnects occurring intermittently like mine are? I've also recently flashed to v1.33NA.

[war59312]

Nope working just fine as is. And yes it has always had a static IP.

Also, worked just fine when I tried placing in DMZ.

Just annoying. I don't really like UPnP. I like to know what ports are open on my router and dont like apps opening them. And don't really want my xbox in DMZ.

But seems with this firmware I have no choice.

Just stinks this happened. I wonder what broke to do this.

[Cobra]

Actually, UPnP is better then port forwarding.

When you port forward those ports are always open even when you are not using them.
Basically you have permanent holes poked through the firewall.

With UPnP the ports open when the  UPnP enabled connection asks to open them and as soon as you stop using the connection the ports close again.

[war59312]

Thankfully, you're wrong.

If that were the case ShieldsUp, over at grc.com would not show currently forwarded ports, but not being used ports, as stealth. Would in fact show those ports as open. Test for yourself if you wish.

For example if I have port 80 forwarded, traffic is only allowed in when I'm actively running a web server. Once I turn off the web server the router, the firewall, blocks it. The forwarded port is no longer valid.

Forwarding ports only become active once data has already been sent out those ports. Or an application on your system, within your network, is actively running on that port.

This is true, because we are running NAT routers. Port forwarding is not for opening wholes in the firewall per say, it's for translating private addresses into public addresses, and vice-versa, or NAT traversal if you will.

Basically the same as UPNP, only UPnP does it automatically for you. I personally just like more control over it.

[bigeyes0x0]

war59312: That depends on the firewall you're running on your server. Only a process aware firewall will do what you said, otherwise when a tcp syn packet goes to the forwarded port (using normal method) on the dlink will return a close port reply instead of dropping the syn packet and does nothing.

Forwarding ports only become active once data has already been sent out those ports. Or an application on your system, within your network, is actively running on that port.

This is actually port triggering port forwarding method, it is listed as Application Rules, a misleading name IMO,  in the DIR-655. The port forward page on the D-Link will always leave holes in your router firewall, same for Virtual Server.

UPnP is not the best thing in the world either, a trojan can use it to open backdoor. On the other hand, if you let something malicious inside your network already, you're already screwed, UPnP is just a method to screw you more.