 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Wifi/client-bridge/subnets???</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/wificlient-bridgesubnets/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/wificlient-bridgesubnets/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 15:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: amnzero</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/wificlient-bridgesubnets/#comment-95020</link>
		<dc:creator>amnzero</dc:creator>
		<pubDate>Fri, 05 Aug 2011 05:22:28 +0000</pubDate>
		<guid isPermaLink="false">#comment-95020</guid>
		<description><![CDATA[The router on side B should be configured as a gateway which will connect to its wan using DHCP to obtain its external address. It should have an internal IP of 192.168.2.1, and an IP range of 192.168.2.2 to 192.168.2.(2 + the number of connections you expect to have) on its own DHCP server. The subnet mask can be the same.

This should allow the two networks to be separated (invisible to each other, but still able to communicate), but still be able to communicate with the internet.

Additionally, you can set the Workgroups of the machines on each side to a different workgroup name for more security between the two sides.

This works on my network. My setup is shown below.
DIR-601(192.168.0.1 - connected to the internet)&lt;---Wireless---&gt;DIR-601(192.168.1.1)&lt;---Ethernet---&gt;Computer(192.168.1.2 - Able to access the internet)]]></description>
		<content:encoded><![CDATA[<p>The router on side B should be configured as a gateway which will connect to its wan using DHCP to obtain its external address. It should have an internal IP of 192.168.2.1, and an IP range of 192.168.2.2 to 192.168.2.(2 + the number of connections you expect to have) on its own DHCP server. The subnet mask can be the same.</p>
<p>This should allow the two networks to be separated (invisible to each other, but still able to communicate), but still be able to communicate with the internet.</p>
<p>Additionally, you can set the Workgroups of the machines on each side to a different workgroup name for more security between the two sides.</p>
<p>This works on my network. My setup is shown below.<br />
DIR-601(192.168.0.1 &#8211; connected to the internet)&lt;&#8212;Wireless&#8212;&gt;DIR-601(192.168.1.1)&lt;&#8212;Ethernet&#8212;&gt;Computer(192.168.1.2 &#8211; Able to access the internet)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/8 queries in 0.014 seconds using memcached
Object Caching 269/270 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 16:18:49 -->