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?
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. This Limited Warranty does not apply in Australia. Consumers in Australia have statutory rights in relation to the Software and media on which the Software is provided under the Australian Consumer Law.
To the extent warranties cannot be disclaimed or excluded, they are limited to the duration of the Warranty Period indicated above. It is your responsibility to back up your system, including without limitation, any material, information or data that you may use or possess in connection with the Product or Software, and Belkin shall have no liability for your failure to back up your system or any material, information or data.
Some Belkin Products and Software may monitor energy consumption in the home. Belkin does not guarantee or promise any specific level of energy savings or other monetary benefit from the use of the Products or Software or any other feature. From time to time, Belkin may use the Software to provide you with information that is unique to you and your energy usage and suggests an opportunity to save money on energy bills if you adopt suggestions or features of the Product or Software.
You acknowledge that this information is not a guarantee of actual savings, and you agree not to seek monetary or other remedies from Belkin if your savings differs. We cannot guarantee that it is correct or up to date. In cases where it is critical, accessing information through the Software is not a substitute for direct access of the information in the home.
The warranties and remedies set out in this Agreement are exclusive, and, to the extent permitted by law, in lieu of all others oral or written, express or implied. You agree to strictly comply with all export control laws and regulations and agree not to export, re-export, divert, transfer or disclose any portion of the Software or any related technical information or materials, directly or indirectly, in violation of any applicable export law or regulation.
All U. Government users acquire the Software and user documentation with only those rights herein that apply to non-governmental customers. Use of either the Software or user documentation or both constitutes agreement by the U. If any portion of this Agreement or any of its terms is found to be void or unenforceable by law in a particular jurisdiction, such portion or terms shall be interpreted and enforced to the maximum extent allowed in such jurisdiction, and the remaining provisions or any part thereof will remain in full force and effect.
This Agreement constitutes the entire agreement between Belkin and you with respect to the Software and your use thereof and supersedes any conflicting or additional terms contained in any purchase order or elsewhere.
No provision of this Agreement may be waived, modified or superseded except by a written instrument signed and accepted by Belkin and you. However, the Belkin Privacy Policy referenced herein is subject to change in the manner described in that document. Belkin may provide translations of this Agreement as a convenience to users.
However, in the event of a conflict or inconsistency between the English and any non-English versions, the English version of this Agreement shall govern, to the extent not prohibited by local law in your jurisdiction. Any suppliers of Belkin shall be direct and intended third-party beneficiaries of this Agreement, including without limitation with respect to the disclaimers of warranties and limitations on liability set forth herein.
Other than as set forth in the preceding sentence, a person or entity who is not a party to this Agreement shall not have any right to enforce any term of this Agreement. No failure or delay in exercising any right or remedy shall operate as a waiver of any such or any other right or remedy. The language of this Agreement shall not be construed strictly for or against either party, regardless of who drafted such language or was principally responsible for drafting it.
The rights and obligations under this Agreement are not assignable by you, and any attempted assignment shall be void and without effect. This Agreement shall bind and inure to the benefit of the parties and their successors and permitted assigns. You have the right to opt-out of this mandatory arbitration provision. If you opt-out, you will retain your right to file a lawsuit. If you do not opt-out, you will have agreed to the mandatory arbitration set forth below.
In order to opt out of mandatory arbitration, you must i mail written notification to Belkin International, Inc. In either case, such written notification must include your name, address, and a clear statement that you do not wish to resolve disputes with Belkin through arbitration.
Any opt-out request received after the Opt-Out Deadline will not be valid and you must pursue your Dispute in arbitration or, if the dispute qualifies, in small claims court.
If you are located outside of the United States, or if Section 17 does not apply to you or is otherwise unenforceable as adjudicated by a court of competent jurisdiction, then Section 18 applies to you:. The courts in some countries or jurisdictions will not apply California law to some types of disputes.
The courts in some countries or jurisdictions will not allow for dispute resolution by arbitration or waiver of classwide claims by you. If you are a resident of one of those countries or jurisdictions, any action arising out of or relating to this Agreement may be brought exclusively in the appropriate state or federal court in Los Angeles, California, and Belkin and you irrevocably consent to the jurisdiction of such courts and venue in Los Angeles, California.
However, if you are a consumer and you live in a country where Belkin markets or distributes the Software, local law may require that certain consumer protection laws of your country of residence apply to some sections of this Agreement. In addition, Belkin may seek injunctive relief in any court having jurisdiction to protect its intellectual property rights.
If you are a natural person who resides in a country in the European Union, the laws of the member state in which you are a resident shall apply to this Agreement and any disputes potentially arising in connection thereto. The courts of the member state in which you reside shall have non-exclusive jurisdiction over any such dispute. Residents of countries in the European Union may also bring any such dispute before a local consumer dispute resolution body, if any such body is constituted under the laws of the country in which you reside.
Finally click on the Administration tab at the top of the page. Change the default password for accessing your wireless router setup pages by typing a new one into the Router Password field and then confirming it. This should be a different password than the one you setup for WEP encryption, but should also be atleast 6 to 8 characters in length.
Click the Save Settings button at the bottom of the Filter List window and then Continue when the Settings are successful dialog is displayed. If you encountered any problems during this configuration procedure, please consult the manual that was included with your router or contact the manufacturer.
Your Linksys Wireless Router is now secure. A-Z Index Help.
0コメント