Widy/Bridging - Revision history

Admin: /* Wired-WIreless Uninvisible Bridge */

2018-01-20T16:36:40Z

Wired-WIreless Uninvisible Bridge

← Older revision		Revision as of 16:36, 20 January 2018
Line 67:		Line 67:
	What we really want is for Widy to act like a gateway. Everything happening on the OpenWrts router, happens there. Nothing leaves the private subnet unless it needs to. This approach can be accomplished using [[Linux/SSH]] and an SSH tunnel to bridge the two network interfaces. This would, e.g., let you create a bridge from one computer on the private wireless network (no network access) to another, remote computer at an IP address (on the other side, using Widy's ethernet cable).		What we really want is for Widy to act like a gateway. Everything happening on the OpenWrts router, happens there. Nothing leaves the private subnet unless it needs to. This approach can be accomplished using [[Linux/SSH]] and an SSH tunnel to bridge the two network interfaces. This would, e.g., let you create a bridge from one computer on the private wireless network (no network access) to another, remote computer at an IP address (on the other side, using Widy's ethernet cable).

	=Wired-~~WIreless~~ Uninvisible Bridge=		=Wired-Wireless Uninvisible Bridge=

	An uninvsiible bridge simply meanas that the Widy is connected to a wired network, and a wireless network, but keeps both separate. The wired network has a different IP space from the wireless network. If a computer on one side needs to reach a resource on the other, it creates an SSH tunnel through the Widy gateway.		An uninvsiible bridge simply meanas that the Widy is connected to a wired network, and a wireless network, but keeps both separate. The wired network has a different IP space from the wireless network. If a computer on one side needs to reach a resource on the other, it creates an SSH tunnel through the Widy gateway.

Admin: /* Wired-WIreless Uninvisible Bridge */

2016-03-16T17:41:26Z

Wired-WIreless Uninvisible Bridge

← Older revision		Revision as of 17:41, 16 March 2016
Line 70:		Line 70:

	An uninvsiible bridge simply meanas that the Widy is connected to a wired network, and a wireless network, but keeps both separate. The wired network has a different IP space from the wireless network. If a computer on one side needs to reach a resource on the other, it creates an SSH tunnel through the Widy gateway.		An uninvsiible bridge simply meanas that the Widy is connected to a wired network, and a wireless network, but keeps both separate. The wired network has a different IP space from the wireless network. If a computer on one side needs to reach a resource on the other, it creates an SSH tunnel through the Widy gateway.

			This would have applications, e.g., with collecting Raspberry Pi data and sending it out to a command and control server. In this case, there would be some Python script going to get the files, then copying them out over the network.

	=Related=		=Related=

Admin: /* Issues */

2016-03-16T17:40:25Z

Issues

← Older revision		Revision as of 17:40, 16 March 2016
Line 66:		Line 66:

	What we really want is for Widy to act like a gateway. Everything happening on the OpenWrts router, happens there. Nothing leaves the private subnet unless it needs to. This approach can be accomplished using [[Linux/SSH]] and an SSH tunnel to bridge the two network interfaces. This would, e.g., let you create a bridge from one computer on the private wireless network (no network access) to another, remote computer at an IP address (on the other side, using Widy's ethernet cable).		What we really want is for Widy to act like a gateway. Everything happening on the OpenWrts router, happens there. Nothing leaves the private subnet unless it needs to. This approach can be accomplished using [[Linux/SSH]] and an SSH tunnel to bridge the two network interfaces. This would, e.g., let you create a bridge from one computer on the private wireless network (no network access) to another, remote computer at an IP address (on the other side, using Widy's ethernet cable).

			=Wired-WIreless Uninvisible Bridge=

			An uninvsiible bridge simply meanas that the Widy is connected to a wired network, and a wireless network, but keeps both separate. The wired network has a different IP space from the wireless network. If a computer on one side needs to reach a resource on the other, it creates an SSH tunnel through the Widy gateway.

	=Related=		=Related=

Admin: /* Wired-Wireless Bridge */

2016-03-16T17:36:21Z

Wired-Wireless Bridge

← Older revision		Revision as of 17:36, 16 March 2016
Line 5:		Line 5:
	An invisible bridge is a bridge that seamlessly connects two networking devices, so that they mirror one another. This allows any clients connecting to the Widy's wireless network to actually send their traffic out over a wired network. This allows them to obtain a DHCP lease from another server on the network. This can be thought of as a repeater mode for the wireless network - the wireless network serves as a wireless repeater for a wired network.		An invisible bridge is a bridge that seamlessly connects two networking devices, so that they mirror one another. This allows any clients connecting to the Widy's wireless network to actually send their traffic out over a wired network. This allows them to obtain a DHCP lease from another server on the network. This can be thought of as a repeater mode for the wireless network - the wireless network serves as a wireless repeater for a wired network.

	=Wired-Wireless Bridge=		=Wired-Wireless Invisible Bridge=

	==How It Works==		==How It Works==
Line 16:		Line 16:

	The bridge is then created, which allows all traffic to flow between the ethernet and wireless interfaces.		The bridge is then created, which allows all traffic to flow between the ethernet and wireless interfaces.

			The bridge is invisible because each computer on either side does not see the interface, there is no filtering of traffic, and the two network devices mirror each other.

	==First Steps==		==First Steps==

Admin: /* Bridging */

