Archive for the 'Unix' Category

11/08/2007

Well, the upgrade to Mac OS X Leopard went smoothly, as Wooley predicted in his comment on my previous post.

The whole upgrade took about an hour and 15 minutes (which included verifying the install DVD) on my MacBook. I now am running the latest and greatest version of Apple’s OS, a certified flavor of UNIX, and am, so far, extremely impressed. The dock is beautiful, Stacks look extremely useful and efficient, there are a lot of desktop customizable features, Spaces (which I am looking forward to setting up soon), and more.

I look forward to getting a bit more intimate better acquainted with Leopard in the upcoming days and months. Anyway, the upgrade went smoothly. If you’re scared, don’t be. Mine was a breeze! I just wish I had upgraded the day this package arrived on my doorstep…

uname Output:

% uname -a
Darwin xbook 9.0.0 Darwin Kernel Version 9.0.0: Tue Oct 9 21:35:55 PDT 2007; root:xnu-1228~1/RELEASE_I386 i386

Until next time…

07/17/2007

I am working on a SUSE Enterprise Linux Server 10 server today and I have no experience with Novell’s flavor of Linux at all. But, that’s wht Google was created… Google allows admins and non-admins to “fake it till you make it”. And, that, ladies and gentlemen, is exactly what I have done today while working with this SUSE box.

So, my task was to get the box booted up, setup the network configuration, and then turn it back over to another department who will get with the vendor working with this server to complete the configuration. I have setup network configurations in FreeBSD, Red Hat Linux (way back in the day), AIX, Solaris (again, way back in the day), and obviously Windows and Mac OS X. But, I had no idea where SUSE stored it’s network configuration files or what the file format was for setting up the network parameters until today.

I am posting this information for two reasons: 1.) I may need this again someday, and 2.) hopefully it will help someone else out who is just entering into the SUSE arena. Here is what I found out during my research:

The files necessary to setup my network configuration were located in /etc/sysconfig/network. Within this directory are different ifcfg-<interface_name> files, obviously, one for each interface in the machine. Now, most Linux fans would assume that since there was a ifcfg-lo file in this directory for the local loopback interface that there would need to be a ifcfg-eth0 file for the eth0 interface. Well, not so… I don’t guess.

My config file for eth0 was labeled ifcfg-eth-id-00:00:00:00:00:00 where 00:00:00:00:00:00 is the MAC address of the interface I wanted to configure. Since I wanted to create a static configuration, not a DHCP assigned address, I put the following contents in my ifcfg-eth-id-00:00:00:00:00:00 configuration file, again, located within /etc/sysconfig/network:

BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='xxx.xxx.xxx.xxx'
MTU=''
NAME='Descriptive Name for Interface'
NETMASK='xxx.xxx.xxx.xxx'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
UNIQUE='<random_stuff_it_appears_maybe_not>'
USERCONTROL='no'
_nm_name='bus-pci-000:01:00.0'

Obviously, you’ll need to set IPADDR to the IP address you want to use for your box/server. The NETMASK also needs to be set correctly. I’m not really sure what the UNIQUE variable is or how it is computed. Maybe someone else can shed some light on this one. And, it appears that the _nm_name is the actual hardware address to your NIC. Again, maybe someone can help me out with the variable as well.

So, once I had that file configured the way I wanted, it was time to set my default route. This was extremely simple. All I had to do was create a file with a name similar to the configuration file we just modified, but instead of using ifcfg-* I used ifroute-*. So, my route configuration file for my eth0 interface was named ifroute-eth-id-00:00:00:00:00:00. Obviously you will need to replace the 00:00:00... with your actual MAC address. Inside the file I put one line and all of my problems were solved. I entered:

default xxx.xxx.xxx.xxx

Make sure you replace xxx.xxx.xxx.xxx with the actual IP address of your network’s gateway. Also, that is a between the word default and the gateway’s IP address.

Once these files were created/modified, I rebooted the server, logged on, and was able to access network resources like it was nobody’s business.

Until next time…

03/11/2007

First of all, let me just ask, is it 11:54PM or 10:54PM… My mind and body can’t tell. The time change last night appears to have taken place already on all of my physical clocks, computers, etc., but my mind hasn’t really caught on yet. Just to be safe I have ironed my clothes for tomorrow and have already shaved my head and face. I don’t expect that my alarm going off at 6:35AM (5:35AM “my time”) tomorrow morning will have a very nice effect on me and I just might get up a little late… We’ll see.

I should also let everyone know (you know who all 3.234 of you are) that I didn’t ever get around to creating my giant poster (or was it a huge poster?) this weekend. I ended up doing some things around the house, working on a couple of projects for FS, and went to work today with Chris.

Read the rest of this entry »

02/26/2007

When I first started getting in to using FreeBSD I bought a shirt to support my latest habit interest. I quickly got involved with FreeBSD and loved every minute of using the operating system. I figured I liked it enough to purchase a shirt to support my newly found robust and free operating system. I really owe more to the FreeBSD Foundation for turning me on to and causing me to use Mac OS X.

I bought and received this shirt either at the end of 2005 or early 2006. Guess what?! I have never wore it. This past Saturday night I was going to WalMart and figured I would wear it there. I mean, why not?! Freak out all those late evening shoppers with the shirt. They were probably like: “FreeBSD? What’s that?! And why is there a picture of a devil on his shirt?! That boy needs to go to church!”

Well, luckily for me, some friends called me up to join them at El Chico’s for dinner. I got to sport my shirt out in public twice in one day! Nice! I even got a comment from someone who actually knew what FreeBSD was, Troy. So, I sported my new shirt at a mexican restaraunt and had a great time (just ask Troy!).

Anyway, here are some photos of me sporting the FreeBSD shirt. I like it. It looks good. Has a couple of images of the FreeBSD mascot on it, Beastie. I’m going to break out this shirt more often now that it has been initialized!

Read the rest of this entry »

02/12/2007

This evening I decided to install some applications I used on FreeBSD before I got my Apple MacBook. I used to thoroughly enjoy the FreeBSD ports system for maintaining 3rd-party applications like Wireshark (formerly known as Ethereal) and Nmap. Since moving to Mac I have found a similar ports system named MacPorts, formerly known as DarwinPorts.

I have used the MacPorts system in the past to install the above mentioned applications, Wireshark and Nmap, as well as screen (great tutorial on TechSays, previously posted at averageadmins.com) and Ettercap. I got crazy with the MacPorts tonight and started installing some of the software that I used to use on my FreeBSD laptop as well as some newer applications I wanted to try out. I installed:

I like messing around with security and network monitoring software, especially when Chris gets involved and we mess around with different tools trying to figure out how they work and how we can use them. I am sure I will think of more applications to install in the near future.

I want to get my MacBook ready for when Chris and I have to go do some network monitoring at a remote branch or something like we did back in the day with his Debian laptop and my FreeBSD laptop. I just need to remember that the MacPorts port system is there for me and always willing to help me install and maintain 3rd-party applications.

Until next time…

2007-02-13 - Correction: I didn’t install Nikto using the MacPorts repository as stated above. I installed it from source. It’s a Perl script with functionality that I already get from Nessus so I removed it from my system and will continue to use Nessus for web site vulnerability testing.

 

Categories