Modifying a FreeBSD release ISO for headless booting

Ok, here are the commands. I will come back later to add context, too many irons in the fire right this minute...

# mkdir /bigdisk/iso # mkdir /bigdisk/iso_headless # cd /bigdisk # fetch ftp://ftp7.us.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/7.2/7.2-RELEASE-i386-disc1.iso # mdconfig -a -t vnode -f /bigdisk/7.2-RELEASE-i386-disc1.iso -u 0 # mount -t cd9660 /dev/md0 /bigdisk/iso

No trailing slash on the rsync destination is significant. The following two commands are equivalent:

   rsync -av /bigdisk/iso/ /bigdisk/iso_headless
   rsync -av /bigdisk/iso/* /bigdisk/iso_headless/

# rsync -av /bigdisk/iso/ /bigdisk/iso_headless # umount /bigdisk/iso # mdconfig -d -u 0

Note that I did attempt the following, which failed:

   echo "/boot/loader -h" > /bigdisk/iso_headless/boot.config

# echo 'console="comconsole"' >> /bigdisk/iso_headless/boot/loader.conf # mkisofs -no-emul-boot -U -R -b boot/cdboot -o /bigdisk/7.2-RELEASE-i386-disc1_HEADLESS.iso /bigdisk/iso_headless # cdrecord -scanbus

Set whatever speed you want here. I had some cheap, old CDRs and they needed burn slowly. I have plenty to keep me busy while it's burning...

# cdrecord speed=2 dev=1,0,0 /bigdisk/7.2-RELEASE-i386-disc1_HEADLESS.iso

That's all for now, please enjoy responsibly.

Retrieve ARP table from Cisco router, parse, spew

I had a colleague in need of an automated way to retrieve the ARP table from a lot of Cisco routers and format the output in a spreadsheet. Another colleague suggested using an Expect script, which is definitely cool because I love using Expect (seriously, it's a Swiss Army knife), but I wanted to take it a different direction. I looked up the SNMP MIB to retrieve the ARP table and then parsed the input to provide a two-column output consisting of the IP address and MAC address, one pair per line.

Here is the script:

snmpwalk -t 60 -v 1 -c MYCOMMSTRING routerhostname .1.3.6.1.2.1.4.22.1.2 | \ while read line; do \ IP_ADDR=`echo ${line} | \ awk '{print $1;}' | \ sed -e 's/^IP-MIB::ipNetToMediaPhysAddress.[0-9]*\.//'`; \ MAC_ADDR=`echo ${line} | \ awk '{print $4;}' | \ sed -e 's/^\([0-9a-f]\)/0\1/' \ -e 's/:\([0-9a-f]\):/:0\1:/g' \ -e 's/:\([0-9a-f]\):/:0\1:/g' \ -e 's/:\([0-9a-f]\)$/:0\1/' | \ tr '[:lower:]' '[:upper:]'`; \ echo "${IP_ADDR} ${MAC_ADDR}"; \ done

Notice that there are two mid-string sed matches, each with a 'g' matching command. The reason that this command needs to be listed twice is that a single iteration of 'g' doesn't mean global, it means to match up to two addresses within the stream. Since some of the MAC addresses I was dealing with were beyond that, such as "0:d:ed:c:7:5e", just using a single mid-string pattern with 'g' left me with "00:0d:ed:0c:7:5e" (note the :7: instead of the desired :07:). Adding the second iteration of mid-string matching fixed this issue by enabling matching of a third and fourth mid-string single-digit. I learned something new about sed, and learning something new is a good thing.

FreeBSD 7.2 on my Samsung NC10-14GB

Everything working well so far. To get X working I read a lot of forums and ML archives. To get the 915resolution tool, from ports, working with the 945GME chipset in this netbook, I had to patch a couple of files...

# diff -ruN 915resolution.c.orig 915resolution.c --- 915resolution.c.orig 2009-08-08 22:51:00.000000000 +0000 +++ 915resolution.c 2009-08-08 22:53:44.000000000 +0000 @@ -57,12 +57,12 @@ typedef unsigned int cardinal; typedef enum { - CT_UNKWN, CT_830, CT_845G, CT_855GM, CT_865G, CT_915G, CT_915GM, CT_945G, CT_945GM, + CT_UNKWN, CT_830, CT_845G, CT_855GM, CT_865G, CT_915G, CT_915GM, CT_945G, CT_945GM, CT_945GME, CT_946GZ, CT_G965, CT_Q965 } chipset_type; char * chipset_type_names[] = { - "UNKNOWN", "830", "845G", "855GM", "865G", "915G", "915GM", "945G", "945GM", + "UNKNOWN", "830", "845G", "855GM", "865G", "915G", "915GM", "945G", "945GM", "945GME", "946GZ", "G965", "Q965" }; @@ -216,6 +216,10 @@ type = CT_945GM; break; + case 0x27ac8086: + type = CT_945GME; + break; + case 0x29708086: type = CT_946GZ; break; @@ -511,6 +515,7 @@ case CT_915GM: case CT_945G: case CT_945GM: + case CT_945GME: case CT_946GZ: case CT_G965: case CT_Q965: @@ -551,6 +556,7 @@ case CT_915GM: case CT_945G: case CT_945GM: + case CT_945GME: case CT_946GZ: case CT_G965: case CT_Q965: @@ -806,6 +812,9 @@ else if (!strcmp(argv[index], "945GM")) { *forced_chipset = CT_945GM; } + else if (!strcmp(argv[index], "945GME")) { + *forced_chipset = CT_945GME; + } else if (!strcmp(argv[index], "946GZ")) { *forced_chipset = CT_946GZ; }

...and this one...

# diff -ruN chipset_info.txt.orig chipset_info.txt --- chipset_info.txt.orig 2007-04-15 07:31:29.000000000 +0000 +++ chipset_info.txt 2009-08-08 22:53:59.000000000 +0000 @@ -7,3 +7,4 @@ 915PM, 915GM, 915GMS, 910GML $2590_8086 $91 - $92 945G $2770_8086 $91 - $92 945GM $27A0_8086 $91 - $92 +945GME $27AC_8086 $91 - $92

More to come later, but I will leave you with this:

# kldstat Id Refs Address Size Name 1 22 0xc0400000 9fab28 kernel 2 2 0xc0dfb000 4a64c sound.ko 3 1 0xc0e46000 1ae38 snd_hda.ko 4 1 0xc0e61000 802c ng_ubt.ko 5 6 0xc0e6a000 da08 netgraph.ko 6 1 0xc0e78000 6a45c acpi.ko 7 4 0xc5a80000 2000 ng_bluetooth.ko 8 1 0xc5a82000 d000 ng_hci.ko 9 1 0xc5aba000 f000 ng_l2cap.ko 10 1 0xc5acb000 1a000 ng_btsocket.ko 11 1 0xc5aed000 4000 ng_socket.ko 12 1 0xc5b39000 22000 linux.ko 13 1 0xc5e27000 9000 i915.ko 14 1 0xc5e30000 13000 drm.ko

Have fun!

Rant: There, fixed that for ya...

I am so sick and tired of people who think they are so clever to reply to someone else on a mailing list, EDITING SOMEONE ELSE'S WORDS, and then covering with the oh-so-bright "There, fixed that for you." comment. Hello jackass, why don't you form an intelligent reply and submit that to the list and refrain from editing quoted text from someone else. If I happen to jump straight into a message in some archive via a Google search or such and I see a quoted message then I don't REALLY know what the quoted message was if some super-smart guy decides to "fix" someone else's quote, do I?

Please, if you have taken up this bad habit, give some thought to quitting. It isn't nearly as witty as you believe it is.

FreeNAS 0.7.3953, RAID 1, growfs... oh my!

Fooling around in VMWare, preparing to build my two NAS boxen, I started playing with disk upgrade scenarios in a two-drive RAID 1 configuration. I have the embedded FreeNAS on /dev/ad0, and the two mirror disks are /dev/ad2 and /dev/ad3. First, I had them both at 512MB each, then bumped one to 1GB, fixed the mirror, then bumped the other to 1GB and fixed the mirror again. At this point, I had two 1GB disks with a 512MB (give or take) mirror since it was sized from the initial installation with two 512MB disks. Time to figure out growfs...

I tinkered around with growfs, finally got it to work, and ended up with a mirror to match the size (more or less) of the actual disks. Now, let's do it again to make sure it wasn't a fluke! I bumped one disk to 2GB, rebuilt the mirror, then bumped the other disk to 2GB, rebuilt mirror, thus leaving me with a pair of 2GB disks and a 1GB mirror. Then I followed the growfs process again and took some notes this time, here for your reading pleasure.

NOTE -- This worked for me and I make no guarantees, express or implied, that it will work for you. If you follow my instructions, you may come through this just fine, or you may not. Always back up your data before starting on something like this, and understand the commands you are using and what the impact is. If you can, play in a VM sandbox for a while until you are comfortable.


Notes

---

At this point, I shutdown the FreeNAS VM and replaced /dev/ad3, which was 1GB, with a 2GB disk to match /dev/ad2.

1. At the web gui, edit the /dev/ad3 disk and just click on 'Save' and the new size will be picked up automatically.

2. The raid is still degraded, as expected, so do the 'replace disk' dance...

• edit the raid1 array
• click on 'tools', then choose RAID1 (volume name) and command 'forget' and click on 'Send Command!'
• click on 'tools', then choose RAID1 (volume name), disk ad3, command 'insert', and click on 'Send Command!'
• go back to the raid1 management tab and the status should be COMPLETE once the mirror is rebuilt

3. The mount point should be in 'Error - Retry' state right now, so click on Retry to ensure that it mounts ok.

[root@freenas ~]# [root@freenas ~]# [root@freenas ~]# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 80430 74634 5796 93% / devfs 1 1 0 100% /dev /dev/md1 31470 12 28942 0% /var /dev/ad0a 39406 34216 5190 87% /cf /dev/mirror/RAID1p1 888526 69300 748144 8% /mnt/NAS1 [root@freenas ~]# [root@freenas ~]#

4. At this point, the mount is back online with the old 1GB mirror size, so let's get into the meat of it.

5. Go back to the mount point configuration and delete the mount point

6. Go to the raid management and delete the raid1 array

7. Add a new raid 1 array, which I will call RAID1, and choose 'create and initialize RAID' option, then click on 'Add'

8. Next, head to the beloved (for me, anyway) CLI via SSH and do the hardcore stuff...

[root@freenas ~]# [root@freenas ~]# [root@freenas ~]# mount /dev/md0 on / (ufs, local) devfs on /dev (devfs, local) /dev/md1 on /var (ufs, local, union) /dev/ad0a on /cf (ufs, local, read-only) [root@freenas ~]# [root@freenas ~]# [root@freenas ~]# [root@freenas ~]# [root@freenas ~]# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 80430 74612 5818 93% / devfs 1 1 0 100% /dev /dev/md1 31470 12 28942 0% /var /dev/ad0a 39406 34216 5190 87% /cf [root@freenas ~]# [root@freenas ~]# [root@freenas ~]# [root@freenas ~]# [root@freenas ~]# cd /dev/mirror [root@freenas /dev/mirror]# alias ls='ls -al' [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# ls total 1 dr-xr-xr-x 2 root wheel 512 Dec 16 16:40 . dr-xr-xr-x 5 root wheel 512 Dec 16 16:40 .. crw-r----- 1 root operator 0, 81 Dec 16 16:40 RAID1 crw-r----- 1 root operator 0, 85 Dec 16 16:40 RAID1p1 [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt remove -i 1 /dev/mirror/RAID1 gpt remove: /dev/mirror/RAID1: error: no secondary GPT header; run recover [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt recover /dev/mirror/RAID1 gpt recover: /dev/mirror/RAID1: recovered secondary GPT table from primary gpt recover: /dev/mirror/RAID1: recovered secondary GPT header from primary [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt show /dev/mirror/RAID1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 2097084 1 GPT part - FreeBSD UFS/UFS2 2097118 2097152 4194270 32 Sec GPT table 4194302 1 Sec GPT header [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt remove -i 1 /dev/mirror/RAID1 /dev/mirror/RAID1p1 removed [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt show /dev/mirror/RAID1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 4194236 4194270 32 Sec GPT table 4194302 1 Sec GPT header [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt add -i 1 -t ufs /dev/mirror/RAID1 [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt show /dev/mirror/RAID1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 4194236 1 GPT part - FreeBSD UFS/UFS2 4194270 32 Sec GPT table 4194302 1 Sec GPT header [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt show -l /dev/mirror/RAID1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 4194236 1 GPT part - "RAID1" 4194270 32 Sec GPT table 4194302 1 Sec GPT header [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt label -i 1 -l RAID1 /dev/mirror/RAID1 /dev/mirror/RAID1p1 labeled [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt show /dev/mirror/RAID1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 4194236 1 GPT part - FreeBSD UFS/UFS2 4194270 32 Sec GPT table 4194302 1 Sec GPT header [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# gpt show -l /dev/mirror/RAID1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 4194236 1 GPT part - "RAID1" 4194270 32 Sec GPT table 4194302 1 Sec GPT header [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# growfs /dev/mirror/RAID1p1 We strongly recommend you to make a backup before growing the Filesystem Did you backup your data (Yes/No) ? Yes new file systemsize is: 1048559 frags Warning: 262076 sector(s) cannot be allocated. growfs: 1920.0MB (3932160 sectors) block size 16384, fragment size 2048 using 15 cylinder groups of 128.00MB, 8192 blks, 16384 inodes. with soft updates super-block backups (for fsck -b #) at: 1835168, 2097312, 2359456, 2621600, 2883744, 3145888, 3408032, 3670176 [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# mount /dev/md0 on / (ufs, local) devfs on /dev (devfs, local) /dev/md1 on /var (ufs, local, union) /dev/ad0a on /cf (ufs, local, read-only) [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 80430 74612 5818 93% / devfs 1 1 0 100% /dev /dev/md1 31470 12 28942 0% /var /dev/ad0a 39406 34216 5190 87% /cf [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]#

9. Ok, go back to the webui and create the mount point again, then check the size either via the webui or via 'df' from your ssh session and you should be at full capacity.

[root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 80430 74614 5816 93% / devfs 1 1 0 100% /dev /dev/md1 31470 12 28942 0% /var /dev/ad0a 39406 34216 5190 87% /cf /dev/mirror/RAID1p1 1904078 69300 1682452 4% /mnt/NAS1 [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]# [root@freenas /dev/mirror]#

Hamcation!

Yeah, we went camping at Hamcation again this year, and it was a good time except that I forgot to bring my sleeping bag and pillow. This year, we started a day early and drove over on Thursday about noon and checked-in after a quick side trip to Skycraft. Arriving at Hamcation early this year was pretty nice, but we had a little pressure getting the campsite set up due to impending storms which, fortunately, never materialized. Compared to last year, the temperature was warmer and it was a great time for all of us (KI4OFU (me), KG4YNI, KI4EFN, AF1RE, KI4OFV (my wife)). I didn't find any cheap Soekris SBCs this year, dang it all, but I did pick up a few goodies. The biggest was a new ICOM IC-2820H with the D-Star/GPS board. This is a beautiful radio, and now I get to learn all about how D-Star works. I also picked up a TRSB for my Buddipole, as well as the Rotating Arm Kit. Other miscellaneous goodies from here and there filled out the annual shopping spree, and it was a lot of fun. Let me take a minute to tell you how much I like ICOM. Not necessarily the radios, though I do adore my IC-7000 and I think the same will be true for this IC-2820H pretty soon, but the company itself. I have a young son, 2.5 years old, and the comic books that ICOM publishes are a great way for me to read to my son about amateur radio and get him interested in it. I know it's smart business for them to appeal to a younger generation for the future of the hobby and consequently future hardware sales for them, but they stand out because they are doing that and I don't see a hint of that kind of youth-oriented material from either Yaesu or Kenwood. Go ICOM! Our club had a swap table set up again this year with tons of junk on it, both donated to the club and also consigned by club members. I would say that about 1/2 of it was sold and the other 1/2 given to other vendors on Sunday afternoon because we didn't want to haul any of it back to Lakeland. Either way, it was good revenue for the club. I think that when Hamcation 2009 comes around, we will probably still camp but might do it in the travel trailer rather than in the tent. Also, staying on Saturday night, which we didn't do in 2007, was not optimal this year since by mid-morning on Sunday most of the vendors were packing up and getting ready for the trip home. Yeah, I think that next year we may pack up camp when we get up on Saturday morning and then make one final good day of it before heading home. We'll see.

NanoBSD - part 1

Wow, where do I start. Last year, I picked up a few Soekris net4521 boards from the Orlando Hamcation. The guy didn't know what he had and sold them to me for $10 each. Nice. I tinkered around with them a little bit last year and got some help with kernel, world, and package building for the NanoBSD image from Bruce Mah. I had built up a nice image on a 512MB CF card and played for a bit, but then life came charging back in and I had to shelve the project for a while.

Now I am back, and here is some stuff to chew on. First, here is a short shell script that I wrote and dropped into /usr/src/tools/tools/nanobsd to evaluate the packages in /usr/src/tools/tools/nanobsd/Pkg and determine if there were any missing dependencies before starting the image building process.

#!/bin/sh
#
# make packages for /usr/src/tools/tools/nanobsd/Pkg:
#  if the port is already installed:
#   cd /usr/src/tools/tools/nanobsd/Pkg && pkg_create -vyb netcat-1.10_2
#  if the port is not installed:
#   cd /usr/ports/net/netcat && make package && mv \
#   /usr/ports/packages/All/dnsmasq-2.38.tbz /usr/src/tools/tools/nanobsd/Pkg/
#
#
# next, run this script to ensure that you aren't missing any deps for the packages
# you want in your image.
#
# after that, you can run `sh nanobsd.sh -c nanobsd-soekris.conf` to build a new image
#
# or, if you are just adding/removing packages to the existing image, you can
# run `sh nanobsd.sh -b -c nanobsd-soekris.conf` to save the time of building world
# and kernel.
#

cd /usr/src/tools/tools/nanobsd

rm -f pkg_deps.list

cd /usr/src/tools/tools/nanobsd/Pkg

for each in *.tbz;
do
 pkg_info -r ${each} | grep Dependency | cut -d' ' -f2 | while read dep
 do
  /bin/ls -1 | grep ${dep} >/dev/null || echo "${each} needs ${dep}" >>/usr/src/tools/tools/nanobsd/temp.$$
 done
done

cd /usr/src/tools/tools/nanobsd

[ -f temp.$$ ] && (cat temp.$$ | sort | uniq >pkg_deps.list && rm -f temp.$$)

That works pretty well. After ensuring that my package list was good to go, I started the build process and it went well. Much thanks need to go to Poul-Henning Kamp for his work on the NanoBSD infrastructure, it's just simply wonderful.

Right now, I am using a Soekris net4521 as my firewall, running off of a little 12v DC wall-wart, instead of the old power-sucking 400w AC-powered tower that I was using. Saving power and money, which are good things, and now I have moved from using IPFW/IP6FW on that old tower to using PF on this Soekris. More about using PF later!