Second, wrt54g is operating in a special "client mode" which is not AP mode - these are two different modes you can choose between with this firmware. Lastly, DHCP is completely optional - you could set up the same configuration by specyfing static addresses for each computer. Ok, now for the clear and simple explanation. The main router is the default gateway for all the devices attached to it, wether wired or wireless.
That means that any packet addressed outside the local network All the devices attached to the main router have addresses in this private local network, including the client router wrt54g - its address is Things work pretty much the same way in the client's router private network the wrt54g and its attached devices - all have addresses The client router is the gateway for all its attached devices, which means that all packets addressed outside the client private network are sent to the client router, which performs NAT and forwards them to the main router.
So the main router doesn't know about all the devices in the client network, it only sees the client router with the address So with this setup the computers in the client network can contact any computer in the main network or the internet, because all externally addressed packets are forwarded by the client router to the main router Now the tricky part is how to route packets originating in the main network to computers in the client network.
This is tricky because the main router doesn't know about these computers and their addresses. In fact, it doesn't even know that the That's why I need to manually add a routing table entry which says - "send all packets addressed to Now, normally the wrt54g should not accept packets addressed directly to its local private network, because all the packets it sends are NATed, so all replies should come addressed to its external address. But the special magic of "client mode" is that the wrt54g accepts packets addressed to its own private network, and forwards them to the appropriate attached PC.
I hope you understand it now. If you want to understand better, here's the routing tables of PC-1, PC-2 and wrt54g. Originally posted by: user Second, wrt54g is operating in a special "client mode" which is not AP mode - these are two different modes you can choose between with this firmware.
Originally posted by: VirtualLarry It then makes sense, if the PCs behind the client AP are on a different IP subnet than those PCs connected to the wired ports on the "main" AP, then by default IP packets sent out from the "main" AP would get routed to the default gateway, which is the WAN interface, and they wouldn't go anywhere, so you have to manually configure the routing to assign the gateway for the client AP's local subnet to be the IP of the client AP's wireless interface, so that the packets will reach there.
Or I might have that slightly wrong, maybe the gateway for that subnet would be the "main" AP's wireless interface. Now this is starting to make some sense. In fact, it would seem that the above probably would not work at all, if all of the devices, both the ones wired to the "main" AP, as well as ones wired to the client AP, were all on the same subnet. They have to be different subnets.
But NAT has nothing directly to do with anything either, since no layer-3 address-translation seems to be needed nor happening. If so, then my theory fits. Edit: In case it wasn't totally clear, what I'm suggesting is really going on here is slightly different than NAT. Normally, all machines behind a NAT are on a local subnet with private IPs, and from the outside, there is only a single public IP address.
In this case, it's a little different, from the outside, there is only a single MAC address visible, that of the client AP's wireless interface, but it appears to have multiple IP addresses, in fact all of the IPs of the machines behind it.
The client AP recieves the frames with its own wireless MAC as the destination address, containing an IP packet with a destination IP that actually belongs to another machine, but to the outside, it appears to belong to the client AP. So it re-sends the ethernet frame containing that IP packet, except over the wired interface, with a destination MAC of the correct PC that corresponds with that destination IP on the local wired ethernet segment.
I already heard from at least two other people that got it to work, but anyone else which does it, please post your experience here. I have no doublt it will work with any existing wireless router that is, the wrt54g will serve as a wireless bridge , but would still like to hear if it worked for you without problems.
Originally posted by: user Bingo!!! Houston, we have lift off!! You are finally getting it, what you said in tha paragraph is exactly right except what you said in parenthesis at the end. Originally posted by: user I still think NAT is being done by the client AP, as the PCs in the client network are on a different private subnet, which the main router doesn't know about.
So I think the client router is translating between those private network addresses e. This is called NAT n-to-1 mode which linux kernel performs natively. Originally posted by: user Not sure how to do this on linux, but I can check the logs on the main router yep, the DI is quite a nice router, for sure which show all the connected wired and wireless clients by MAC address, and the only wireless client listed as currently connected is the client AP wrt54g mac address.
Does that answer your question? Originally posted by: user I think you can call this a double NATed configuration, which is how skyking correctly described it all along. I would think that normally these packets should be blocked by a NAT router. The links below describe essentially the same thing as what I did, but in a little less clear and concise fashion.
I just wanted to give people a simple one-stop-shop guide so they don't have to chase around bits and pieces of information, or try out an endless number of configurations, which could be quite daunting to people with little networking knowledge.
Did you catually read the first paragraph of this sveasoft documentation page? The wireless mode list box shown has 3 options - AP, Client, and Ad-hoc. I've been using Client mode, not AP mode. In this mode you cannot connect to the WRT54G that is in client mode using another wireless client device".
And "AP mode: This is the default mode. It acts like a half-duplex HUB in the wired networks". I've been using client mode not AP mode! And btw, NAT is "network address translation", which is happening here. Don't get confused by the routing entry I added. In fact, it would be simpler to understand the setup without it.
In that case, the hosts in the client network are indeed unreachable from the main network, but the main network is reachable from the client network. So this is classic NAT, right? To work around this limitation, I had to add an entry to tell a compuer in the main network to route packets addressed to the client network addresses to the client router's address on the main network. So even though a PC on the main network can't directly send to a PC on the client network, it can send to the client gateway which I added to its routing table I hope you understand routing tables, because that's what's used to implement all these high level policies.
So obviously, the main network PC never sees the mac address of PCs in the client network. And for the last time, there is no WDS - in fact, I changed nothing in the configuration of the DI when adding the wrt54g and its attached devices - that's part of the simplicity of this solution - no chance to mess up your existing configuration. Of course, this only works after I add the routing table entry: route add -net Feb 12, 1 0 0.
Thanks for all the good work user! I think you might be able to help me with this one. I have limited network experience so need your help with this. I have both of the ap and the bridge talking getting an ip from the dhcp. If not is there a way for the computers in the two subnets to see each other? Maybe throught the different subnets? If so would I also make the routes in the Firewall or in the router or both to connect the two differnet subnets?
This is so we can connect the computer from both sides of the network to see the windows domain and connect to it using windows xp pro. Nutdotnet Diamond Member. Dec 5, 7, 3 My question is, and after reading this thread seems possible, but how exactly does one go about allowing PC1 and PC2 to speak to each other? So, is it possible to FTP into the Xbox with this setup? Setting up a wireless security key or password to your network is the best way to prevent other people from using your wireless Internet connection.
For detailed instructions, click here. For instructions on how to set up your router manually, click on the specific link that applies to your Internet connection type:. If you are experiencing corrupted files when you download a file with your FTP client, try using another FTP software.
It depends on which network game or what kind of game server you are using. Otherwise, game servers most commonly do not allow logins using the same IP Address. Set your Ethernet adapter to 10 Mbps or half duplex mode , and turn off the Auto-negotiate feature of your Ethernet adapter as a temporary measure.
Make sure that your proxy setting is disabled in the browser. First, you can reset the router. You can also power cycle your Cable or DSL modem by unplugging the power cord from the power outlet for at least a minute then plug it back in. Then update the firmware of your router. Theoretically, the router can establish sessions at the same time, but you can only forward 10 ranges of ports. This error message will appear if you are connected to a router or access point that does not have active Internet connection.
Make sure that your router is properly configured for Internet connection. For instructions on setting up your router, click on the links below:. The button should be lit in either orange or white color. Any wireless device like a wireless TV can be connected directly to the router but not through the computer that is connected to it. An SNMP feature is used to monitor devices within a large network as a management system.
The Linksys WRT54G router has a limited network monitoring system, restricted only to monitor incoming and outgoing network traffic. Belkin International, Inc. Software does not include any Open Source Software as defined below. As part of this license, you may A operate the Software in the manner described in the user documentation for the Software; B where the Software is provided for download onto a personal computer or mobile device, make as many copies of the Software as you reasonably need for your own use this does not include firmware ; and C permanently transfer all of your rights to use the Product including but not limited to the Software to another person, so long as that person also agrees to be bound by this Agreement, and following such transfer you stop using the Product and the Software.
The Software is made available to you on the basis of a limited license only as set out in this Agreement. You have the non-exclusive right to use the Software in accordance with this Agreement. All rights not expressly granted to you by Belkin under this Agreement are hereby reserved by Belkin. You will not acquire such rights, whether through estoppel, implication, or otherwise.
If you have downloaded the Software from an App Store, you are also subject to any terms of use of that App Store. Such terms of use may prohibit you from doing some of the things you are permitted to do under this Agreement or permit you to do some of the things you are prohibited from doing under this Agreement.
Notwithstanding anything to the contrary in this Agreement, by using the Software, you acknowledge and agree that it is solely your responsibility to understand the terms of this Agreement, as well as the terms of use of any App Store that may be relevant to the Software or the Product.
While Belkin is not required to do so, Belkin may provide you with upgrades or updates to this Software. Some Products include an auto-update feature, which gives us the ability to make updates automatically. You can change auto-update options by changing your settings within the Product account information. In very limited cases, updates may still be automatically applied, regardless of the auto-update setting. For example, we may provide an automatic update that fixes a security breach or vulnerability to your network.
We may also provide you with updated Software data files automatically to benefit you, such as to provide you with updated device information to identify new devices in your network. These data files do not update your firmware but consist of Software files that are cached on your Product and override older files.
By agreeing to this Agreement, you agree to automatic updates. Belkin is committed to protecting your privacy. Our privacy practices are described in the Privacy Policy, as well as in separate notices given when an app, product or service is purchased or downloaded. At all times your information will be treated in accordance with the Belkin Privacy Policy, which is incorporated by reference into this Agreement and can be viewed here.
You hereby acknowledge that the Software may contain Open Source Software. This license does not apply to Open Source Software contained in the Software. Rather, the terms and conditions in the applicable Open Source Software license shall apply to the Open Source Software. Nothing in this Agreement limits your rights under, or grants you rights that supersede, any Open Source Software license. You acknowledge that the Open Source Software license is solely between you and the applicable licensor of the Open Source Software.
You shall comply with the terms of all applicable Open Source Software licenses, if any. Belkin is not obligated to provide any maintenance or support for the Open Source Software or any Product Software that has been modified by you pursuant to an Open Source Software license. Open source licenses are generally licenses that make source code available for free modification and distribution, but can also apply to technology received and distributed solely in object code form.
All title and intellectual property rights including without limitation all copyrights, patents, trade secret rights and trademark rights in and to the Software including but not limited to any content incorporated into the Software , the accompanying printed materials, and any copies of the Software, are owned by Belkin or its suppliers. Therefore, you must treat the Software like any other material protected by laws and treaties relating to international property rights and in accordance with this Agreement.
These features are provided solely as a convenience to you. You will need to make your own independent judgment regarding your interaction with any Linked Sites. You hereby waive and release any legal claim you might have against Belkin with respect to these sites or third-party products or services, and your use of these sites, third-party products or services.
We encourage you to read the terms and conditions and privacy policy of each third party website that you choose to visit. If Belkin is the subject of a claim, becomes involved in a legal proceeding, or suffers any economic loss or damage as a result of your violation of this Agreement, to the extent permitted by law, you will be responsible for compensating Belkin for the full amount of its loss, as well as any reasonable amounts Belkin incurs in lawyers' fees, expenses and court costs, except to the extent that Belkin contributed to the loss or damage.
Once accepted, this Agreement remains in effect until terminated. The limited license in this Agreement will automatically terminate if you fail to comply with any of the terms and conditions in this Agreement. You agree that upon such termination, you will immediately destroy all programs and documentation that relate to the Software, including all copies made or obtained by you, and otherwise cease use of the Software.
If the Software has been installed on a personal computer or mobile device, you must uninstall the Software immediately. You said you have gotten into the WRT54G. This will depend on your ISP. Try to follow the manual. The basic setup is all you need this time and then, if you like, later on go to advanced configuration. If you can't get these information from your ISP. You might get these information from it.
I can't guarantee it will work, but it might be worth a try. Export the item and then delete it and see if that helps. Doesn't, double click on the. REG saved file and put it back. I exported it then deleted the entry. I added an entry for the WRT54G that followed the style of the one that was in there for the mn I then restarted my PC. At least I got back my mn wireless network. Thanks for the idea but it didn't work.
I told them I purchased this one used at an auction and it did not have the CD. I asked if I could download the setup program and they told me it was not available for download.
How do you like that! Nice people aren't they. I looked at the link you provided. That is not possible! I have one Ethernet connection on my computer. Thanks for trying. I still need the Setup CD. Even if you have the setup CD it will basically accomplished same result as manual configuration through the user guide manual. I had the same Linksys model once and the accompanying setup CD. And believe me, the CD setup won't help you when problems with the configuration arise. It will just terminate the setup with and error message with no clear-cut explanation on the error.
G41M; you are missing my point. I have one computer running. If I want working internet then I have my ethernet cable connected to my DSL router and that gives me a working internet connection.
With only one ethernet connection on my computer and it connected to the DSL to provide the working internet connection that doesn't leave any ethernet connection to use on the WRT54G to configure it. I guess i will just stay with the working MN wireless router and scrap the WRT54G router because there is no way that I can figure out to get it working. If I could find someone who has it working with a DSL connection from the old Bell South using a Westell DSL router and I could get them to write down all the information from there setup maybe I could get it working but the chance of finding this is very small.
So I guess I will just stay with what I have working.
0コメント