2016-03-16T17:35:05Z

Bridging

← Older revision		Revision as of 17:35, 16 March 2016
Line 1:		Line 1:
	=Bridging=		=Bridging=

	~~Bridging~~ the Widy ~~can take~~ two ~~forms:~~		There are many kinds of bridges you can build on the Widy.
	* Bridging a wired ~~and~~ a wireless ~~connection~~
	* Bridging two wireless ~~connections (~~repeater ~~mode)~~		An invisible bridge is a bridge that seamlessly connects two networking devices, so that they mirror one another. This allows any clients connecting to the Widy's wireless network to actually send their traffic out over a wired network. This allows them to obtain a DHCP lease from another server on the network. This can be thought of as a repeater mode for the wireless network - the wireless network serves as a wireless repeater for a wired network.

	=Wired-Wireless Bridge=		=Wired-Wireless Bridge=

Admin: /* Issues */

2016-03-16T17:26:00Z

Issues

← Older revision		Revision as of 17:26, 16 March 2016
Line 48:		Line 48:

	=Issues=		=Issues=

			==Consistency Issues with Internet Connection==

	Having some consistency issues connecting to the internet from the Widy's OpenWrts wireless network.		Having some consistency issues connecting to the internet from the Widy's OpenWrts wireless network.

	However, with one computer (Linux, morpheus) I am able to consistently start from no network connections, bring up wireless, connect to Widy, and access a random Wikipedia page.		However, with one computer (Linux, morpheus) I am able to consistently start from no network connections, bring up wireless, connect to Widy, and access a random Wikipedia page.

			==IP Schema Issues==

	The IP address schema of the Widy also seems to be screwed up somehow. I plug the ethernet cable into a router. I set the Widy to assign IP addresses to wireless clients from the namespace 192.168.1.X. Then I create the wired-wireless bridge.		The IP address schema of the Widy also seems to be screwed up somehow. I plug the ethernet cable into a router. I set the Widy to assign IP addresses to wireless clients from the namespace 192.168.1.X. Then I create the wired-wireless bridge.

Admin: /* Issues */

2016-03-16T17:25:23Z

Issues

← Older revision		Revision as of 17:25, 16 March 2016
Line 49:		Line 49:
	=Issues=		=Issues=

	~~Can't connect~~ to ~~wider~~ internet from ~~one node on~~ the network,		Having some consistency issues connecting to the internet from the Widy's OpenWrts wireless network.

	~~Can~~ connect to ~~the wider internet from another node~~.		However, with one computer (Linux, morpheus) I am able to consistently start from no network connections, bring up wireless, connect to Widy, and access a random Wikipedia page.

	~~Can't consistently piggyback~~ a ~~network connection through~~.		The IP address schema of the Widy also seems to be screwed up somehow. I plug the ethernet cable into a router. I set the Widy to assign IP addresses to wireless clients from the namespace 192.168.1.X. Then I create the wired-wireless bridge.

	~~Trying~~ a ~~different~~ IP address ~~schema~~.		If the wired-wireless bridge already exists, any new node that joins the network is automatically assigned an IP address by the router. If my home router is on 10.0.0.1, it is assigning IP addresses in the namespace 10.0.0.X. That means a computer that connects to the Widy OpenWrts wireless network will be asking for a DHCP lease, signed with its unique mac address, which will be directly forwarded on through to the Widy's wireless cable, and reach the router. This will then assign a new IP address to that mac address.

			This is not quite what we want. This makes the Widy a WIRELESS REPEATER, and allows us to join wireless and wired.

			What we really want is for Widy to act like a gateway. Everything happening on the OpenWrts router, happens there. Nothing leaves the private subnet unless it needs to. This approach can be accomplished using [[Linux/SSH]] and an SSH tunnel to bridge the two network interfaces. This would, e.g., let you create a bridge from one computer on the private wireless network (no network access) to another, remote computer at an IP address (on the other side, using Widy's ethernet cable).

	=Related=		=Related=

Admin: /* Bridging Wired Connection */

2016-03-16T17:18:58Z

Bridging Wired Connection

@@ Line 5: / Line 5: @@
 * Bridging two wireless connections (repeater mode)
-=Bridging Wired Connection=
+=Wired-Wireless Bridge=
 The first step to bridging a wired and wireless connection is figuring out how to connect to a wired network with the Widy. When you connect the Widy to a router that's connected to the internet, it won't immediately be able to obtain an IP address.

Admin: /* Issues */

2016-03-16T06:50:00Z

Issues

← Older revision		Revision as of 06:50, 16 March 2016
Line 40:		Line 40:

	Can connect to the wider internet from another node.		Can connect to the wider internet from another node.

			Can't consistently piggyback a network connection through.

			Trying a different IP address schema.

	=Related=		=Related=

Admin: /* Victory Dance */

2016-03-16T06:27:59Z

Victory Dance

← Older revision		Revision as of 06:27, 16 March 2016
Line 31:		Line 31:
	Now you can seamlessly connect to the internet from your devices connected only to the Widy's access point, the OpenWrts wireless network.		Now you can seamlessly connect to the internet from your devices connected only to the Widy's access point, the OpenWrts wireless network.

	===Victory Dance===		==Victory Dance==

	Hooray! You have now simultaneously created a working wireless network.		Hooray! You have now simultaneously created a working wireless network.