Linksys WAP54G User Manual. 2.4 ghz wireless-g access point. Also See for WAP54G. “Configuring the Linksys Wireless Guard Settings.”. Page 28: Figure 5-24: Confirm New Settings Screen. Wireless-G Access Point 5. The Setup Wizard will ask you to review your settings before it saves them. Click the Yes button if you are.
Alright here you go - a step by step guide to setting up a linksys in client or bridge mode for whatever purposes. Some use it to hook up an XBOX or other game consoles with the network, or a media center pc, etc. I was going to paste this in response to another topic, but it was closed by someone. Assumptions: 1.
ROUTER refers to a linksys with stock/original firmware. Any other should work as well. ROUTER internal ip = 192.168.1.1 3. ROUTER subnet mask = 255.255.255.0 4. ROUTER DNS Server 1 = aaa.bbb.ccc.ddd (replace by actual ip) 5.
ROUTER DNS Server 2 = aaa.bbb.ccc.eee (replace by actual ip) 6. ROUTER has wireless enabled with SSID = SUBSTITUTEYOURROUTERSSID 7. ROUTER as security enabled using 64 bit WEP encryption with key = SUBSTITUTEYOURROUTERWEPKEY 8. CLIENT refers to a linksys with latest satori or alchemy firmware. Please subscribe to sveasoft and get the latest firmware, it's worth the small subscription amount. Satori works as well but you can only hook up a single device to the CLIENT.
I am morally against placing support discussions contributed by public behind closed doors (hence posting this here instead of closed sveasoft forums) but I still paid for my software, because I think the bits are worth the money. X Y = Click on first level menu on the top labelled X and then click on submenu or tab labelled Y 10. A.B = Value of a field labelled B in the section labelled A on a page.
Section names appear vertically on the left of the page with black background. Preperation: 1. Validate or obtain the above information about the ROUTER. As long as you have access to it one way or another it shouldn't be an issue, e.g. On windows, you can run a ipconfig /all command in the command prompt to obtain the info above.
Whatever the values, please use those values instead of the above. Also figure out an ip address on the ROUTER that is outside the dynamic ip address assignment range.
Most routers come pre-configured with dynamic ip assignments starting from.100 or.50 onwards. So a low ip like 192.168.1.2 should work in our scenario. This will be used to assign the ROUTER facing ip to the CLIENT later on. These steps assume that you are starting with a clean slate. So if you have messed around with the settings, undo it by restoring the defaults.
Any settings not outlined in the steps are to remain at the default values! CLIENT setup step 1: 1. Select Wireless Basic Settings tab 2. Set Wireless Network.Wireless Mode = Client 3.
Set Wireless Network.Wireless Network Mode = Mixed (or if all your cards and ROUTER support G, then set it to G-Only) 4. Set Wireless Network.Wireless Network Name (SSID) = SUBSTITUTEYOURROUTERSSID 5. Click Save Setting button CLIENT setup step 2: The settings in this tab will vary depending on what security settings are configured on the ROUTER.
Basically it is the same as you enter when connecting a laptop or any other wireless device with the ROUTER. I will use the example of WEP based encryption with a 64 bit hex key. If your ROUTER doesn't have any security settings, then this step can be skipped.
Select Wireless Security tab 2. Set Wireless Security.Security Mode = WEP 3.
Set Wireless Security.Default Transmit Key = 1 (or which ever your ROUTER is configured to use) 4. Set Wireless Security.WEP Encryption = 64 bits 10 hex digits 5. Set Wireless Security.Passphrase = Leave blank if you manually entered your key when setting up router otherwise enter the passphrase and click generate 6. Set Wireless Security.Key 1 = SUBSTITUTEYOURROUTERWEPKEY assuming you didnt enter a passphrase and hit generate in the previous step 7. Repeat #6 for the rest of the keys to set them to what ever was configured on the ROUTER.
Click Save Setting button CLIENT setup step 3: 1. Select Setup Basic Setup tab 2.
Set Wireless Setup.Internet Connection Type = Static IP 3. Set Wireless Setup.Internet IP Address = 192.168.1.2 (or whatever ip address you identified in step 2 of preperation) 4. Set Wireless Setup.Subnet Mask = 255.255.255.0 (same as assumption #3) 5.
Set Wireless Setup.Gateway = 192.168.1.1 (Same as assumption #2) 6. Set Wireless Setup.Static DNS 1 = 192.168.1.1 (Same as assumption #2) 7. Set Wireless Setup.Static DNS 2 = aaa.bbb.ccc.ddd (Same as assumption #4) 8.
Set Wireless Setup.Static DNS 3 = aaa.bbb.ccc.eee (Same as assumption #5) 9. Set Wireless Setup.Router Name = BRIDGE (doesn't matter what you name it) 10. Set Wireless Setup.Host Name = BRIDGE (doesn't matter what you name it) 11. Set Wireless Setup.Domain Name = Blank (unless you have a reason to enter it) 12.
Set Wireless Setup.MTU = Auto 13. Set Network Setup.Local IP Address = 192.168.2.2 (increment the 3rd octet of the Wireless Setup.Internet IP Address field by 1, e.g 192.168.1+1.2. So now 192.168.1.2 is your ROUTER facing IP and 192.168.2.2 is your CLIENT network facing IP.
Set Network Setup.Subnet Mask = 255.255.255.0 (Same as assumption #3) 15. Set Network Setup.Gateway = 192.168.2.2 (Same as #13 above) 16.
Set Network Setup.Local DNS = 192.168.1.1 (Same as #6 above) 17. Set Network Setup.DHCP Server = Enabled (To let the CLIENT issue dynamic IPs to the devices hooked up to it) 18. Set Network Setup.Starting IP Address = 192.168.2.100 (You may have to click on Save Settings button before you see 192.168.2 written in this field. If you do, make sure you connect back to the CLIENT using the ip address is #13 above) 19. Set Network Setup.WINS = 0.0.0.0 20.
Click on Save Settings button. Notice that after this configuration, your CLIENT bridge/router has a different IP address for administration. So if you are not automatically redirected to the new IP, you may have to connect to the administration web page by typing 192.168.2.2 yourself. Also note that at this stage, you may not be able to connect to the new IP unless you are using a computer hooked up to one of the LAN ports of the CLIENT itself.
And you may need to temporarily setup your computer's TCP/IP config to use a static IP in the 192.168.2. subnet.
CLIENT setup step 4: These steps are temporary so that you don't run into any issues during setup. Once you have everything working, you can undo these settings one by one as long as your setup keeps working. Theoratically speaking, you shouldn't need to because your internal network is protected by the firewall of your ROUTER from the internet anyway.
But if you are security conscious then you may want to undo these. Select Security Firewall 2. Set Firewall.Firewall Protection = Disabled 3. Set Firewall.Block Anonymous Internet Requests = unchecked 4.
Click Save Settings button At this point, you should be able to Click on Status Wireless tab and see that you are connected to the ROUTER. You should also be able to hook up a device or computer to one of the four LAN ports of the CLIENT and notice that it obtains a dynamic IP like 192.168.2.100 or some number greater than 100. You should also be able to ping your ROUTER, i.e. Ping 192.168.1.1. You should also be able to ping the internet, e.g. If you are not successful, then complete the next steps and retry after restarting the device/computer connected to the CLIENT. You may want to reboot the CLIENT as well.
ROUTER setup step 1: If you are not able to ping the ROUTER from a computer connected to the CLIENT, then you may have MAC address filtering enabled on the ROUTER and your security settings may be incorrect. For the former problem, make sure that you add the MAC address of the CLIENT as well as the MAC address of the computer connected to the CLIENT to the MAC filter list.
In fact, the best thing to do right now is to temporarily turn off MAC address filtering. Also, at this stage since the CLIENT and all devices/computers hooked up to it are on the 192.168.2. subnet while your ROUTER is on the 192.168.1. subnet, you will most likely not be able to ping the CLIENT or any computer connected to the CLIENT. In order to fix that, you need to setup a static route to the 192.168.2. network so your ROUTER knows how to forward traffic to that network. Connect to the ROUTER's admin app, 192.168.1.1 typically 2.
Select Setup Advanced Routing 3. Set Advanced Routing.Operating Mode = Gateway 4. Set Advanced Routing.Select Set Number = 1 5.
Set Advanced Routing.Enter Route Name = BRIDGE (or any name you fancy) 6. Set Advanced Routing.Destination LAN IP = 192.168.2.0 (the last octet must be 0 and the third octet must be the same as your CLIENT's local IP's third octet) 7. Set Advanced Routing.Subnet Mask = 255.255.255.0 8. Set Advanced Routing.Default Gateway = 192.168.1.2 (same as your CLIENT's ROUTER facing IP, i.e. Client setup Step 3, #3 above) 9. Set Advanced Routing.Interface = LAN & WIRELESS 10. Click Save Settings button 11.
Click on Show Routig Table button and it should look something like: Destination LAN IP, Subnet Mask, Gateway, Interface YOUREXTIP, 255.255.255.255, 0.0.0.0, WAN (Internet) 192.168.2.0, 255.255.255.0, 192.168.1.2, LAN & Wireless 192.168.1.0, 255.255.255.0, 0.0.0.0, LAN & Wireless 0.0.0.0, 0.0.0.0, YOUREXTIP, WAN (Internet) That is it! If you have followed the steps correctly and made sensible substitutions for your specific environment, everything should work flawlessly. If you run into any issues, double check your settings adn run through the steps again. Make sure you are starting from a clean slate configuration on the CLIENT. Hope this helps.
Admins, you may want to make this a sticky topic. Click to expand.Yes, you are right. If you choose to put the CLIENT and the CLIENT attached devices on a seprate subnet, which is my preferred configuration (primarily security reasons for me), you will have to configure your CLIENT while connected to a computer on the same subnet. It's a temporary setup-time thingy though, once the route to the subnet is configured, you should be able to access both the CLIENT and the XBOX attached to it.
You can try to setup the CLIENT on the 192.168.1. subnet, but I am not sure if it will work. Click to expand.You shouldn't need this one as long as the first route above is setup right. But if it doesn't work then do the same thing here, that is use the LAN IP instead of the laptop IP. So replace 192.168.0.3 with 192.168.0.0 Also, before testing file sharing, try to just ping the pc from the laptop and vice versa. Also, make sure that the firewalls on the routers or any of the software firewalls on your pc are not the culprits. Try that before configuring the second route on the linksys.
As I said, it may not be needed. Hope that helps. Click to expand.carrere206: You don't need static IPs from your ISP for the guide, not sure what led you to believe that.
All 192.168. IPs discussed are internal non-routable on the internet IP addresses.
The external IP can be dynamic and your ROUTER set in the gateway mode manages it automatically for you. Re: Step by step guide to setup a WRT54G in client bridge mo Shah- Thanks so much for your reply. Your guide was the only one that I could find that listed step-by-step the setting needed for connecting 2 routers. So I really appreciate your spending the time to write it and answer questions. The symptoms of my problem are that with my current config of the router/client I have to regularly (about 1/day) either restart the client machine or release then renew the DHCP lease in order for the connection to work. This caused me to believe that the DHCP lease had run out or had been changed by Comcast on a regular basis and subsequently drop the client's connection. Another of the reasons that I zeroed in on the static IP issue as a possible problem was that your guide listed needing the DNS server IPs as some of the assumptions.
Comcast doesn't supply the static DNS addresses. So I plugged in the DNS addresses that I could resolve with a network utility however I believe that they change regularly. Also after implementing the steps you outlined, I was unable to get the client to connect to the network until I changed the Network connection setting on the client machine to 'DHCP with Manual address' and then set the machine's IP to 192.168.1.20.
Before implementing this 'fix' the client machine would pull an IP with a 192.168.2.X address and I couldn't connect nor reach the reconfig screen of the client router. If it would help I can post the setting for each of the routers, so if you need that info I will post it.
Thanks again, Carrera206. Carrere206: You don't need static IPs from your ISP for the guide, not sure what led you to believe that. All 192.168. IPs discussed are internal non-routable on the internet IP addresses. The external IP can be dynamic and your ROUTER set in the gateway mode manages it automatically for you. Re: Step by step guide to setup a WRT54G in client bridge mo The symptoms of my problem are that with my current config of the router/client I have to regularly (about 1/day) either restart the client machine or release then renew the DHCP lease in order for the connection to work.
This caused me to believe that the DHCP lease had run out or had been changed by Comcast on a regular basis and subsequently drop the client's connection. Well, the ip address of the CLIENT is assigned by the dhcp server in the ROUTER and has nothing to do with the Comcast assigned IP addresses for your ROUTER'S external (WAN) interface. So this is an issue with the dhcp config of your ROUTER. Make sure it is configured to lease out an IP for a long period of time. If that is already the case, then you may have a conflict on the network where multiple devices are assigned the same IP. Make them all dynamically assigned and ensure that all devices on teh same subnet are configured to receive the IP from one and only one DHCP server. Another of the reasons that I zeroed in on the static IP issue as a possible problem was that your guide listed needing the DNS server IPs as some of the assumptions.
Comcast doesn't supply the static DNS addresses. So I plugged in the DNS addresses that I could resolve with a network utility however I believe that they change regularly.
This is another non-issue. You should be able to get the list of DNS servers by typicing ipconfig /all in the command prompt.
The DNS servers typically don't change. But you can almost always get away with assigning the IP address of yoru ROUTER'S internal interface as the DNS server on the CLIENT and CLIENT attached devices. I have that in my instructions. DNS server IPs are a nice to have in most cases. Also after implementing the steps you outlined, I was unable to get the client to connect to the network until I changed the Network connection setting on the client machine to 'DHCP with Manual address' and then set the machine's IP to 192.168.1.20.
This may be the cause of a potential conflict on the network. You shouldn't do that. Before implementing this 'fix' the client machine would pull an IP with a 192.168.2.X address and I couldn't connect nor reach the reconfig screen of the client router. The 192.168.2.X IP is correct, you just need to configure the static route from the.1 net tot eh.2 net as per my instructions.
I have a feeling you didn't follow the instructions down to every detail/step. Please recheck and you shouldn't have any issues. If it would help I can post the setting for each of the routers, so if you need that info I will post it. If the above doesn't help, then do so. But hopefully you won't need that. Hi, here is my config: Ethernet modem - Netgear wifi router - Linksys WRT54GS - Desktop (running Linux) It seems that Encryption causes a problem to me.
I tried either WEP or WPA-PSK, and it doesn't work. Without any security, it works fine. Any clue of what the problem is? Slee: If everything is working without the encryption then following are the only things I can ask you to check or re-check: - You are using the same encruption method on both the ROUTER and the CLIENT - You are using the same length key on both ROUTER and the CLIENT - The key values are the same and don't use the passphrase feature, just type in the same value for all four keys, e.g.
If you are using WEP - Check the Status.Wireless.Encruption Function value and make sure it is enabled. Enable logging Administration.Log and see if it reports anything of use Hope some of it helps. Regardless, if you resolve the issue please post back what the problem was so I can improve the guide. Cannot reach CLIENT from ROUTER Thanks Shah that was an excellent guide however I still have a few unresolved issues. I have a Netgear WGR614 router and Linksys WRT54GS client. I have internet access from the client attached pc (CAP) but cannot ping any router attached device (RAP). A CAP can ping the CLIENT at both subnet address and the ROUTER successfully (obviously as its getting an internet connection) but a CAP cannot ping a RAP.
Additionally a RAP cannot ping the CLIENT at either address or any CAP. I have set up a static route on the router to 1 of my CAPs of which I know the address as follows: Destination IP Address: 192.168.2.100 IP Subnet Mask: 255.255.255.0 Gateway IP Address: 192.168.1.2 Metric: 2 MAC filtering is OFF on both CLIENT and ROUTER Any suggestions as to what might be the problem? Playing network games with this set up Hi Shah, Is it possible to have two Xbox's play system link games using client mode?
Xbox1 - Router Bridge - Xbox2 The main problem I see is that they will both be on different subnets so that any broadcast messages sent out by the hosting Xbox will not reach the other. I have looked a lot in to this and no-one seems to be able to provide a concrete answer except to say that it works in WDS mode. That would require buying a new primary router which supports WDS and putting up with lower overall throughput. I've since read that when a game runs the xbox's no longer uses the dash set IP addresses. I can confirm this because when I unplugged an xbox set up on the bridge with a static ip and plugged it back in to the router whilst the game was still running it had no problem finding the hosted game on the same subnet. If there is no way of knowing what the ip addresses of the attached xbox's are when playing a game then what can we do to force them to talk to each other? Is there a different set up that would work for this?
I've followed your directions and this is my current status: I have attached one computer to the CLIENT with an ethernet cable and everything works beautifully. IP address on the computer is 192.168.2.100. I have another computer that connects to my network wirelessly. It only connects to my ROUTER with an ip address of 192.168.1.100. This is obviously not what I want.
I want it to connect to the CLIENT, with an IP address of 192.168.2.101 for example. So to summarize, my CLIENT connects to my main network, but it doesn't seem like the 'range expanding' is working. Any thoughts?.Edit - Only read the first page and didn't see the comment about only wireless clients. So my next quesiton is, can I do something to also set up wireless clients?
I've since read that when a game runs the xbox's no longer uses the dash set IP addresses. I can confirm this because when I unplugged an xbox set up on the bridge with a static ip and plugged it back in to the router whilst the game was still running it had no problem finding the hosted game on the same subnet. If there is no way of knowing what the ip addresses of the attached xbox's are when playing a game then what can we do to force them to talk to each other?
Is there a different set up that would work for this? Click to expand.As long as you have configred static routes, devices on the two subnets should be able to communicate with each other ASSUMING they know the other's IP. The issue in your case seems to be the auto-discovery of the IPs or even the devices on the two different subnets. Well, I don't know much about XBOX and how they are configured to communicate but they have to be using IP broadcasts to ask others on the network for identification. Which means, if you can forward the broadcast messages between the subnets, you should be set. Here is where it would help to know how XBOX's exactly broadcast. I can only see one of two mechanisms (you can use a sniffer to validate).
A limited broadcast to IP 255.255.255.255 which is only meant for devices attached to the CLIENT network. Routers are typically designed to ignore forwarding of limited broadcasts and you may be out of luck. A subnet broadcast to IP 192.168.2.255 which you can TRY to forward to your 192.168.1.0 network (ROUTER's) by setting up a static route for it. You may have to setup the subnet mask for the route as 255.255.255.255 instead of 255.255.255.0.
If this doesn't work, WDS may be your only option or you can try to setup bridge mode on the same subnet with very careful IP address assignments. Let us know what worked for you. Thanks for the guide shah! I have it working sweetly here between a WAG54G v2 and a WRT54GS v1.1(client mode - Alchemy-V1.0) thanks to it!! Only thing i didn't use from your guide is I set static ip's once i had it working as per your instructions and turned off dhcp all together on both routers.
I also put the client routers ip address in the main routers DMZ and left the firewall on on the client router and block anonymous requests CHECKED, I figure the main router is protecting it's self and the client is protecting it's self this way?? I have one lil question for you tho is there anyway to get file sharing working wif pc's connected either side of the routers??
Or does the different subnet kill it?? PC1 - Main Router Client Router - PC2 Thanks again for the guide! Click to expand.I'm trying to do exactly what you are, I have two xboxes, one on the 192.168.1.0 network and the other on the 2.0 network bridged between two wrt54gs running alchemy and I can't get them to see eachother in system link mode. Can you tell me specifically what routes you had to add to get this to work? One other problem I'm having is that I cannot administer the CLIENT device when connected to the 192.168.1.0 network.
Funny thing is I can administer the ROUTER when I'm connected wirelessly thru the CLIENT on the 2.0 network. This makes it very difficult to change settings. Anyone have an idea how to fix this?
Here's my network setup: DSL Router Linux Box NIC1 - real world IP NIC2 - 192.168.1.1 (IP Masq/NAT box) (ROUTER) Internet Setup: Disabled - XBOX 1 (192.168.1.110) Router IP: 192.168.1.2 / / WRT65g (CLIENT) Internet Setup: 192.168.1.3 - XBOX 2 (192.168.2.100) Router IP: 192.168.2.3 From the 1.0 network I can ping devices on the 2.0 network, but cannot access the CLIENT's web admin. Devices on the 2.0 network can surf the web, and connect to all devices on the 1.0 network, access the ROUTER's web admin, etc.
Xboxes do not see eachother in system link mode. I have set the basic static routes per the instructions above, but I may have botched something Any help would be appreciated!!! Click to expand.Hrm, I just looked at the routing table on my CLIENT, and it looks messed up: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0. 255.255.255.0 U 0 0 0 br0 192.168.1.0. 255.255.255.0 U 0 0 0 eth1 127.0.0.0. 255.0.0.0 U 0 0 0 lo default 192.168.1.2 0.0.0.0 UG 0 0 0 eth1 default 192.168.2.3 0.0.0.0 UG 0 0 0 br0 This does not seem to correspond to the static route I set on my CLIENT thru the web interface which is dest: 192.168.1.0 mask 255.255.255.0 gw 192.168.1.2 (my ROUTER's wireless IP) Any ideas?
Working almost perfectly Hello I set up a network in my place, using the method you describe and it works almost perfectly. My main router has the address 192.168.1.1 My PC connected to it (wired) has the 192.168.1.102 (static to allow port enabling for the p2p) Then I set up a secong as a wireless bridge, with the IP address 192.168.2.2.
To this client I have a streamium box from PHILIPS, and XBOX and a PC. (all the the subnet 192.168.2.x) I can ping the different devices, from the PCclient or from the main PC (connected to the router), but I have an issue to have my streamium box (192.168.2.101) finding the upnp server running on the main PC. However this box (streamium) can connect perfectly on the internet. I have disable all the firewall (on the 2 ), but also on the PC. I have also enable the upnp function on the 2 (just in case.).
Just for the info, when the streamium is connected wired to the main PC it finds right away the upnp server. Any idea would be a great help. Thanks in advance Olivier. Discovering ROUTER attached devices using subnet broadcasts Alright, I am going to go all stingy on bandwidth and try to post a stock answer to most of the recent posts that have the same issues in common, i.e. Unable to discover ROUTER attached devices that rely on IP broadcasts for the discovery mechanism from the CLIENT attached devices. I had recommended the following to another poster who reported that it worked like a charm. You can see the full post on page 2 of this thread: A subnet broadcast to IP 192.168.2.255 which you can TRY to forward to your 192.168.1.0 network (ROUTER's) by setting up a static route for it.
You may have to setup the subnet mask for the route as 255.255.255.255 instead of 255.255.255.0 Please setup this additional static router from the CLIENT to the ROUTER and most of your problems will go away. Hope this helps SHAH. Hello I set up a network in my place, using the method you describe and it works almost perfectly. My main router has the address 192.168.1.1 My PC connected to it (wired) has the 192.168.1.102 (static to allow port enabling for the p2p) Then I set up a secong as a wireless bridge, with the IP address 192.168.2.2. To this client I have a streamium box from PHILIPS, and XBOX and a PC. (all the the subnet 192.168.2.x) I can ping the different devices, from the PCclient or from the main PC (connected to the router), but I have an issue to have my streamium box (192.168.2.101) finding the upnp server running on the main PC.
However this box (streamium) can connect perfectly on the internet. I have disable all the firewall (on the 2 ), but also on the PC. I have also enable the upnp function on the 2 (just in case.). Just for the info, when the streamium is connected wired to the main PC it finds right away the upnp server. Any idea would be a great help. Thanks in advance Olivier. Click to expand.Olivier, Please read page 2 of my thread where I posted the solution for what could possibly be the problem you are having also, that is, the subnet broadcasts don't have a static router defined from the CLIENT to the ROUTER which is typically used for discovery based services.
Specifically, UPnP (last I heard it was a bad bad thing from a security point of view) is based on SSDP protocol that heavily relies on multicast messaging for discovering devices, so there is a good chance that this will solve your issue. When announcing itself to the UPnp server, the streamium is quite possily issuing a subnet broadcast to IP 192.168.2.255 which you can forward to your 192.168.1.0 network (ROUTER's) by setting up a static route for it. You may have to setup the subnet mask for the route as 255.255.255.255 instead of 255.255.255.0 lio256 tried this suggestion and according to him, it worked like a charm. Hope that solves your problem also. If it does, please do let us all know. Further explanations Shah Can I take 5 minutes more of your time in order to ask you further explanation on how to set this. When announcing itself to the UPnp server, the streamium is quite possily issuing a subnet broadcast to IP 192.168.2.255 which you can forward to your 192.168.1.0 network (ROUTER's) by setting up a static route for it how to set up this route?
Do i need to do that on the router or on the client? I fully understand that I need to go and the advanced routing in the basic set up, but what are the parameters I need to enter exaclty (IP destination, Sub mask, Gateway IP) (just for reminder, my router is 192.168.1.1, my client is 192.168.2.2, my main PC with uPnp running is 192.168.1.102 and my streamium is 192.168.2.101) On the streamium box. Can I keep the 192.168.2.101 static IP.
Do I need to put the subnet mask to 255.255.255.255? Thanks again for your explanation. I've got the feeling I am close to solve this issue, but I still need a little push. Thanks Olivier. I would just like to clarify something. I presume this setup will also work where the internet ip address is not a LAN address but a real internet address.
My isp is a wireless AP on which I will use a static internet ip address. So my routing table ends up like this: 192.168.1.0 255.255.255.0 0.0.0.0 LAN & Wireless 10.22.3.0 255.255.255.0 0.0.0.0 WAN (Internet) 0.0.0.0 0.0.0.0 10.27.3.254 WAN (Internet) My LAN is of course the 192.168.1. and the AP point which is my gateway is 10.22.3.254. My internet ip address will be in the 10.22.3. block.
Does this seem right? Thanks in advance.
Will this setup work with Talisman? First of all, SHAH, excellent guide! It has been very helpful. I have tried to implement your system using Talisman firmware without success. I am able to ping the MAIN from the CLIENT without difficulty. I essentially have the following problem: (1) I have a Dell multifunction laser PRINTER in Room 1 hooked up to a CLIENT v3.0 running Talisman 1.0.3.1 (2) I have internet access through a cable modem via another computer hooked up to the main ROUTER v3.0 running Talisman 1.0.3.1. (3) I would like to print wirelessly (my printer would be given an IP address from the CLIENT DHCP).
The printer cannot be moved (for family reasons). (4) I would like to surf the net wirelessly using my laptop with built-in 802.11g A few questions: 1.
Can your setup work with Talisman? Do I need to choose client-bridged or client-routed to get this to work? Under advanced routing in Talisman there are checkboxes for WAN and LAN&Wireless and also checkboxes for RIP, etc. can I leave these all unchecked and simply enter the data you suggested? Thanks in advance for your advice.
Hello I set up a network in my place, using the method you describe and it works almost perfectly. My main router has the address 192.168.1.1 My PC connected to it (wired) has the 192.168.1.102 (static to allow port enabling for the p2p) Then I set up a secong as a wireless bridge, with the IP address 192.168.2.2. To this client I have a streamium box from PHILIPS, and XBOX and a PC. (all the the subnet 192.168.2.x) I can ping the different devices, from the PCclient or from the main PC (connected to the router), but I have an issue to have my streamium box (192.168.2.101) finding the upnp server running on the main PC.
However this box (streamium) can connect perfectly on the internet. I have disable all the firewall (on the 2 ), but also on the PC. I have also enable the upnp function on the 2 (just in case.). Just for the info, when the streamium is connected wired to the main PC it finds right away the upnp server. Any idea would be a great help. Thanks in advance Olivier. Click to expand.Olivier, Please read page 2 of my thread where I posted the solution for what could possibly be the problem you are having also, that is, the subnet broadcasts don't have a static router defined from the CLIENT to the ROUTER which is typically used for discovery based services.
Specifically, UPnP (last I heard it was a bad bad thing from a security point of view) is based on SSDP protocol that heavily relies on multicast messaging for discovering devices, so there is a good chance that this will solve your issue. When announcing itself to the UPnp server, the streamium is quite possily issuing a subnet broadcast to IP 192.168.2.255 which you can forward to your 192.168.1.0 network (ROUTER's) by setting up a static route for it. You may have to setup the subnet mask for the route as 255.255.255.255 instead of 255.255.255.0 lio256 tried this suggestion and according to him, it worked like a charm. Hope that solves your problem also. If it does, please do let us all know.
Click to expand.Shah, Your tutorial is excellent. It's the reason that I just went out and bought a second to set up in client mode so that I could connect my TiVo to the rest of my network. The big plus of this method for me was the ability to use WPA security (anything less is unacceptable, and I could find NO OTHER bridges that support it). So, I've got it all working thanks to your post and others comments. It all seems to be working great, I can ping everything from everything. My TiVo has internet access (it's connected to the BRIDGE ). There is just one problem left, and I think it's related to the last several posts in this thread.
Here's the problem. I'm running the TiVo software on my PC, connected to the ROUTER. The TiVo is on the BRIDGE and the two don't see each other. There is TiVo software used to copy files from the TiVo to the computer, but it does not allow you to enter the TiVo IP address, it must be able to 'auto detect' it on the network. I suspect that they are using broadcasts to know they're there, and these are not traveling across the bridge. You've posted that adding a static route to the ROUTER will possibly fix this, to forward the broadcasts to the CLIENT and vice versa.
I've tried it in every possible configuration I can imagine to no avail. In your post above you mention that 192.168.2.255 should be forwarded to 192.168.1.1, with subnet mask of 255.255.255.255. Well, when I try that, it gives me an error as I enter the 192.168.2.255 in the 'Destination LAN IP' field, that 255 is out of range. So, I CANNOT forward x.x.x.255, because the 255 is not allowed in the field.
I tried forwarding 192.168.2.0 with subnet masks of both 255.255.255.0 and 255.255.255.255 with no luck. I've tried every combination I can imagine of forwarding from the ROUTER to the CLIENT and back again, I can't get it to work.
I'd really appreciate any more specific guidance from those that have been successful in this setup. By 'more specific' I guess I mean, could you please list exactly the addresses placed in the 'Destination LAN IP', 'Subnet Mask' and 'Default Gateway' fields in the advanced routing tab.
I appreciate everyone's time posting on this forum, it's an incredible resource. Thanks in advance for any additional help with this! Click to expand.Mike, I'll chime in here again I managed to get my FTP client working to get to my xbox via the WPA wireless routed-client method I described above. In order to 'see' the FTP again, I had to set up the port forwarding. As everything is behind the firewall, I turned off the firewall (as SHAH describes in his first post), then I set up port 21 to go to the internal ip (of the bridge) of 21 for my xbox, then I setup port 80 to go to port 80 of the internal ip (of the bridge) of the xbox. I setup the forwarding of ports 21 and 80 to go to 192.168.2.200 (the ip addresses that I assigned to my xbox from the bridge). Then I can FTP to the internal ip I've assigned to my xbox (from the router e.g.1.200) which then forwards my requests to.2.200 I don't know if this answers your question or not, but hopefully it'll give you a start on getting it setup.
Oh yes, one more thing. I was able to ping the.1.200 ip of the xbox before I set up port forwarding (this is what was confusing me.if I can ping it, why can't I FTP or get to it).
I guess it wasn't forwarding my requests to the correct place, but now they are. Re: Working almost perfectly Lampei, Thanks for the post. Let me describe my network in a little more detail (although it's very similar to what has been described). ROUTER is connected to internet through WAN port LAN side address of ROUTER is 192.168.1.1 Have computer wired to ROUTER with address of 192.168.1.5 (static). This is the computer running the TiVo software CLIENT running Alchemy 1.0 has a ROUTER side ip of 192.168.1.2 CLIENT has a lan side ip of 192.168.2.1 TiVo is wired to CLIENT lan port with static ip of 192.168.1.5.
I have a static route set up on the ROUTER with destination 192.168.2.0, subnet 255.255.255.0, gateway 192.168.1.2 With this configuration, I can ping the tivo from the ROUTER connected computer. I can also access the web page on the TiVo. From the TiVo I can hard code in the ip address of the computer running the TiVo server to access music and picture files. This also works great (because I can enter the 192.168.1.5 ip of the computer directly).
The TiVo also is able to access the internet with no problems (for the tvguide listing updates etc). So it seems that everything is working great. Oh, I've got all the firewall stuff turned off on the CLIENT.
But, the problem is that the TiVo software running on my computer (192.168.1.5) provides the additional feature of being able to download tv programs from the tivo to the computer. But in this software you cannot just specify the ip of the tivo, it has to 'find' it on the network. The TiVo support website says that they have to be on the same subnet, but I'm guessing that this is because it uses a subnet broadcast to find the tivo. ZoneAlarm reports that the tivo software is trying to access 192.168.1.255:2190, which I believe is the broadcast (of course I turn off zonealarm while troubleshooting just to make sure it's not the problem).
Others (specifically lio256 and shah) have reported that a static route forwarding 192.168.1.255 on the ROUTER to 192.168.1.2 (the ROUTER side CLIENT ip), would forward these broadcasts. But when I try and put this in, it does not let me use.255, but gives an error that this is out of range and only.0.254 are allowed. I have (as per your suggestion Lampei) added port forwarding on the CLIENT to forward ports 2190 (and 8080-8089 as per directions on the TiVo site) directly to 192.168.2.5 which is my TiVo ip address. This doesn't help. What I have tried is to set up a static route on the CLIENT with destination 192.168.2.0, subnet 255.255.255.0 (also tried 255.255.255.255), gateway 192.168.1.1.
I've also gone backwards, forwarding from the ROUTER to the CLIENT in the same way. This also doesn't help. Anyways, that's my problem (sorry for the long post). It seems that if I could forward x.x.x.255 that would do it, but the router will not let me put in an address of.255. Any suggestions would be very welcomed! It seems that there are people who have gotten this to work, I just can't seem to quite get it right.
Perhaps others are using Talisman instead of Alchemy? Any thoughts??? Thanks, Mike (Spankster). Is it possible to choose between 'client-routed' mode and 'client-bridged' mode on DD-WRT prefinal 4 firmware? I'm having trouble setting it up with WPA. WEP works fine. Btw, my ROUTER is a DI-624, (it's routing tables cannot be changed) so the PC + Xbox behind the CLIENT cannot be seen.
Anyway, my top priority is to get WPA working with this setup. This is what it looks like: Router - DI-624, subnet 255.255.255.0 WAN Side-public IP LAN Side-192.168.0.1 - connected to PC1(192.168.0.100) Client - 1.1 on DD-WRT Firmware, subnet 255.255.255.128 'WAN' Side-192.168.0.102 LAN Side-192.168.0.129 - connected to Xbox(0.130), PC2(0.131). My router (ver 2.2, fw linksys 3.03.9) settings: Basic setup - Local IP = 192.168.1.1 Mask = 255.255.255.0 DHCP = Disable Advanced Routing: - Operating Mode = Gateway Set Number = 1 Route Name = BRIDGE Destination LAN = IP 192.168.2.0 Mask = 255.255.255.0 Default Gateway = 192.168.1.2 Interface = LAN & WIRELESS Show Routig Table: - Destination LAN IP, Subnet Mask, Gateway, Interface Internet Def Gw IP 255.255.255.255 0.0.0.0 WAN (Internet) 192.168.1.0 255.255.255.0 0.0.0.0 LAN & Wireless 0.0.0.0 0.0.0.0 Int. Def gw Ip WAN (Internet) There isn't this line: 192.168.2.0, 255.255.255.0, 192.168.1.2, LAN & Wireless Why is it?
Router Keeps Restarting Every 10 minutes I have a WRT54GS v1.1(HyperWRT) -Wireless-WRT54GS v.3 (Alchemy v1.0 Final) and have everything working perfect execpt for the fact the router keeps restarting every 5 mins like my aim, my msn, and my servers will all reboot i currently run a p2p hub with around 500 users and it keeps getting disconnected, almost like my old router used to do before i incrased the maxconnections routing table limit, i have everything port forwarded from my router to my CLIENT then from client to my server pc. I go login to the router and it usally never has an uptime greater then 9 mins what seems to be the problem?
I always thought the sveasoft firmware was suppposed to be stable and made for servers. Any suggestions would help!
NOte: since i installed hyperwrt and increased max connections i never had this problem hosting 1000's of users thru wireless 24/7 for months on my GS v1.1 so i know that is not the problem its something with my v.3 that is dropping the connection every few mins its very annoying becuase i have to keep restarting it every time. Can ping Router attached PC from Client but not vice versa Great guide Shah, but I have a few questions. I configured everything the way you said, using the same numbers for all the settings you used. I can connect to the ROUTER web interface and the CLIENT web interface from my laptop which is connected to the CLIENT. I can also ping the PC attached to the ROUTER with my laptop, but I can't get the PC attached to the ROUTER to either connect to the CLIENT web interface, or ping the Laptop attached to the client. Filesharing does not work either way. I am using two v4 routers with stock firmware on the ROUTER router and DD-WRT v23 firmware for the CLIENT router.
Any suggestions would be appreciated. I have a solution/workaround for getting a computer to connect to the shared files on another computer across a subnet. Desktop Linksys DSL modemSamba Desktop: IP=192.168.2.202 via DHCP from Linksys Win2k Linksys: Static IP= 192.168.2.200 IP=192.168.1.109 via DHCP from the DSL modem firmware: dd-wrt v23 firewall=off DSL modem: Static IP= 192.168.1.1 Also wireless AP Samba: IP=192.168.1.110 via DHCP from the DSL modem Linux Redhat 9. Running Samba server Setup on the Linksys was done according to shah's instructions. I didn't do anything with routing. Nothing special with the setup of DSL modem or Samba. Before I found my solution to the problem I was able to ping Samba from the desktop, I was able to log into the Samba using SSH, and I was able to log into both the Linksys and DSL modem.
But I could not map a network drive. Then I found these pages. The user with the problem could connect using the IP address but not the name of the computer. This help show me part of the problem. But the steps to fixing it didn't apply to me.
I stumbled upon nbtstat command. By entering: 'Nbtstat -A 192.168.1.110' into the command prompt somehow my mapped drives started working.
I am not sure what it did. I think it found the 192.168.1.110 address and got the name for it. Now I have the command run in a.bat in my startup followed by mapping the drives. This was a solution to my problem and I hope it can help. Was wondering if someone could help a noob out. I followed the directions to 'T'.
I can access the internet with a PC attached to the client, but I can't seem to file/print share in either direction. It's like I'm only bridging internet. I have all the IP's set in accordance to the instructions, and yes, I did set the advance routing only on the router and the routing table shown in the instructions matches what I have (except the internet ip's of course). My set up is two 's (both Ver 2) with Alchemy firmware - One AP, One client, and I have a BEFSR41 linked off my AP (which works fine) (The BEFSR IP is 192.168.1.3) so there shouldn't be any problems there.
To recap.the internet works great from the client side.just can't see PC's or printers from Router side (or vice-versa). Any help would be greatly appreciated. Have you enabled sharing on each PC. Its not just a matter of getting IP's and routing correct. Files and folders need to be shared. Then DNS/Netbios also have to be setup (for sahred naming to be used) once a share is inplace do the share have permissions set? Username/passwords perhaps?
If you cannot see the share in you network places are they on the same IP subnet? If not you may need to create a mapped drive, or goto the run command and type in the UNC name and shared that you need to access.
If you need help with adding sharing and you have setup the IP in this thread then please create a new thread about file sharing since it is slightly off topic from what this threads title is about.
Through the web interface. Open your browser and navigate to the router interface (check default settings below). Under the Administration tab you will find a sub-tab called Factory defaults. On the Factory defaults page click the button labeled Restore Factory Defaults With the reset button. Have your unit powered on. Press and hold the reset button for at least 10 seconds until the power light starts blinking, then release.
When the power light goes solid, unplug the power to the router for 10 seconds. Plug the power back in and start the router. When the power light goes solid again the router is ready to use. The 30-30-30 reset If the above instructions don't work you can always try the 30-30-30 reset as follows:. When router is powered on, press the reset button and hold for 30 seconds.
(Use a paper clip or something sharp). While holding the reset button pressed, unplug the power of the router and hold the reset button for 30 seconds. While still holding the reset button down, turn on the power to the unit again and hold for another 30 seconds. This process usually works for resetting any router to it's factory setting.
Note: It is worth reading more about and what the risks and considerations are when resetting your router this way, instead of just rebooting it. WAP54G v2 Firmwares Staying up to date with the latest firmware is a good idea to keep your router even more secure from various security flaws. If you want to squeeze a little bit of extra functionality out of your router, consider flashing an open-source firmware like dd-wrt, openWRT or LEDE. Flashing a custom ROM can greatly increase the stability and functionality of your old router. Following are the firmwares that we have identified existing for the Linksys WAP54G v2: Flashing dd-wrt on the Linksys WAP54G v2 Since the WAP54G v2 has 2 MiB of flash memory, you should choose a stripped down version of dd-wrt that fits on the smaller flash.
Instructions on how to flash dd-wrt onto your Linksys WAP54G v2 can be found on the Note: Always make sure to read the wiki and howtos of dd-wrt before doing any flashing. Flashing OpenWrt on the Linksys WAP54G v2 The Linksys WAP54G v2 is supported by OpenWrt according to their Table of Hardware. So flashing OpenWrt onto it should be quite straigthforward. To get started with the flashing, head over to the and they'll take it from there. Note: Flashing custom firmwares is always on you're on own risk.
Make sure to read OpenWrt's wikis to understand the risks and how to proceed if something goes wrong. Linksys stock firmware for the WAP54G v2 Stock firmwares for the WAP54G v2 are available under the download section on the modem's. You can also refer to the router's manual for instructions on how to upgrade the firmware.