First off I want to give mad props to Google for making Blogger work in lynx. You guys rock my console.
With that out of the way, I thought I'd give a little update as to what I've been doing lately. Most of my 'free time' has been spent helping to bring a hackerspace online in Norfolk, VA. 757 Labs is a project formed from a local technology social group called HRGeeks. I've been hanging out with these guys for a while, and even used to know a few of them when I was in high school. It's been a lot of fun, and as I seem to have become the network admin it's been a great learning experience. My home network just didn't offer the level of complexity that the lab network does. Maintaining a number of VLANs, making sure that visitors have working internet connection while keeping the main network secure with both hardline and wireless access for everything. I've learned that there were things I didn't even know that I didn't know. Of course, that's part of why I'm here, so it's all good.
My own personal projects have mostly been on hold for the time being, partly because this has been much more fun, and partly because once the space is active I'll be able to use it for my projects. Win/Win!
I can't believe I just typed that. I feel so lame. Oh well, it stands.
Now, why did I happen to come to know that Blogger works in lynx? Well, I'm at the lab now, upstairs at the server racks, about to shut down the audio stream I've been running, and got the urge to type this. As for that audio stream, Matt Lestock (former Hak5 host, and all-around spiffy fellow) has restarted his old internet radio show. What, you didn't know? Well carry yourself over to www.jeffandchew.com, and check it out. I'll wait...
Got the skinny? Good. Listen weekly, you'll be glad you did. Just don't listen with small children or people that can't take a joke. You've been warned.
That's about all I have for now. I'm going to try to get back into posting more, now that I'll have more to post about. Until then, keep doing what you do, as no one else can do it better than you.
Showing posts with label networking. Show all posts
Showing posts with label networking. Show all posts
Case Sensitivity: It's not just for passwords anymore
Me: Connect to SSID 'accesspoint' with 'this password'
FreeBSD: I don't see SSID 'accesspoint'
(disable encryption)
Me: Connect to SSID 'accesspoint' without a password
FreeBSD: I don't know what you're talking about
(connect with another computer)
Me: It's there, the Mac can see it
FreeBSD: I don't care if we're related, I'm not the Mac and I don't know what you're talking about
(verify the access point is in b/g mode)
Me: O'kay fine, connect to the first thing you see
FreeBSD: Connected to SSID 'Accesspoint'
(facepalm)
Me: I'm sorry, 'accesspoint' != 'Accesspoint'
FreeBSD: :P
FreeBSD: I don't see SSID 'accesspoint'
(disable encryption)
Me: Connect to SSID 'accesspoint' without a password
FreeBSD: I don't know what you're talking about
(connect with another computer)
Me: It's there, the Mac can see it
FreeBSD: I don't care if we're related, I'm not the Mac and I don't know what you're talking about
(verify the access point is in b/g mode)
Me: O'kay fine, connect to the first thing you see
FreeBSD: Connected to SSID 'Accesspoint'
(facepalm)
Me: I'm sorry, 'accesspoint' != 'Accesspoint'
FreeBSD: :P
The internet the way it should be
The following was posted on my blog at Sony's Gamer Advisory Panel website on August 26th of last year. I was told by someone that I should post it elsewhere. So here it is in its original form.
I just finished changing some settings on my router in an effort to make more effective use of my bandwidth when my son and I are both playing our respective games of choice. So, as I do after every change to my home network I fired up the PS3 connection test and made sure that it was still working properly. As I did I started to think about what I was looking at, and what it really meant.
In particular, I was looking at the result of the UPnP and NAT Type tests. They came up as 'Available' and 'Type 2' respectively. Both what I expected to see, and so everything is just fine. Except it isn't. Why is the PS3 even running these tests? Why does it care? Why, over 10 years after IPv6 was defined, are we still living under the limitations of IPv4?
For those of you that don't know, the current version of the numbering and routing system that the internet as we know it runs on is but a few short years from being totally out of addresses to hand out. We would have already run out if not for things such as NAT (Network Address Translation) which allows a single IP address to service a much larger number of systems, with some limitations. Not the least of which is that there is no trivial way to allow systems 'on the outside' to contact one of your systems. That brings me back to UPnP.
UPnP (Univeral Plug and Play) allows another device to configure a NAT router to allow outside connections into a specific address and port for a specific reason (as well as many other nifty and happy things). Until UPnP came along if you wanted to host a game that your friend in another part of the world (or down the street) could play in you had to login to your router, and with sometimes almost intimate knowledge of how the game communicated, configure the router to forward communications to your PC/Game console. Often times this required a lot more knowledge about the router than most people had, and many times the router didn't support it properly anyway. The only other option was to directly connect to the internet, which meant that anyone else trying to use the connection in your home was now quite out of luck.
UPnP to the rescue, yes? Sort of. Sure, new devices and new software are released with support out of the box, but it's an imperfect solution and most certainly not a fix just a tool to prolong the inevitable. Also, it has no way to authenticate the program making the request, so it is possible to use it to remove the pseudo-security that a NAT router provides. IP version 6 to the rescue? It could. With an address space so large that you could easily give an address to every person on the planet so many times over that you would lose count, everything could have it's own publicly routable, worldwide addressable, place on the net. No more worries about how to talk to another device, you just do it. Like things used to be, when the net was new, and tumbleweed was all around... or was that Gunsmoke?
Anyway, where was I? Oh yes, IPv6. Where is it? Why isn't it here? When will it be? I don't know. By now we should be well on our way to changing over to IPv6 only communications, with 4to6 gateways scattered around the net to allow the older devices and services to be accessed until they are replaced with the latest and greatest thing since sliced bread. The operating systems that most of us use on our computers are more than capable of making use of IPv6 right out of the box, or with only minor settings changes. Windows XP just requires turning it on, and it's on and ready to go in Vista as soon as you turn it on. Even Windows 2000 can make use of it with a download from Microsoft's website (as of this post the link for it is dead). Mac OS has had it for a while now, and it is on by default since OS X 10.3. Our Linux and BSD using brothers and sisters have also had it for a while (some longer than others). So why aren't we using it? Because there is no connection available. No one wants to start the ball rolling, or more I should say those that are doing so are in a very small, very exclusive group, and they can only do but so much.
I'm sitting on my bed, using an old Gateway laptop running FreeBSD and connected to my Mac via SSH over an IPv6 connection to prepare this. I listen to live streaming radio from the UK over an IPv6 connection within iTunes. I watch video from around the world, listen to trance and trip-hop from Germany, communicate via IRC with people all over the world all over an IPv6 connection. No thanks to my ISP, but thanks to a small group of people out of Switzerland, and others like them who offer cheap, or free IPv6 tunnels over people's existing IPv4 connections so they can start taking advantage of the still limited resources that are out there.
Limited resources, that's the problem. There is no killer app, no holy grail that will bring the masses in line and make the IPv6 gods shine their love down upon us; but that killer app is there, just waiting. It's sitting next to your TV, beside your VCR, on your kid's dresser. Your game console. Your PS3/360/Wii/etc. There it is, just waiting for unrestricted anywhere to anywhere communications. It wants to let you host a game to people all over the planet. It wants to tune into an internet radio station hosted by one lone guy in his basement along with hundreds, or even thousands of other people while lone basement guy only sends out one stream because you all just subscribe to that one stream. It wants to make a multi-person video conference call with your sister in California, your aunt in Mexico, and your best friend forever that just moved to Australia without any of you having to know anything at all about how it works or worrying about if your NAT device will allow the connection through.
If your console had those features, if you knew it, and knew how much easier it would be to host a server, or make that video call... if everyone had it and knew they had it. Knew what it could do, what it could mean. Then the connection providers (not just your ISP, but your ISP's ISP, and so forth) would have to give it to you, or someone else would. If you could take your laptop out on the road and still had full access to all of your resources at home, not because you knew how to set up a VPN, but because the underlying network just knew how to do it (and mobile IPv6 does) you're ISP would have to give it to you, or someone else would.
Why does your console not have that ability? Why doesn't it get an IPv6 address if one is available? Why doesn't it use Teredo (a zero-configuration tunneling protocol that can, under the right conditions, give a single machine behind a NAT an IPv6 address without the user having to know, or do anything) when a routable IPv6 address isn't available? That question I pose to Sony, to Microsoft, to Nintendo. Sony, remote play is great, being able to access my PS3 from my PSP... but think about how much easier it would be, and how much more useful it could be, if you didn't have to punch a hole through a router, if the router will even let you? Microsoft, your pride and joy (and the bane of technical support reps everywhere) Vista is all ready and revved up to go, why isn't your game console? Oh, and Apple, why doesn't that shiny new iPhone I just bought understand IPv6 when your desktop OS has for years? Cox, Time Warner, Charter, why aren't you already using it? Comcast, why are you only deploying it for internal CMTS to cable modem use? Why does your own IPv6 deployment strategy explicitly say "Deploy IPv6 only where it is absolutely necessary, and nowhere else!" Verizon, Quest, Earthlink, and other DSL providers, why aren't you using this as a selling point over cable, which has you beat in speed in most areas so badly that it's not even funny anymore?
Why?
Why is no one willing to take the first step? Why are we waiting until it's too late; until there becomes an IP black market of sorts? Why are we going to wait until end users don't have public IPs anymore, and their games don't work because their console is behind two, or more NAT devices? Did we not learn anything from the Y2K issue? We waited and waited, and it was almost too late when we did anything. It cost billions to fix, and we knew it was a problem when it was created. IPv4 was never intended to be a production network protocol, it was just a case study that got let loose into the wild, but we've had the solution for a very long time yet we do nothing. Sure, Japan and China are going a long way, but it's still mostly just academic networks that use it. Sure the US government made it mandatory for their networks to be IPv6 capable by June of this year, and they did, but never said anyone had to actually use it.
So here we are, looking at 2010-2011 (some even think 2009) as the end of the available IPv4 address pool, but we sit on our collective butts and wait for the other guy to go first. Two things drive technology. Two things always have. Entertainment and sex. So to The Great IPv6 Experiment I say godspeed to you, and to the gaming and mobile device makers I say, what are you waiting for? If not you, who, if not now, when? Soon your customers will not be able to use your products; why wait until it's too late, do something now.
I just finished changing some settings on my router in an effort to make more effective use of my bandwidth when my son and I are both playing our respective games of choice. So, as I do after every change to my home network I fired up the PS3 connection test and made sure that it was still working properly. As I did I started to think about what I was looking at, and what it really meant.
In particular, I was looking at the result of the UPnP and NAT Type tests. They came up as 'Available' and 'Type 2' respectively. Both what I expected to see, and so everything is just fine. Except it isn't. Why is the PS3 even running these tests? Why does it care? Why, over 10 years after IPv6 was defined, are we still living under the limitations of IPv4?
For those of you that don't know, the current version of the numbering and routing system that the internet as we know it runs on is but a few short years from being totally out of addresses to hand out. We would have already run out if not for things such as NAT (Network Address Translation) which allows a single IP address to service a much larger number of systems, with some limitations. Not the least of which is that there is no trivial way to allow systems 'on the outside' to contact one of your systems. That brings me back to UPnP.
UPnP (Univeral Plug and Play) allows another device to configure a NAT router to allow outside connections into a specific address and port for a specific reason (as well as many other nifty and happy things). Until UPnP came along if you wanted to host a game that your friend in another part of the world (or down the street) could play in you had to login to your router, and with sometimes almost intimate knowledge of how the game communicated, configure the router to forward communications to your PC/Game console. Often times this required a lot more knowledge about the router than most people had, and many times the router didn't support it properly anyway. The only other option was to directly connect to the internet, which meant that anyone else trying to use the connection in your home was now quite out of luck.
UPnP to the rescue, yes? Sort of. Sure, new devices and new software are released with support out of the box, but it's an imperfect solution and most certainly not a fix just a tool to prolong the inevitable. Also, it has no way to authenticate the program making the request, so it is possible to use it to remove the pseudo-security that a NAT router provides. IP version 6 to the rescue? It could. With an address space so large that you could easily give an address to every person on the planet so many times over that you would lose count, everything could have it's own publicly routable, worldwide addressable, place on the net. No more worries about how to talk to another device, you just do it. Like things used to be, when the net was new, and tumbleweed was all around... or was that Gunsmoke?
Anyway, where was I? Oh yes, IPv6. Where is it? Why isn't it here? When will it be? I don't know. By now we should be well on our way to changing over to IPv6 only communications, with 4to6 gateways scattered around the net to allow the older devices and services to be accessed until they are replaced with the latest and greatest thing since sliced bread. The operating systems that most of us use on our computers are more than capable of making use of IPv6 right out of the box, or with only minor settings changes. Windows XP just requires turning it on, and it's on and ready to go in Vista as soon as you turn it on. Even Windows 2000 can make use of it with a download from Microsoft's website (as of this post the link for it is dead). Mac OS has had it for a while now, and it is on by default since OS X 10.3. Our Linux and BSD using brothers and sisters have also had it for a while (some longer than others). So why aren't we using it? Because there is no connection available. No one wants to start the ball rolling, or more I should say those that are doing so are in a very small, very exclusive group, and they can only do but so much.
I'm sitting on my bed, using an old Gateway laptop running FreeBSD and connected to my Mac via SSH over an IPv6 connection to prepare this. I listen to live streaming radio from the UK over an IPv6 connection within iTunes. I watch video from around the world, listen to trance and trip-hop from Germany, communicate via IRC with people all over the world all over an IPv6 connection. No thanks to my ISP, but thanks to a small group of people out of Switzerland, and others like them who offer cheap, or free IPv6 tunnels over people's existing IPv4 connections so they can start taking advantage of the still limited resources that are out there.
Limited resources, that's the problem. There is no killer app, no holy grail that will bring the masses in line and make the IPv6 gods shine their love down upon us; but that killer app is there, just waiting. It's sitting next to your TV, beside your VCR, on your kid's dresser. Your game console. Your PS3/360/Wii/etc. There it is, just waiting for unrestricted anywhere to anywhere communications. It wants to let you host a game to people all over the planet. It wants to tune into an internet radio station hosted by one lone guy in his basement along with hundreds, or even thousands of other people while lone basement guy only sends out one stream because you all just subscribe to that one stream. It wants to make a multi-person video conference call with your sister in California, your aunt in Mexico, and your best friend forever that just moved to Australia without any of you having to know anything at all about how it works or worrying about if your NAT device will allow the connection through.
If your console had those features, if you knew it, and knew how much easier it would be to host a server, or make that video call... if everyone had it and knew they had it. Knew what it could do, what it could mean. Then the connection providers (not just your ISP, but your ISP's ISP, and so forth) would have to give it to you, or someone else would. If you could take your laptop out on the road and still had full access to all of your resources at home, not because you knew how to set up a VPN, but because the underlying network just knew how to do it (and mobile IPv6 does) you're ISP would have to give it to you, or someone else would.
Why does your console not have that ability? Why doesn't it get an IPv6 address if one is available? Why doesn't it use Teredo (a zero-configuration tunneling protocol that can, under the right conditions, give a single machine behind a NAT an IPv6 address without the user having to know, or do anything) when a routable IPv6 address isn't available? That question I pose to Sony, to Microsoft, to Nintendo. Sony, remote play is great, being able to access my PS3 from my PSP... but think about how much easier it would be, and how much more useful it could be, if you didn't have to punch a hole through a router, if the router will even let you? Microsoft, your pride and joy (and the bane of technical support reps everywhere) Vista is all ready and revved up to go, why isn't your game console? Oh, and Apple, why doesn't that shiny new iPhone I just bought understand IPv6 when your desktop OS has for years? Cox, Time Warner, Charter, why aren't you already using it? Comcast, why are you only deploying it for internal CMTS to cable modem use? Why does your own IPv6 deployment strategy explicitly say "Deploy IPv6 only where it is absolutely necessary, and nowhere else!" Verizon, Quest, Earthlink, and other DSL providers, why aren't you using this as a selling point over cable, which has you beat in speed in most areas so badly that it's not even funny anymore?
Why?
Why is no one willing to take the first step? Why are we waiting until it's too late; until there becomes an IP black market of sorts? Why are we going to wait until end users don't have public IPs anymore, and their games don't work because their console is behind two, or more NAT devices? Did we not learn anything from the Y2K issue? We waited and waited, and it was almost too late when we did anything. It cost billions to fix, and we knew it was a problem when it was created. IPv4 was never intended to be a production network protocol, it was just a case study that got let loose into the wild, but we've had the solution for a very long time yet we do nothing. Sure, Japan and China are going a long way, but it's still mostly just academic networks that use it. Sure the US government made it mandatory for their networks to be IPv6 capable by June of this year, and they did, but never said anyone had to actually use it.
So here we are, looking at 2010-2011 (some even think 2009) as the end of the available IPv4 address pool, but we sit on our collective butts and wait for the other guy to go first. Two things drive technology. Two things always have. Entertainment and sex. So to The Great IPv6 Experiment I say godspeed to you, and to the gaming and mobile device makers I say, what are you waiting for? If not you, who, if not now, when? Soon your customers will not be able to use your products; why wait until it's too late, do something now.
Speed is Beautiful
I get sidetracked easily. I don't think I suffer from attention deficit disorder, but I do have a tendency to go off on a tangent and end up somewhere totally different than where I started.
I had already planned out what my first 'real post' was going to be about. I had already decided that I was going to take my system status application of choice (which isn't really a system status application in and of itself) and do a write-up on its use and how I use it specifically. I still fully intend on doing that, but that will have to wait a little while.
'Real post' number one is about starting to change the house's network from a mix of 10/100Mb and 802.11b/g networking to 1Gb and having a separate b and g access point. Speed is not actually where this project started, though it's a nice side effect.
So why do it? The core of the house network is in a bedroom, which as anyone with more than a few computers will likely know, is a very inconvenient place for the core of a network to be. Power in that room isn't overly reliable and it's occupied by a 14-year old whose internet access is restricted at the router, giving him easy physical access to it. As anyone who deals with security knows, physical access negates security as router reset buttons negate passwords. Sure I could probably disable the reset button, but that's a lot of hassle and doesn't solve the location problem. So into the basement office, everything will go.
Since I have to pull new coax for the modem and will have to pull at least one new line to link the aforementioned 14-year old's room, I might as well just do the whole house. This also gives me the excuse to reroute the coax that I pulled earlier this year up into the walls and set up proper outlets for everything. I will likely pull at least one, maybe two, ethernet jack as well as one coax, and one phone jack per room. The phone brings up a whole different possibility with new hardware and such. One thing at a time, though.
For now, the promise of faster media streaming, and less wireless clutter is very appealing to me.
I had already planned out what my first 'real post' was going to be about. I had already decided that I was going to take my system status application of choice (which isn't really a system status application in and of itself) and do a write-up on its use and how I use it specifically. I still fully intend on doing that, but that will have to wait a little while.
'Real post' number one is about starting to change the house's network from a mix of 10/100Mb and 802.11b/g networking to 1Gb and having a separate b and g access point. Speed is not actually where this project started, though it's a nice side effect.
So why do it? The core of the house network is in a bedroom, which as anyone with more than a few computers will likely know, is a very inconvenient place for the core of a network to be. Power in that room isn't overly reliable and it's occupied by a 14-year old whose internet access is restricted at the router, giving him easy physical access to it. As anyone who deals with security knows, physical access negates security as router reset buttons negate passwords. Sure I could probably disable the reset button, but that's a lot of hassle and doesn't solve the location problem. So into the basement office, everything will go.
Since I have to pull new coax for the modem and will have to pull at least one new line to link the aforementioned 14-year old's room, I might as well just do the whole house. This also gives me the excuse to reroute the coax that I pulled earlier this year up into the walls and set up proper outlets for everything. I will likely pull at least one, maybe two, ethernet jack as well as one coax, and one phone jack per room. The phone brings up a whole different possibility with new hardware and such. One thing at a time, though.
For now, the promise of faster media streaming, and less wireless clutter is very appealing to me.
Reviewing my roots (aka: don't login as root)
This entry was originally the inaugural post to this blog before I merged an older personal blog into it. I'm leaving the post intact, below:
I've been thinking about this for a while but a few things that have changed in my daily routine have made me decide to stop thinking and start doing. So without my usual (hence the name of this blog) ramblings, on with the show.
My personal blog has started to take a somewhat technical bent as of late. As such, I've decided to branch out and keep things separate (more or less). Here I plan to spout off about things of the geek nature which just so happen to be tickling my fancy, yanking my chain, or otherwise getting in my face. I make no promise to release schedules, nor that my personal life won't end up here. After all, I'm a geek at heart, so keeping my personal life out of it all together will be hard.
Why should you read, why should you care? Hell if I know but I'll tell you a little about who I am; you can decide for yourself after that.
I'm a thirty-something geek of all trades (master of none) with a particular bent towards audio/video. My formal education spans classic arts (drawing, painting, clay sculpture), music (violin and piano), electronics, graphics arts (photography, print layout), radio and television broadcasting, as well as network management (back in the Netware days w/thinnet weee!), business application programming (C, COBOL, RPG, Clipper, Visual Basic), and a little general expert system development for taste. After school I started my training in taming the beast that is FreeBSD since 2.2.6, Linux still makes me cringe, Windows has its place (but I still think MSDOS 5.5 was the last decent OS Microsoft ever made, so long as you were running DESQview), and spend most of my time now in OS X. I'm no Apple fanboy but I do own an iPhone (in the interest of full disclosure).
Can't call me a 'gamer' but I do own a PS3. Don't really enjoy PC gaming as a whole but I do keep a WinXP partition on my Mac specifically to play Evil Genius. Read into that what you will. In fact, I'm not sure that any of the commonly accepted subclasses of geek really apply properly to me. All in all, I'm just me... an elder-n00b. For those that chose to check in on me from time to time, I'll be putting my own spin on life, tech, and the way they come together.
I've been thinking about this for a while but a few things that have changed in my daily routine have made me decide to stop thinking and start doing. So without my usual (hence the name of this blog) ramblings, on with the show.
My personal blog has started to take a somewhat technical bent as of late. As such, I've decided to branch out and keep things separate (more or less). Here I plan to spout off about things of the geek nature which just so happen to be tickling my fancy, yanking my chain, or otherwise getting in my face. I make no promise to release schedules, nor that my personal life won't end up here. After all, I'm a geek at heart, so keeping my personal life out of it all together will be hard.
Why should you read, why should you care? Hell if I know but I'll tell you a little about who I am; you can decide for yourself after that.
I'm a thirty-something geek of all trades (master of none) with a particular bent towards audio/video. My formal education spans classic arts (drawing, painting, clay sculpture), music (violin and piano), electronics, graphics arts (photography, print layout), radio and television broadcasting, as well as network management (back in the Netware days w/thinnet weee!), business application programming (C, COBOL, RPG, Clipper, Visual Basic), and a little general expert system development for taste. After school I started my training in taming the beast that is FreeBSD since 2.2.6, Linux still makes me cringe, Windows has its place (but I still think MSDOS 5.5 was the last decent OS Microsoft ever made, so long as you were running DESQview), and spend most of my time now in OS X. I'm no Apple fanboy but I do own an iPhone (in the interest of full disclosure).
Can't call me a 'gamer' but I do own a PS3. Don't really enjoy PC gaming as a whole but I do keep a WinXP partition on my Mac specifically to play Evil Genius. Read into that what you will. In fact, I'm not sure that any of the commonly accepted subclasses of geek really apply properly to me. All in all, I'm just me... an elder-n00b. For those that chose to check in on me from time to time, I'll be putting my own spin on life, tech, and the way they come together.
(mis)adventures in networking
To further my quest to see just how much I can make my poor old FreeBSD box do without falling over I have setup (and mostly have working) both PPTP VPN and Samba as a WINS server. Now the end goal is to make it so that connecting clients will be able to browse the shared drives/printers on the network, but so far only direct reference seems to be working. Not sure what I'm doing wrong but then it might just be a limitation of the built-in Mac OS X VPN client.
The only reason I set up Samba, really, was that supposedly having a WINS server would allow the browsing to happen but so far that doesn't seem to be cutting it. Though since I have it up I might try messing with LDAP based login authentication again. *shrug* Had it working once before for the BSD and Windows machines I had on the network but it's a bigger network now and I would be causing a possible issue for people that don't really need that kind of thing, so maybe not.
If anyone has any thoughts on what I might be doing wrong with the VPN and share browsing, do feel free to pipe up.
Also, I want to be able to route IPv6 traffic over the connection but I haven't even gotten rtadvd to send over the VPN connections yet, so that's a project for another day.
Why can't I have a normal hobby, like everyone else? No, wait, most of the people I talk to do networking for a hobby. Never mind. :)
The only reason I set up Samba, really, was that supposedly having a WINS server would allow the browsing to happen but so far that doesn't seem to be cutting it. Though since I have it up I might try messing with LDAP based login authentication again. *shrug* Had it working once before for the BSD and Windows machines I had on the network but it's a bigger network now and I would be causing a possible issue for people that don't really need that kind of thing, so maybe not.
If anyone has any thoughts on what I might be doing wrong with the VPN and share browsing, do feel free to pipe up.
Also, I want to be able to route IPv6 traffic over the connection but I haven't even gotten rtadvd to send over the VPN connections yet, so that's a project for another day.
Why can't I have a normal hobby, like everyone else? No, wait, most of the people I talk to do networking for a hobby. Never mind. :)
A computer by any other IP...
Finished a network renumber tonight. Why? In preparation for another project that I'll be starting soon.
After a few minor hiccups (forgetting to update the default gateway in the dhcpd.conf is minor, right?) everything is back to normal. Actually fixed a few things along the way. Lease file is filling up with new info and all seems to be right with the world again.
After a few minor hiccups (forgetting to update the default gateway in the dhcpd.conf is minor, right?) everything is back to normal. Actually fixed a few things along the way. Lease file is filling up with new info and all seems to be right with the world again.
128 bits, all in a row, looking for which way to go
Well after a few brain melting days of rereading on routing and subnets and all that I asked a straightforward question, got given the most polite RTFM in my life and well I did, again, and somehow this time it made sense.
My poor lone IPv6 tunnel is now hosting my happy little subnet. I still have some tinkering to do to work out security on the FreeBSD machine that is acting as the router and then there's the whole idea of using DHCP to assign specific IPs, and don't even get me started on reverse DNS. It's working; so far I've verified one XP machine and one OS X machine, the others should work too I would think, but we'll see. For now, I have the two machines I really care about working correctly working, the rest I don't use and so they can get done as time allows.
I feel better; this was really kicking my ass, and I'm glad that I finally beat it.
It's been way too long since I've done this kind of thing, I'm out of practice.
My poor lone IPv6 tunnel is now hosting my happy little subnet. I still have some tinkering to do to work out security on the FreeBSD machine that is acting as the router and then there's the whole idea of using DHCP to assign specific IPs, and don't even get me started on reverse DNS. It's working; so far I've verified one XP machine and one OS X machine, the others should work too I would think, but we'll see. For now, I have the two machines I really care about working correctly working, the rest I don't use and so they can get done as time allows.
I feel better; this was really kicking my ass, and I'm glad that I finally beat it.
It's been way too long since I've done this kind of thing, I'm out of practice.
Double your address length, double your fun...
To continue my geek-fest I now have a working IPv6 address and a tunnel to use it with. The end goal is to have every capable machine in the house on the tunnel, but one thing at a time. Right?
Why? I don't know, I've just been doing things lately with this 'out of nowhere' drive. Unlike usual when I get in the mood to do something lately I've been doing the hell out of it, instead of my usual good enough is good enough way of doing things.
I don't know why but I've got a nifty new toy to play with, and found someone that I haven't talked to in 10 years so far. We'll see what comes next.
For now, it's bedtime I think.
Nighty night peoples.
p.s. Yes, I know it's actually 4x longer, but that just wouldn't have sounded as good.
Why? I don't know, I've just been doing things lately with this 'out of nowhere' drive. Unlike usual when I get in the mood to do something lately I've been doing the hell out of it, instead of my usual good enough is good enough way of doing things.
I don't know why but I've got a nifty new toy to play with, and found someone that I haven't talked to in 10 years so far. We'll see what comes next.
For now, it's bedtime I think.
Nighty night peoples.
p.s. Yes, I know it's actually 4x longer, but that just wouldn't have sounded as good.
Gotta love Mondays
Got up this morning to find out that I got a little carried away Sunday with Kathryn's upgrade (Kathryn is my local mail/DNS/DHCP/etc server) and overwrote the named.conf file... so I kinda broke local resolving. Now I usually have a pretty good memory when it comes to technical things, but first thing in the morning, when I'm still trying to focus on things more than a few inches in front of me, it's a little hard to remember what goes where in a file I've only looked at while I was making it.
Went back to bed after I got that working, then overslept and didn't get to take a shower before work. The manager was being a raving psycho today... wonder what mood she'll be sporting tomorrow, or if it'll be one of those "new mood every five minutes" days.
Now it's an hour into Tuesday, and I need to be getting to bed. Better luck tomorrow eh?
Went back to bed after I got that working, then overslept and didn't get to take a shower before work. The manager was being a raving psycho today... wonder what mood she'll be sporting tomorrow, or if it'll be one of those "new mood every five minutes" days.
Now it's an hour into Tuesday, and I need to be getting to bed. Better luck tomorrow eh?
Subscribe to:
Posts (Atom)