Wireless Networking - Revision history

Mcefan at 11:34, 8 October 2012

2012-10-08T11:34:45Z

←Older revision		Revision as of 11:34, 8 October 2012
Line 3:		Line 3:
	\| __TOC__		\| __TOC__
	\|}		\|}
	[[Category:Networking\|*Network Setup]]		[[Category:Networking\|*Network Setup, Wireless]]

	==Wireless Access Points==		==Wireless Access Points==

Mcefan at 11:33, 8 October 2012

2012-10-08T11:33:53Z

←Older revision		Revision as of 11:33, 8 October 2012
Line 3:		Line 3:
	\| __TOC__		\| __TOC__
	\|}		\|}
	[[Category:Networking\|Network Setup]]		[[Category:Networking\|*Network Setup]]

	==Wireless Access Points==		==Wireless Access Points==

Mcefan at 11:29, 8 October 2012

2012-10-08T11:29:47Z

←Older revision		Revision as of 11:29, 8 October 2012
Line 3:		Line 3:
	\| __TOC__		\| __TOC__
	\|}		\|}
	[[Category:Networking]]		[[Category:Networking\|Network Setup]]

	==Wireless Access Points==		==Wireless Access Points==

Wierdbeard65 at 08:47, 5 May 2010

2010-05-05T08:47:58Z

←Older revision		Revision as of 08:47, 5 May 2010
Line 1:		Line 1:
			{{versioninfo}}
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__

Ray N at 02:36, 11 August 2009

2009-08-11T02:36:34Z

←Older revision		Revision as of 02:36, 11 August 2009
Line 2:		Line 2:
	\| __TOC__		\| __TOC__
	\|}		\|}
	~~[[Category:Hardware]]~~
	[[Category:Networking]]		[[Category:Networking]]

Perspectoff: /* Wireless Access Points */

2008-05-24T22:44:28Z

Wireless Access Points

←Older revision		Revision as of 22:44, 24 May 2008
Line 9:		Line 9:
	It is easiest to use a central switch for the LinuxMCE LAN, and connect that switch to the Core. The Core will then take care of the DHCP, firewall, DNS, and other network functions.		It is easiest to use a central switch for the LinuxMCE LAN, and connect that switch to the Core. The Core will then take care of the DHCP, firewall, DNS, and other network functions.

	To allow wireless devices, a Wireless Access Point can be connected to the switch. ~~Natutally~~, WEP/WPA/other security protocols are recommended for use between the Wireless ~~Acess~~ Point and wireless Devices.		To allow wireless devices, a Wireless Access Point can be connected to the switch. Naturally, WEP/WPA/other security protocols are recommended for use between the Wireless Access Point and wireless Devices.

	==Wireless Routers==		==Wireless Routers==

Perspectoff: /* Netbooting Wirelessly */

2008-05-24T14:11:16Z

Netbooting Wirelessly

←Older revision		Revision as of 14:11, 24 May 2008
Line 37:		Line 37:
	Unless you have a wireless card with a PXE-ROM chip built into it, it is not easy to directly netboot over a wireless connection. BIOS-based PXE algorithms usually only search for a wired NIC card to be used in a PXE [[netboot]].		Unless you have a wireless card with a PXE-ROM chip built into it, it is not easy to directly netboot over a wireless connection. BIOS-based PXE algorithms usually only search for a wired NIC card to be used in a PXE [[netboot]].

	Some users have cleverly connected a "Wireless Bridge" (i.e. a wireless router or Access Point set to the "bridge" mode) to the wired NIC card in their PC. The PC then netboots through the wired Ethernet NIC as usual, but the data is then transmitted from the NIC to the Wireless AP/Router connected to it and then wirelessly "across the bridge" to the Wireless Access Point/Router that is connected to the Core.		Some users have cleverly connected a "[http://en.wikipedia.org/wiki/Wireless_bridge Wireless Bridge]" (i.e. a wireless router or Access Point set to the "bridge" mode) to the wired NIC card in their PC. The PC then netboots through the wired Ethernet NIC as usual, but the data is then transmitted from the NIC to the Wireless AP/Router connected to it and then wirelessly "across the bridge" to the Wireless Access Point/Router that is connected to the Core.

	This solution works pretty well, but of course you must have two Wireless Access Points/Routers (one on each side of the "bridge"). These both should be Wireless-N (so you can have decent transmission speeds), and your costs will therefore start to increase. Still, this is sometimes easier than running extra Ethernet cables throughout your home.		This solution works pretty well, but of course you must have two Wireless Access Points/Routers (one on each side of the "bridge"). These both should be Wireless-N (so you can have decent transmission speeds), and your costs will therefore start to increase. Still, this is sometimes easier than running extra Ethernet cables throughout your home.

Perspectoff: /* Netbooting Wirelessly */

2008-05-24T14:08:54Z

Netbooting Wirelessly

←Older revision		Revision as of 14:08, 24 May 2008
Line 35:		Line 35:
	==Netbooting Wirelessly==		==Netbooting Wirelessly==

	Unless you have a wireless card with a PXE-ROM chip built into it, it is not easy to directly netboot over a wireless connection. BIOS-based PXE algorithms usually only search for a wired NIC card to ~~use~~ in a PXE netboot.		Unless you have a wireless card with a PXE-ROM chip built into it, it is not easy to directly netboot over a wireless connection. BIOS-based PXE algorithms usually only search for a wired NIC card to be used in a PXE [[netboot]].

	Some users have cleverly connected a "Wireless Bridge" (i.e. a wireless router or Access Point set to the "bridge" mode) to the wired NIC card in their PC. The PC then netboots through the wired Ethernet NIC as usual, but the data is then transmitted from the NIC to the Wireless AP/Router connected to it and then wirelessly "across the bridge" to the Wireless Access Point/Router that is connected to the Core.		Some users have cleverly connected a "Wireless Bridge" (i.e. a wireless router or Access Point set to the "bridge" mode) to the wired NIC card in their PC. The PC then netboots through the wired Ethernet NIC as usual, but the data is then transmitted from the NIC to the Wireless AP/Router connected to it and then wirelessly "across the bridge" to the Wireless Access Point/Router that is connected to the Core.

Perspectoff: /* Wireless Orbiters */

2008-05-23T04:01:28Z

Wireless Orbiters

←Older revision		Revision as of 04:01, 23 May 2008
Line 21:		Line 21:
	==Wireless Orbiters==		==Wireless Orbiters==

	~~Fortunately,~~ [[Orbiters]] do not require much bandwidth. Command data is quite small in size. Because the User Interface is [[Orbiter Generator\|pre-rendered]], it is also small in size, and not much traffic between the Core and the Orbiters is required. You can use the Orbiters wirelessly no matter what Wireless Specification you use. Wireless-B (4.5-11 Mb/sec) is fine.		[[Orbiters]] do not require much bandwidth. Command data is quite small in size. Because the User Interface is [[Orbiter Generator\|pre-rendered]], it is also small in size, and not much traffic between the Core and the Orbiters is required. You can use the Orbiters wirelessly no matter what Wireless Specification you use. Wireless-B (4.5-11 Mb/sec) is fine.

	==Media Streaming over a Wireless connection==		==Media Streaming over a Wireless connection==

Perspectoff: /* Netbooting Wirelessly */

2008-05-23T00:16:02Z

Netbooting Wirelessly

←Older revision		Revision as of 00:16, 23 May 2008
Line 41:		Line 41:
	This solution works pretty well, but of course you must have two Wireless Access Points/Routers (one on each side of the "bridge"). These both should be Wireless-N (so you can have decent transmission speeds), and your costs will therefore start to increase. Still, this is sometimes easier than running extra Ethernet cables throughout your home.		This solution works pretty well, but of course you must have two Wireless Access Points/Routers (one on each side of the "bridge"). These both should be Wireless-N (so you can have decent transmission speeds), and your costs will therefore start to increase. Still, this is sometimes easier than running extra Ethernet cables throughout your home.

	*[http://www.netgear.com/Products/APsWirelessControllers/AccessPoints/WNHDE111.aspx Netgear WNHDE111 Wireless-N Bridge] -- about $100 each in May 2008		*[http://www.netgear.com/Products/APsWirelessControllers/AccessPoints/WNHDE111.aspx Netgear WNHDE111 Wireless-N Bridge] -- about [http://www.amazon.com/gp/product/B00126V3EI $100] each in May 2008
	*[http://www.smc.com/index.cfm?event=viewProduct&localeCode=EN_USA&cid=5&scid=126&pid=1635 SMCWEB-N EZ Connect™ N Pro Draft 11n Wireless Access Point/Ethernet Client] -- about [http://shopper.cnet.com/wireless-access-points/smc-ez-connect-n/4014-3265_9-32598043.html?tag=pdtl-list $99] each in May 2008		*[http://www.smc.com/index.cfm?event=viewProduct&localeCode=EN_USA&cid=5&scid=126&pid=1635 SMCWEB-N EZ Connect™ N Pro Draft 11n Wireless Access Point/Ethernet Client] -- about [http://shopper.cnet.com/wireless-access-points/smc-ez-connect-n/4014-3265_9-32598043.html?tag=pdtl-list $99] each in May 2008