Comments for netnix.org http://netnix.org Networking and Unix Tue, 15 May 2012 10:52:17 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Understanding PS3 NAT Types by scott http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-67 scott Tue, 15 May 2012 10:52:17 +0000 http://netnix.org/?p=40#comment-67 Ok Question??? my nephews ps3 is NAT2 OPEN, COD black ops, in his room running off wireless (belkin router/modem) My ps3 is NAT2 MODERATE with same game, but i am using mine with the ethernet cable, also i have port forwarded my ps3 with a static IP, now is it possible to make both ps3s run OPEN, any help would be great cause i have searched over and over and cant seem to find anything cheers ppl Ok Question??? my nephews ps3 is NAT2 OPEN, COD black ops, in his room running off wireless (belkin router/modem)
My ps3 is NAT2 MODERATE with same game, but i am using mine with the ethernet cable, also i have port forwarded my ps3 with a static IP,
now is it possible to make both ps3s run OPEN,
any help would be great cause i have searched over and over and cant seem to find anything
cheers ppl

]]> Comment on Understanding PS3 NAT Types by Josh Post http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-61 Josh Post Tue, 20 Mar 2012 00:31:04 +0000 http://netnix.org/?p=40#comment-61 I've noticed when it comes to gaming consoles, and PC gaming clients, if you use a Gateway (Combination Modem/Router) you will have increased issues, due to the companies locking out features, and hardware not supporting gaming applications. Best setups to use are seperate modems and routers, where the modem is just a straight pass through, and the router is made within the last few years, where it will support the modern consoles and gaming clients. Like my router is a DIR 632 from Dlink and I never have a problem running gaming applications on my PC, xbox 360 or PS3. On the gateway I previously had, I had loads of issues. Its better to learn about networking, and do the connections yourself, rather than having the craptacular hardware from the ISP. Also, some ISPs don't have support for gaming networks, and may not have the necessary bandwidth continuity. If they can provide a stable 1500 MTU to your house, then you should do fine. I’ve noticed when it comes to gaming consoles, and PC gaming clients, if you use a Gateway (Combination Modem/Router) you will have increased issues, due to the companies locking out features, and hardware not supporting gaming applications. Best setups to use are seperate modems and routers, where the modem is just a straight pass through, and the router is made within the last few years, where it will support the modern consoles and gaming clients. Like my router is a DIR 632 from Dlink and I never have a problem running gaming applications on my PC, xbox 360 or PS3. On the gateway I previously had, I had loads of issues. Its better to learn about networking, and do the connections yourself, rather than having the craptacular hardware from the ISP. Also, some ISPs don’t have support for gaming networks, and may not have the necessary bandwidth continuity. If they can provide a stable 1500 MTU to your house, then you should do fine.

]]> Comment on Understanding PS3 NAT Types by pgibson http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-50 pgibson Tue, 07 Feb 2012 16:33:47 +0000 http://netnix.org/?p=40#comment-50 My router happens to run OpenBSD, this was the only guide online I could find that could give me a clue what I was doing wrong. I also learned a bit more about NAT! I never knew that port address translation existed, after about 40 minutes looking through man pages, I figured out the 'static-port' option. It works perfectly now! Much thanks to <a HREF="http://netnix.org/author/cmason/" rel="nofollow">Chris</A>! In case y'all are interested: <CODE> [ root@********* +4F314C18 etc ]$pfctl -sr . . . pass in inet proto tcp from any to (fxp1) port = www flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = www flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = https flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = https flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = smtps flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = smtps flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = 983 flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = 983 flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = 5223 flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = 5223 flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port 10071:10080 flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port 10071:10080 flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = 9293 flags S/SA keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = 9293 flags S/SA keep state nat-to (fxp1) round-robin static-port pass in inet proto udp from any to (fxp1) port = 3478 keep state rdr-to 192.168.2.146 pass out inet proto udp from 192.168.2.146 to any port = 3478 keep state nat-to (fxp1) round-robin static-port pass in inet proto udp from any to (fxp1) port = 3479 keep state rdr-to 192.168.2.146 pass out inet proto udp from 192.168.2.146 to any port = 3479 keep state nat-to (fxp1) round-robin static-port pass in inet proto udp from any to (fxp1) port = 3658 keep state rdr-to 192.168.2.146 pass out inet proto udp from 192.168.2.146 to any port = 3658 keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = 10070 flags S/SA keep state rdr-to 192.168.2.146 pass in inet proto udp from any to (fxp1) port = 10070 keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = 10070 flags S/SA keep state nat-to (fxp1) round-robin static-port pass out inet proto udp from 192.168.2.146 to any port = 10070 keep state nat-to (fxp1) round-robin static-port pass in inet proto tcp from any to (fxp1) port = 3074 flags S/SA keep state rdr-to 192.168.2.146 pass in inet proto udp from any to (fxp1) port = 3074 keep state rdr-to 192.168.2.146 pass out inet proto tcp from 192.168.2.146 to any port = 3074 flags S/SA keep state nat-to (fxp1) round-robin static-port pass out inet proto udp from 192.168.2.146 to any port = 3074 keep state nat-to (fxp1) round-robin static-port pass in inet proto udp from any to (fxp1) port = 81 keep state rdr-to 192.168.2.146 pass out inet proto udp from 192.168.2.146 to any port = 81 keep state nat-to (fxp1) round-robin static-port pass in inet proto udp from any to (fxp1) port = 3075 keep state rdr-to 192.168.2.146 pass out inet proto udp from 192.168.2.146 to any port = 3075 keep state nat-to (fxp1) round-robin static-port . . . </CODE> In my setup; fxp1 is the NIC connected to my ISP and 192.168.2.146 is the IP address of my PS3. Probably not useful to most people, but hopefully it finds a fellow BSD nerd ;) My router happens to run OpenBSD, this was the only guide online I could find that could give me a clue what I was doing wrong. I also learned a bit more about NAT! I never knew that port address translation existed, after about 40 minutes looking through man pages, I figured out the ‘static-port’ option. It works perfectly now! Much thanks to Chris!

