# Mind Candy

Wednesday, March 14, 2007

"women who love too much & the interfaces that ignore them"

I'm feeling dull and thick today, like half my blood has been replaced by sugar-free molasses. It's kind of like watching Jerry Springer after eating a tube of toothpaste.

I've got an entry in my /etc/rc.conf file that reads:
ifconfig_xl0="inet 192.168.1.9 netmask 255.255.255.0"

It's almost the same as its counterpart, ifconfig_fxp0--one number and two letters difference, in fact. There don't appear to be typos, and I have Known Good hardware installed on the box.

So why can't I see xl0 when I do an ifconfig? Why does it tell me "ifconfig: interface xl0 does not exist"?

Added "network_interfaces="fxp0 xl0 lo0" to my /etc/rc.conf, to no avail. I've added a line to /etc/defaults/rc.conf that says: 'ifconfig _xl0="inet 192.168.1.9"' and rebooted my machine. Checked /dev/net and did not see an xl0.

I'm looking at this sort of thing under uname -a:
"FreeBSD toybox.company.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri jan 12 10:40:27 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386

"ifconfig xl0 create" also does not seem to work. The error message ends up being "ifconfig: SIOCIFCREATE: Invalid arguement". I wonder what's wrong...did I just not read the manual closely enough? Does the same action taken in 6.0 not work in 6.2?

Labels:

Monday, February 26, 2007

make install whine

What a day. First, the Clover school's theory professor whined about how he couldn't get Asterisk to work on a hard drive on one of his overpowered (but underfunctional) computers while we students looked up the answers FOR HIM, and now my IDS hardware appears to be flaking out.

Yesterday, I installed FreeBSD on one of the machines designated for use as a sensor. Today, it decided all checksums were completely invalid and then something decided to fandango on core.

I'm installing Windows 98 on the drive, then I'll install FreeBSD back on top of it.

I love computers. I just don't love when they misbehave suddenly and without warning. I know that Sguil works because I've seen it and I've implemented it at a site or two. It's just a matter at this point in having the time to fight with hardware and software issues. I love FreeBSD. I just don't love how it comes to an anxiety-attack style halt and can no longer function without having a boot to the head. I love Sguil unconditionally.

Is it maybe that I've got a big ol' USB device attached to it when I'm attempting to download and untar the ports collection? This is the same machine that won't reboot if same USB device is attached...

Labels: