Topic: How To Block Xbox Live On Your Router (Read 367 times)

conneen · « **on:** January 01, 2004, 02:58:00 PM »

I want to take this a step further.

I want globally block 3074 UDP/TCP. Effectively disabling live.

Then I want to unblock it for 192.168.1.170.

If I manually configure the MSDash/Live to use 192.168.1.170.
And I manually configure my Evox Dash to use 192.168.1.175.

If I boot with the Modchip off. (ending up with *.170), then Live should work.

If I boot with the Modchip on. (ending up with *.175), then Live won't work.

Now my only question is, if I play a backup while the modchip is on, and try to access Live with it. Will it use the settings from Evox (175) or the settings from the MSDash (170)?

Conneen

...ReLLiK · « **Reply #1 on:** January 01, 2004, 03:28:00 PM »

QUOTE (jfullam @ Nov 17 2003, 06:49 AM)

I have currently blocked UDP/TCP 3074 on my router. If I have my mod chip on and "somebody" accidentally chooses an XBOX Live option on a game CD, do I still run the risk of having my Evox Dash replaced with M$? I am trying to think of a fool proof way to make sure my dash doesn't get trashed... I have my young son playing on the XBOX and it is possible he or one of his friends could inadvertedly click on a XBL option in a game when I have the mod chip on...

If u do in fact have an x2.2 pro like your tag says... just leave your original dash as xboxdash.xbe and name evox as evoxdash.xbe... your bios will try to boot from evoxdash.xbe first. Then any time Live! is chosen it can only modify xboxdash.xbe not your evox!

tranus69 · « **Reply #2 on:** March 28, 2004, 01:07:00 PM »

trejkaz · « **Reply #3 on:** April 21, 2004, 08:53:00 PM »

Probably not such a good idea to block port 88 globally, just in case you're one of those users whose mail server is elite enough to support Kerberos logins. Just a thought...

So give your Xbox an address, and then block exactly those three ports from exactly the one address.

The question I have on top of this is, what stops MS changing the port next month, and getting people banned all over the place?

(I'm actually tempted to block *everything* from the Xbox, and enable one service at a time where I need it, for things like live weather updates.)

frank10 · « **Reply #4 on:** May 17, 2004, 12:16:00 PM »

th3gh05t · « **Reply #5 on:** June 03, 2004, 09:35:00 AM »

Jully · « **Reply #6 on:** September 21, 2004, 06:34:00 AM »

johnblox · « **Reply #7 on:** September 27, 2004, 09:15:00 AM »

If xbox is behind NAT router it prevents INCOMING connections except on the few opened ports and then only to the IP specified in the route. BUT any pc/xbox can initiate comms OUT of any ports. Is this xblive secure or not?

Leafz · « **Reply #8 on:** November 10, 2004, 01:28:00 AM »

buy adding a passcode for security, would that help prevent on connection to live? or does it check after you connect?

gimpism · « **Reply #9 on:** November 13, 2004, 08:25:00 AM »

why not block any traffic to their servers? It basically comes down to determining if they have a set ip range or and point to a dns name/pool.

This post has been edited by gimpism: Nov 13 2004, 04:25 PM

Bizarro · « **Reply #10 on:** November 13, 2004, 09:47:00 AM »

i have (probably a stupid) question.
shanafan says to block ports
UDP 88
UDP 3074
TCP 3074

why shouldn't we also block
UDP 53

feflicker · « **Reply #11 on:** December 01, 2004, 02:43:00 PM »

Because UDP 53 is used for DNS, and you might want that for other things

Tittie · « **Reply #12 on:** December 07, 2004, 05:31:00 PM »

If I have 1 box with 2 hdds. One Softmod for FUN, the other retail for Live. I use static IP on both with different IP addresses. I would be safe just blocking the ports on the softmod IP right?

STICKY_BUD · « **Reply #13 on:** March 15, 2005, 02:20:00 PM »

QUOTE(conneen @ Jan 1 2004, 01:04 PM)

I want to take this a step further.

I want globally block 3074 UDP/TCP. Effectively disabling live.

Then I want to unblock it for 192.168.1.170.

If I manually configure the MSDash/Live to use 192.168.1.170.
And I manually configure my Evox Dash to use 192.168.1.175.

If I boot with the Modchip off. (ending up with *.170), then Live should work.

If I boot with the Modchip on. (ending up with *.175), then Live won't work.

Now my only question is, if I play a backup while the modchip is on, and try to access Live with it. Will it use the settings from Evox (175) or the settings from the MSDash (170)?

Conneen

since there has been no confirmation of this method in this thread, i decided to test it partially, but since i did not desire to force a hacked xbox to connect to xbl not thoroughly... unfortunately, i may have gotten banned(99% positive) in my testing method anyways, but i will not know that until tomorrow.

the only thing that did not work for me with conneen's theory was that after several reboot tests, the retail dash network settings would very often accept the the hacked dash ip address - not sure why...

the only way to keep my retail dash from assuming the same manual ip from the hacked dash, was to set the retail dash network settings to dhcp. after this, i could block xbl access for my manually configured hacked dash ip by adding an access restriction rule to my router which allows the hacked dash ip internet access, but blocks udp/tcp 3074 port access specifically.

EDIT - after re-reading this, i realize it is not clear how i tested it. to test whether xbl access was blocked to a specifc ip, i tried connecting to xbl through the retail dash which was manually configured with the ip i wanted to block. once i had it blocked, i tested for internet access by launching my hacked dash and making sure i could still download a skin with the same manually configured ip and the xbl blocking rule enabled.

i have tested it several times over the last hour with as many reboot combinations as i can think of and it is still working for me.

if i receive the ban message due to this testing i have done so far, i will have an *expiring in 3 weeks* flagged gt to do some more tests and i have been wondering about the validity of the flagged gt *extra testing* theories anyways. however, if i do those tests, i will write a new post for it.

This post has been edited by STICKY_BUD: Mar 15 2005, 10:32 PM

schnide · « **Reply #14 on:** March 26, 2005, 07:02:00 PM »

I thought I read somewhere on this forum that there was an edit to the EvoX config file to make sure that Live didn't connect? Or have I got this wrong?

I've just setup my entire network so that my XBox runs through my PC with internet connection sharing, and although I'm going to try to disconnect the network lead each time I'm not on Live without the chip, I'm worried I'll forget.

Any automatic solution to allow only Live with the chip off and allow everything except Live with the chip on would be a complete blessing!

Keep up the good work guys, I'll wait patiently for the perfect fix..

Author Topic: How To Block Xbox Live On Your Router (Read 367 times)