This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
mobile-video [2009/07/27 17:37] hytham |
mobile-video [2009/08/25 14:40] (current) hytham |
||
---|---|---|---|
Line 50: | Line 50: | ||
**Testing SplitSockets** | **Testing SplitSockets** | ||
- | - TBD | + | - Checkout modified kernel per instructions below. Type 'make' within scratchbox to compile the kernel, and use the above instructions for flashing it into the device. |
+ | - <fill in with link to Josh's splitsockets stuff> | ||
**Bluetooth PAN Support** | **Bluetooth PAN Support** | ||
Line 63: | Line 64: | ||
* After a few seconds, bnep0 will show up in 'ifconfig -a' of both devices. Assign static IPs to each interface and you should be able to ping! | * After a few seconds, bnep0 will show up in 'ifconfig -a' of both devices. Assign static IPs to each interface and you should be able to ping! | ||
- Note: the Linksys USBBT100 v2 has a Broadcom chipset and as such requires proprietary firmware (which as of now is hard to find or unavailable) for compatibility with bluez v4.0. As a result, downgrade bluez-utils to v3.0 (which seems to function with the USBBT100 reasonably well). As of now, I am also having issues setting the USBBT100 as the GN, so setup the N800 as the GN and the Ubuntu VM as a connecting node. If you notice that the USBBT100 isn't showing up when doing a scan from another device, type 'hciconfig hci0 iscan'. | - Note: the Linksys USBBT100 v2 has a Broadcom chipset and as such requires proprietary firmware (which as of now is hard to find or unavailable) for compatibility with bluez v4.0. As a result, downgrade bluez-utils to v3.0 (which seems to function with the USBBT100 reasonably well). As of now, I am also having issues setting the USBBT100 as the GN, so setup the N800 as the GN and the Ubuntu VM as a connecting node. If you notice that the USBBT100 isn't showing up when doing a scan from another device, type 'hciconfig hci0 iscan'. | ||
+ | |||
+ | **Ad-Hoc Wifi Network on N800** | ||
+ | - Disconnect from any wifi network. | ||
+ | - Go to a root terminal and type the following commands. | ||
+ | * ifconfig wlan0 192.168.1.1 255.255.255.0 | ||
+ | * iwconfig wlan0 mode Ad-Hoc essid N800Gateway key off | ||
+ | |||
+ | **SOCKS Proxy** | ||
+ | - Setup one N800 as a GN and connect the second N800 to the GN (see above for Bluetooth PAN support). | ||
+ | - Assign static IPs to both N800s (i.e. 10.0.0.1 and 10.0.0.2). | ||
+ | - Connect the second N800 to a valid wifi network, and setup the first N800 as an Ad-Hoc wifi network. | ||
+ | - Establish a SOCKS ssh session from the first N800 to the second N800. | ||
+ | * ssh -D 8080 10.0.0.2 | ||
+ | - To browse the web on the first N800, open Web and browse to about:config. Type the following into the Name and Value fields at the top of the page. | ||
+ | * network.proxy.socks localhost | ||
+ | * network.proxy.socks_port 8080 | ||
+ | * network.proxy.socks_remote_dns true | ||
+ | * network.proxy.type 1 | ||
+ | - Note: network.proxy.type must be set to 1 for every new window of the browser. Bookmark the page after setting it to allow quick access. | ||
+ | - To browse the web on a wifi client connected to N800Gateway, setup Firefox with the above proxy settings and establish an ssh port forwarding session using the following command. Note: you may have to set a static IP on the client. | ||
+ | * ssh -f root@192.168.1.1 -L 8080:127.0.0.1:8080 -N | ||
**CVS Module / Tag Information** | **CVS Module / Tag Information** |