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
Showing posts with label FreeBSD. Show all posts
Showing posts with label FreeBSD. Show all posts
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.
IP Renumbering w/PHP and Compilers.
In episode 424 of Hak5 a viewer question led to Darren and Matt discussing renumbering a whole subnet of Windows machines using the netsh command in a script, but how would you specify an IP for each machine with only one script? PHP to the rescue, because it's not just for web pages anymore.
On this week's episode of Hak5, I show off a script to do just that, as well as two different PHP runtime compilers.
Since most Windows workstations don't have PHP installed a compiler will let you prepare your code to run on systems that don't have PHP installed.
First, we have Roadsend PHP, which is available for Linux, FreeBSD, Mac OS X and Microsoft Windows. It's released under GNU GPL, and it's runtime libraries are GNU LGPL so compiled programs may be used for both open source and commercial projects.
Roadsend PHP is not just to package up your PHP into nice friendly bundles, it comes with Roadsend Studio, a full development environment (IDE) with support for the Glade interface builder (*nix/Win32), to give your PHP a GUI front end.
It supports PHP 4 and 5, and so far all the code I've compiled with it runs just as it would if launched from the command line using the PHP command. The only drawback to it is the compile process seems to take a while even on relatively small projects, and the file sizes are a little large (simple scripts weighing in at over 3MB), but if you want to stay in one environment from start to finish Roadsend will do the job.
Second is the Bambalam PHP EXE Compiler/Embedder, which as the name implies is for Windows only. Like Roadsend PHP, Bambalam PHP is free to use as it's released under the PHP license, generates code that will run without a full PHP install, and with the use of the WindBinder library can produce programs with GUI front ends. That is about where the similarities end.
Bambalam is small, consisting of a hand full of files, and is only for the actual building of the executable code. Bring your own editor, debugger, GUI builder, and project manager. That's not what Bambalam is for. What it is for, though, is producing small, fast programs out of any PHP that will run under PHP 4.4.4. The same +3MB code that Roadsend produced came in at just over 1MB with Bambalam, and under 700KB with compression turned on.
The problem my code solves is how to write one script to renumber a whole group of machines without having to issue a different version of the script to each machine. As this is more of a proof of concept we will assume that only the last octet of the IP address will be changing.
The command is issued with the following options:
<New IP> <Subnet Mask> <Default Gateway> [DNS] [WINS]
The new IP is given as the first three octets in xxx.xxx.xxx format, subnet, and gateway will be a full four octets a piece. IP, DNS, and WINS can each be assigned as DHCP (using DHCP for IP precludes the need for subnet and gateway). DNS and WINS can also be assigned as NONE so long as IP is not DHCP. Furthermore, specifying WINS requires that some value is given for DNS.
If a new first three octets are given without specifying DNS or WINS and those values were already staticly assigned then the new first three octets will be used for those values as well. Also if IP is currently assigned via DHCP that can't be changed at this time.
The following code is my first attempt at PHP, and before writing this I had never even seen PHP code before. While comments and advice are welcome, keep that in mind.
iprenum.php
This code is released under the BSD license (two clauses), so feel free to use it as you see fit, just don't complain to me when it plots with your cat to take over the world.
Don't ask me how to deploy this script across a Windows network without physically accessing every machine, I don't do Windows. I have a feeling Darren has some thoughts on it, though.
On this week's episode of Hak5, I show off a script to do just that, as well as two different PHP runtime compilers.
Since most Windows workstations don't have PHP installed a compiler will let you prepare your code to run on systems that don't have PHP installed.
First, we have Roadsend PHP, which is available for Linux, FreeBSD, Mac OS X and Microsoft Windows. It's released under GNU GPL, and it's runtime libraries are GNU LGPL so compiled programs may be used for both open source and commercial projects.
Roadsend PHP is not just to package up your PHP into nice friendly bundles, it comes with Roadsend Studio, a full development environment (IDE) with support for the Glade interface builder (*nix/Win32), to give your PHP a GUI front end.
It supports PHP 4 and 5, and so far all the code I've compiled with it runs just as it would if launched from the command line using the PHP command. The only drawback to it is the compile process seems to take a while even on relatively small projects, and the file sizes are a little large (simple scripts weighing in at over 3MB), but if you want to stay in one environment from start to finish Roadsend will do the job.
Second is the Bambalam PHP EXE Compiler/Embedder, which as the name implies is for Windows only. Like Roadsend PHP, Bambalam PHP is free to use as it's released under the PHP license, generates code that will run without a full PHP install, and with the use of the WindBinder library can produce programs with GUI front ends. That is about where the similarities end.
Bambalam is small, consisting of a hand full of files, and is only for the actual building of the executable code. Bring your own editor, debugger, GUI builder, and project manager. That's not what Bambalam is for. What it is for, though, is producing small, fast programs out of any PHP that will run under PHP 4.4.4. The same +3MB code that Roadsend produced came in at just over 1MB with Bambalam, and under 700KB with compression turned on.
The problem my code solves is how to write one script to renumber a whole group of machines without having to issue a different version of the script to each machine. As this is more of a proof of concept we will assume that only the last octet of the IP address will be changing.
The command is issued with the following options:
<New IP> <Subnet Mask> <Default Gateway> [DNS] [WINS]
The new IP is given as the first three octets in xxx.xxx.xxx format, subnet, and gateway will be a full four octets a piece. IP, DNS, and WINS can each be assigned as DHCP (using DHCP for IP precludes the need for subnet and gateway). DNS and WINS can also be assigned as NONE so long as IP is not DHCP. Furthermore, specifying WINS requires that some value is given for DNS.
If a new first three octets are given without specifying DNS or WINS and those values were already staticly assigned then the new first three octets will be used for those values as well. Also if IP is currently assigned via DHCP that can't be changed at this time.
The following code is my first attempt at PHP, and before writing this I had never even seen PHP code before. While comments and advice are welcome, keep that in mind.
iprenum.php
This code is released under the BSD license (two clauses), so feel free to use it as you see fit, just don't complain to me when it plots with your cat to take over the world.
Don't ask me how to deploy this script across a Windows network without physically accessing every machine, I don't do Windows. I have a feeling Darren has some thoughts on it, though.
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.
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)