Manuevered Some connections around to make way for a special VLAN

Over the weekend I made some changes to my network in preparation for venturing out as an Anonymous user.  My real reason for doing this is to see if I can somehow escape Google's tracking.  This is an interesting twist since I am using Blogger to blog on and that in turn is owned by Google.

I have been reading up on the DarkNet and what that really means.  Since I am getting more involved with security I thought it might be a good thing to explore various anonymization networks, e.g. TOR, to see how they function and what to expect when I am out there.  This obviously involves assuming a pseudo id to mask who I really am - new territory, haven't ventured there before.

I was able to set up a VLAN on the ActionTec router from http://support.actiontec.com/doc_files/Creating_an_Ethernet_VLAN.pdf on the ActionTec site.  The instructions are a little old but after a bit of trying out different things, I was able to have a VLAN (tagged) on a specific port with a DHCP server and a localized subnet.  I then proceeded to change the wiring around a little, moving my MacMini ethernet connections from the tail-end switch to the one just before it.  I set up the first switch to have a tagged input port then connected an Ethernet cable from the ActionTec to it.  Next I set up the switch to send the new VLAN down a trunk line to the second switch and from there to the third and last switch.  In the process of doing this I consolidated a number of Ethernet connections to one switch which actually speeded up my access to the outside.  I was also able to reduce the usage of the last switch in the stream to make it more experimenter like, including adding the new VLAN.

I now have a line from the ActionTec router that has only one port (I will be putting a laptop on this port) isolated from my network that I will be able to use for Anonymity.

I've been out of the loop over the holidays

Sorry for not posting since the end of November.  I have been busy with home life and work and have not had a chance to get back to this blog.  New posts to come shortly.

I now have a personal cloud device in the home network

I just purchased a Western Digital My Cloud drive (3TB) and added it to my network in the Pers vlan.  Right up front I can say that I am very pleased with this drive and how it operates.  The My Cloud drive has a 1GB Ethernet port and a USB 3.0 port on the back.  The 1GB Ethernet gives the drive plenty of flexibility to stream media content within the house, so I am planning on using it to host both video and audio files for use throughout.  I have also connected a 4TB backup drive to the USB 3.0 port on the back, giving a total of 7TB of storage.

I was able to get the drive up and running through the WD website for use with my iOS apps.  The 4TB drive shows up as a share on the drive, which is perfect.  Unfortunately, my work network's proxy server doesn't recognize the WD website, so I had to go through our guest wireless to test out general access via PC from work.  I was able to log into the WD website and select one of the shares to be opened in Windows Explorer, and it came right up.  So that is an interesting way to interface to the drive from the outside.  It appears that Western Digital did their homework.

The problem that I am currently facing is that the My Cloud drive is on my Pers vlan while the media components (that would make use of the video and audio file storage) are on the Media vlan.  At the moment I am in the process of setting up an Ubuntu VM to be the router between the Pers and Media vlans.  My constraints are as follows:

• Use Shorewall firewall on Ubuntu VM to do routing; propose using Media and Pers zones; connection is via the vlans that were created on the Thunderbolt interface.  These show up as different ethX devices in the Ubuntu VM
• Using 1 to 1 NAT, present the Mac Mini and the My Cloud drive on the Media vlan with Media vlan IPs
• Setup firewall to allow connection to iTunes protocol, AFS protocol, SMB protocol, and http protocol on the My Cloud drive from Media vlan
• Setup firewall to allow connection to iTunes protocol, AFS protocol on the Mac Mini from Media vlan

More later.

Some Thoughts on a Remote Wireless Access Device

The thought occurred to me today that I might want to set up a version of the RPi Router that would be able to be an extension of my home system.  What I want to do is take the RPi Router into my office at work, turn it on, and have it use the same SSID, but via an SSH tunnel, go into my system at home.  I would need to be able to:

1. Use dual wi-fi access, provide a connection to the work wi-fi network (with auto authentication) and provide the same SSID as my home.  Not sure if I need two USB wi-fi dongles or not.
2. The connection should use an SSH tunnel which is kept up in the background, allowing me to use any of the systems that I have in my house.
3. Somehow, this RPi Router should provide a DHCP forwarding from my house to whatever device hooks into the router.  I may be able to use my new FVS318N router to accomplish some of this, since it does provide VPN capabilities (in case I cannot get the SSH tunnel to do it).  An RPi based VPN for using the FVS318N anyone?
4. Should be plug and play, i.e. put in the SD card and plug in the RPi to get it to function.  Wishing for the moon at the same time.

This obviously is a variation on some of the 1-Port Router ideas that I have had in the past.

Got in the new RFDuino

I received my incentive from the RFDuino kick starter program. I sincerely hope that the individual who started this is successful. This is a quality piece of work. I can't wait to try it out.

Issue with the FVS318N Router

I am slowly learning how to incorporate the FVS318N.  However, now I discover that there is apparently no way to setup VLAN to VLAN rules.  The router gives you the ability to make some rules for LAN to WAN, LAN to DMZ, and DMZ to WAN, but no LAN to LAN (or in my case VLAN to VLAN).  I did discover that there is a CLI (command line interface document that details some newer aspects of the router, but a cursory look into the command set did not give me the impression that there was a way to setup LAN to LAN rules.

My main motivation in setting up the LAN to LAN rules is to allow the Media VLAN to be able to access the Plex server running on my Mac Mini which is on a completely separate VLAN.  In addition to that, I use the Mac Mini as the main workstation for modifying the routers and switches in my home network.  Yea, I know, way too much - but I enjoy doing what I do.  I was thinking that I might try my hand at setting up either a Raspberry Pi router or setup a VM on the Mac Mini to do the routing.  What would be perfect is if I could do it on the new FVS318N.  This router will be able to replace about 3 devices if I succeed. 

Update: I figured out that if I use a "1 to 1 NAT" from a router, I can have an IP show up in one VLAN from a device resident in another VLAN with a different IP.  I am currently working the issue using a VM on the Mac Mini to do the routing with Shorewall.  Once I get that up and running, I will transfer it to a Raspberry Pi router which will be on all the time.

Found an interesting thing while using one of my routers

This weekend while fooling around with one of my routers, I chanced to put the WAN input of the main router onto my DMZ vlan.  I was able to have a full connection to the outside after I got rid of the first ethernet cable that I was using (it did not register as being connected).  When I connected the main router to my DMZ vlan, I noticed that I had a GHz connection (thanks to the GBit switch that I was using) and I was able to connect to the outside with no apparent slowdown of the speed.

I still have an issue though, because I set up the ActionTec router to route specific ports to my main router.  However, with this new connection, I have a means of controlling pretty much everything in the house.  I was wondering how I might fit my new FVS318N router into the mix.  Originally, I was going to put it upstairs and replace 3 devices (my main router, the upstairs switch and the router I use with the media vlan downstairs).  The media vlan router is connected into the DMZ vlan in the downstairs bedroom.  I was going to use the FVS318N to replace it as I could set up multiple dhcp servers, each tuned to a separate vlan.  This has been the issue throughout my house as I expand the capabilities of my setup.

Sounds like I need to explore a little more of what vlans can do for me.