In case y’all are interested:

[ root@********* +4F314C18 etc ]$pfctl -sr
. . .
pass in inet proto tcp from any to (fxp1) port = www flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = www flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = https flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = https flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = smtps flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = smtps flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = 983 flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = 983 flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = 5223 flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = 5223 flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port 10071:10080 flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port 10071:10080 flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = 9293 flags S/SA keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = 9293 flags S/SA keep state nat-to (fxp1) round-robin static-port
pass in inet proto udp from any to (fxp1) port = 3478 keep state rdr-to 192.168.2.146
pass out inet proto udp from 192.168.2.146 to any port = 3478 keep state nat-to (fxp1) round-robin static-port
pass in inet proto udp from any to (fxp1) port = 3479 keep state rdr-to 192.168.2.146
pass out inet proto udp from 192.168.2.146 to any port = 3479 keep state nat-to (fxp1) round-robin static-port
pass in inet proto udp from any to (fxp1) port = 3658 keep state rdr-to 192.168.2.146
pass out inet proto udp from 192.168.2.146 to any port = 3658 keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = 10070 flags S/SA keep state rdr-to 192.168.2.146
pass in inet proto udp from any to (fxp1) port = 10070 keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = 10070 flags S/SA keep state nat-to (fxp1) round-robin static-port
pass out inet proto udp from 192.168.2.146 to any port = 10070 keep state nat-to (fxp1) round-robin static-port
pass in inet proto tcp from any to (fxp1) port = 3074 flags S/SA keep state rdr-to 192.168.2.146
pass in inet proto udp from any to (fxp1) port = 3074 keep state rdr-to 192.168.2.146
pass out inet proto tcp from 192.168.2.146 to any port = 3074 flags S/SA keep state nat-to (fxp1) round-robin static-port
pass out inet proto udp from 192.168.2.146 to any port = 3074 keep state nat-to (fxp1) round-robin static-port
pass in inet proto udp from any to (fxp1) port = 81 keep state rdr-to 192.168.2.146
pass out inet proto udp from 192.168.2.146 to any port = 81 keep state nat-to (fxp1) round-robin static-port
pass in inet proto udp from any to (fxp1) port = 3075 keep state rdr-to 192.168.2.146
pass out inet proto udp from 192.168.2.146 to any port = 3075 keep state nat-to (fxp1) round-robin static-port
. . .

In my setup; fxp1 is the NIC connected to my ISP and 192.168.2.146 is the IP address of my PS3.
Probably not useful to most people, but hopefully it finds a fellow BSD nerd ;)

]]> Comment on Understanding PS3 NAT Types by acesass http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-49 acesass Sun, 05 Feb 2012 13:41:43 +0000 http://netnix.org/?p=40#comment-49 your ps3 needs a different ip from say your laptop or pc if it uses the same one will be moderate or strict.also you need to alter the dmz in your router to the ip your ps3 using to get nat type open. your ps3 needs a different ip from say your laptop or pc if it uses the same one will be moderate or strict.also you need to alter the dmz in your router to the ip your ps3 using to get nat type open.

]]> Comment on Understanding PS3 NAT Types by Kris Dodd http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-48 Kris Dodd Thu, 02 Feb 2012 19:35:28 +0000 http://netnix.org/?p=40#comment-48 Also, I have Nat type 2 but its still strict. Also, I have Nat type 2 but its still strict.

]]> Comment on Understanding PS3 NAT Types by Kris Dodd http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-47 Kris Dodd Thu, 02 Feb 2012 19:28:14 +0000 http://netnix.org/?p=40#comment-47 Okay, well my PS3, my tablet and my computer all connect to my modem, I'm not sure if this is the problem, but my NAT has always been open and then as soon as I got my internet back through a different company, it was strict, please explain. Okay, well my PS3, my tablet and my computer all connect to my modem, I’m not sure if this is the problem, but my NAT has always been open and then as soon as I got my internet back through a different company, it was strict, please explain.

]]> Comment on Understanding PS3 NAT Types by ro http://netnix.org/2011/09/06/understanding-ps3-nat/#comment-39 ro Fri, 13 Jan 2012 07:33:38 +0000 http://netnix.org/?p=40#comment-39 so i went an change the nat from strict or moderate yesterday an it wrked fine,nextday its back 2 moderate i my playstation broken so i went an change the nat from strict or moderate yesterday an it wrked fine,nextday its back 2 moderate i my playstation broken

]]>