How to bridge

It doesn’t matter if you have a 360 or not so listen up. You must have your computer close.  Next find out if you have a second Ethernet port on your computer that is empty. If not then buy one that can plug into the USB it worked for me. Next go to your control panel, Internet connections (network connections) then you should have a list of 3 sections the bottom section you should have 2 things (after you have put your Ethernet cord was taken out of your modem/router and put it in your second Ethernet port) Local area connection and local area connection 3. Highlight them both and right click it should say bridge connections and do that. Now here is the tricky part -  get a program called Zone Alarm. Now if you have Macafee, get rid of it; Zone alarm is the same thing, but it lets you bridge. Now you can use the trial the website gives you and that lasts a LONG time so get that. Use this to get it http://www.download.com/3000-2092-10061193.html. Ok you have all that.  Now you’re set, just a couple more things. Now go to the Firewall page off to the side and click on that. You should see 2 things -  Internet Zone Security and Trusted Security Zone, put those both on low. Now go to the tab at the to go to Zones. Now you should have 2 things -  new connection and loop back adapter. The new network is the Xbox. Now they probably both say trusted off to the side. For the new network click on trusted and put it on Internet. Go to the bottom and it should say add>>   click on that and go to IP address. It will ask for a description and an IP. You need all of Bungies IPs so put the ones in that are and the next page below this one that you are reading.   Now to bridge someone you add there IP address and put your Internet firewall on high. Have them make a party and they join them and they are bridged host.

the ips you need to bridge

Click on Ip Range for these :

System - 65.55.42.130 - 65.55.42.225

Epic -     206.13.213.20 - 206.13.213.225

Your loopback addapter has to be on trusted and your network bridge or xbox will need to be on internet.

Make sure the ips stay on trusted and never remove them. The idea of the ranges is to make sure that even when bungie changes there ip, it wont matter.

Can I bridge without 2 ports

movie on how to - http://youtube.com/watch?v=7AIWr9SSSwM 

2nd move - http://youtube.com/watch?v=QsGrJTEGYzA&mode=related&search=

( if none of the pics come up send me an aim to xavekiller or a freind request on xbl to xavekiller)

vOk this tutorial will teach you how to setup your bridge step by step. TuT** created by ArecBardwen and Bl0ckbust3d


Part 1: The Program

Cain and Abel~ a network hacking tool. Antivirus programs will delete it because it contains certain types of files. I assure you it is clean and will do no harm to your computer or network. Download:
Cain and Abel

---------------------------------------------------------------

Part 2: Setting up Cain and Abel

First of all start up your xbox and sign onto live.

Ok install Cain and Abel along with wincap. NOTE: wincap is neccesary for Cain to run. Now start Cain and your screen should look like this


Now click the sniffer button and then the sniffer tab

Now for instance my xbox is 192.168.0.105. whatever one yours is find out and then find out which connection is your internet connection. mine is 192.168.0.1 for example.Now click on the APR tab at the bottom left. your screen should look like this

Now to add to list, you have to click in the box then the plus sign.

Now you will be confronted with an option of IP addres's. First chose your xboxs then on the other side chose your internet IP.Then click the radiation sign next to the plus sign. it should say poisoning and IP's should show up on the bottom box.Those are the ips of the people you are playing with! Congratulations you've successfully found their IP's!

Now you can bridge whoever you want whenever you want!
 

wireless bridging

This howto is intended to help people who currently use a wireless router in their house, and also have additional PCs or devices without wifi cards which cannot be connected to the wireless router using a cable because they're too far from it (like in another room).

This howto will explain how to use the wrt54g a to connect these remote PCs to the internet and your home network, without using wifi cards. This is possible using 3rd party firmware (sveasoft) which allows the wrt54g to operate in "client" mode, where it forwards packets from its connected devices to the main wireless router, using a wireless link.

I got my wrt54g running in client mode - that is, it serves as a bridge between a PC attached to it and the main wireless router. Here's my complete setup, starting with the wired connections (markeded by "<===>"):

Room 1: Cable Modem <===> D-Link DI-624 Wireless Router <===> PC-1
Room 2: WRT54G <===> PC-2

The DI-624 and the WRT54G connect to each other wirelessly. I also have a mobile laptop which connects wirelessly to the DI-624.
So in this case, the WRT54G let me use PC-2 without having a wifi card in that PC. In fact, I could connect up to 4 PCs to the wrt54g, and save the price of 4 wifi-54g pci cards, plus I don't have to install drivers for wifi cards (a pain in Linux). The wrt54g acts like a "wireless ethernet bridge", which in fact is another product sold by linksys (WET54G) for around $150. This is also useful when you have devices (in a room which doesn't have ethernet connections) which can only connect using a ethernet cable, but cannot connect wirelessly - like XBOX !

So how do you do it ? Here's the list of steps - you should be doing these steps (except step 1) from a PC attached to the wrt54g (e.g. PC-2 in my setup). Physically attaching a PC to the wrt54g is required only for this initial set up phase, because we need to login and set up the various options. Note that this doesn't require any changes to your main router's configuration, so it's quite safe with regard to not messing up your current networks' setup.

1. Download the "wrt54g alchemy firmware" (google this, or go here) version 6rc5 from the internet (it is the only one compatible with the new models wrt54g V2.2 & wrt54gs V1.1).
2. Upload the firmware to the wrt54g via the "Administration->Firmware Upgrade" option in the router's web interface.
3. Reset the device (press reset button until power led flashes - this could take 20 seconds or more). In the following steps, leave all settings which are not mentioned in the description at their default (only change the ones specifically mentioned in the step).

Note: We will use addresses that end in 128-255 for the wrt54g router and it's attached PCs. To make sure there is no overlap in the addresses assigned by the two routers, we have to make sure that your main router only assign addresses below 128 to its own clients. For example, if your main router address is 192.168.0.1, its DHCP address range could be 192.168.0.50 - 192.168.0.120. Another important note regarding the main router: some routers allow you to disable the broadcast of the SSID, but for this setup to work properly the SSID broadcast MUST BE ENABLED (which is usually the default behavior).

4a. In "Setup::Basic setup" screen, set Internet Connection Type to "Auotomatic Configuration - DHCP".
4b. Set the local IP to 192.168.0.129, assuming your main router is 192.168.0.x (in general, if your main router is a.b.c.d set the wrt54g to a.b.c.129).
4c. Set the Subnet Mask to 255.255.255.128.
4d. Set the "Gateway" to the IP address of your main router (e.g. 192.168.0.1).
4e. Set the DHCP Server to Enabled, and starting IP Address to something above 129 (e.g. 140).
4f. Save the settings on this page. You should reboot the attached PC, since the subnet mask has changed. Note: from now on you have to use the new local IP you set in step 4b (e.g. http:// 192.168.0.129) to connect to the router from your PC.

5. In "Setup::Advanced Routing" screen, make sure operating mode is "Gateway".

6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client", wireless network mode to "mixed", and SSID to your main wireless router's SSID.

7. In "Wireless::Security" screen, set yor WEP/WPA settings which match the main wireless router. You should now be connected to the main wireless router. Note: if you have MAC filtering set up on the main router (which allows only specific clients to connect), then obviously you have to add the client router to the list of allowed clients.
To verify that you've established a connection to the main router, you can check the "Status::Router" screen, which should show an IP Address assigned by the main router (which would end with a number below 128), and the "Status::Wireless" page should show the AP Signal strength together with the mac address of the main router. Also you should now be able to ping the main router and even log in to it (using h ttp://192.168.0.1) from the PC attached to the client router (the wrt54g).

8. In "Security::Firewall" screen, disable firewall protection, as this subnet is already behind your main router's firewall. Also make sure that "Block Anonymous Internet Requests" is unchecked.

9. In "Administration::Management" screen, you can leave all settings at their default. You may want to enable remote management and Telnet or SSHD, especially if you want to be able to log in to the wrt54g from a computer which is not directly attached to it.

10. To enable PCs attached to the main router to be able connect to PCs attached to the wrt54g: Login into the wrt54g using telnel or ssh by running the command "telnet 192.168.0.129" and use same root/passwd as for the web interface. Then type this command (copy it exactly):

# echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp

Now you should be able to ping/telnet to any PC attached to the wrt54g from any PC attached to the main router. Btw, this assumes that the subnet mask of the main router is the default 255.255.255.0.

Important note about the last step : The last step (which is an optional step) allows PCs attached to the main router to be able to connect to PCs attached to the client router, by specyfing the IP of the destination PC, for example "telnet 192.168.0.150". But they are still on two different subnets which do not share their broadcast messages, therefore when browsing PCs on the local network you will not automatically see the PCs attached to the other router. But you can always connect to them by explicitly specyfing the IP. Btw, this step was added after the initial posting of this HOWTO and solves a lot of the issues people discussed later in this thread, so don't worry if you read posts in this thread about problems with communicating between PCs attached to different routers. Also note that this proxy_arp setting is not saved in the WRT54G non-volatile memory like all the other settings, so when the router is rebooted (like after a power outage), it will be cleared and you will need to repeat step 10 to set the proxy_arp back on.


Done !!! That's it !!!!