[00:29] <Skaag> I'm trying to install Ubuntu 8.04 on a machine with an Intel 82576 NIC (drive name is 'igb')
[00:30] <Skaag> It doesn't detect the network card
[00:32] <Skaag> I can only find a driver for Redhat & Suse, on SuperMicro's site
[00:45] <ziesemer> Skaag what is SuperMicro? Can't you get a driver directly from Intel?
[00:45] <Skaag> I don't really know how to do that
[00:46] <Skaag> what to get
[00:46] <Skaag> how to prepare it so that Hardy's Install CD will see it
[00:46] <twb> A driver for what?
[00:46] <Skaag> for Intel's 82576 network card ('igb' module)
[00:46] <Skaag> It works in Jaunty
[00:47] <Skaag> but I'm supposed to install 8.04 LTS on this box
[00:47] <Skaag> I wish I could just install Karmic on it
[00:47] <ziesemer> Just install Hardy.  It doesn't need the network to work right away.
[00:47] <Skaag> and then?
[00:47] <twb> Skaag: it's part of the mainline kernel
[00:47] <twb> Skaag: to get it to work on Hardy, you'll need to install a non-Hardy kernel
[00:48] <Skaag> I see
[00:48] <ziesemer> Can't he install as a module otherwise?
[00:48] <Skaag> if I mount the karmic cd?
[00:48] <twb> ziesemer: if it was packages as a standalone module, perhaps.
[00:48] <Skaag> can I install its kernel  on hardy?
[00:48] <twb> ziesemer: as it is, I don't know.
[00:48] <ziesemer> I'm looking on Intel...
[00:49] <ziesemer> They always seem to have pretty good Linux support.
[00:49] <twb> Skaag: it's usually a very bad idea to install packages -- especially low-level packages -- from a different release.
[00:49] <twb> ziesemer: good support means that it's in the kernel, not that you download a shitty third-party driver.
[00:49] <twb> Installing third-party drivers is also a good way to make your system unstable.
[00:50] <ziesemer> Yes, exactly:  http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=13663
[00:50] <ziesemer> twb:  It may not be exactly desired, but it'll meet his requirements.
[00:51] <ziesemer> Skaag:  There's a readme in the download.  Just compile and follow the instructions after you install Hardy.
[00:51] <twb> Skaag: what's your reason for running Hardy?
[00:51] <ziesemer> It's not like it's a "binary BLOB", as used with some video drivers.
[00:51] <Skaag> I need to compile this on another 8.04 that works already and is connected, right?
[00:51] <ziesemer> Hardy is also LTS, remember.
[00:51] <Skaag> twb: It's requested by some company I work with
[00:52] <twb> ziesemer: yes, that's my guess.
[00:52] <Skaag> They want 8.04 because it's LTS
[00:52] <ziesemer> Skaag:  You could, but I'd just run it on the machine you need it on.
[00:52] <twb> Skaag: what I'd tell the company is that you can install 8.04, but you'll need an out-of-band driver -- or you can install a non-LTS release and upgrade to 10.04 in a few months.
[00:53] <twb> Both suck, so IMO it's best to leave the decision to the customer
[00:56] <ziesemer> I just went through all this on a system with a Realtek network card.  My only issue was that the r8169 driver from Realtek's web site wasn't updated yet for the latest 2.6.31 kernel, so it won't compile without some patchwork, or until Realtek updates it.  In this case, Intel last updated the driver just last month, so I doubt you'll have any issues.
[00:59] <Skaag> ziesemer: I need to find a way to copy it there... along with build-essential... without a network!
[01:00] <Skaag> 10.04 is the next LTS?
[01:00] <Skaag> how long until that's out?
[01:05] <ziesemer> 10.04 would be roughly April 2010.
[01:05] <pting> is it just my network, or is amazon.com down?
[01:06] <ziesemer> Skaag:  Especially if you use the DVD installation of hardy, you should have most everything you need available, including build-essential.
[01:06] <ziesemer> pting:  It's just your network.  :-)
[01:07] <ziesemer> Skaag:  Otherwise, you can always "sneaker-net" the packages, using a USB flash drive, etc.  Or just temporarily install a compatible network card.
[01:07] <Skaag> I don't have physical access to the machine, just IPMI, so I can connect my local cd-rom, and my local flopy
[01:07] <Skaag> floppy
[01:07] <Skaag> all the iso files are on my laptop here
[01:09] <ziesemer> Well, after you complete the initial install, you can always create new .iso's containing the files you need, if necessary.
[01:16] <twb> Skaag: can you have a waldo add a second NIC to the machine temporarily?
[01:17] <twb> Skaag: or use IP-over-1394?
[01:17] <twb> If it has to be via CD, you can use jigdo to create a CD with the packages you need.
[01:29] <Skaag> jigdo sounds like the only option I have
[01:33] <twb> What kind of box is this?
[01:33] <twb> Normally I would just slap in an e100 for a few months, then upgrade to 10.04
[01:34] <Skaag> 10.04 is available now?
[01:34] <Skaag> ok sorry
[01:34] <Skaag> don't answer that
[01:34] <Skaag> I just re-read what you wrote
[01:34] <Skaag> I'm just really tired
[01:34] <Skaag> there's nobody I can speak to right now, so I can't have anything put into the server
[01:36] <twb> I hate hardware
[01:37] <Skaag> oh man, so do I
[01:37] <twb> When computers run entirely in software, I'll be happy
[01:37] <Skaag> every hardware manufacturer and his own stupid proprietary crap
[01:37] <ziesemer> They do.  Enter virtualization.  :-)
[01:37] <twb> ziesemer: SOMEONE is still responsible for the hardware
[01:38] <Skaag> I actually believe in Open Source hardware
[01:38] <Skaag> And its adoption by companies
[01:38] <Skaag> like, ok, here's a standard for implementing a network card
[01:38] <Skaag> and companies will just make cards to that spec
[01:38] <twb> There are like four pieces of fully open hardware
[01:39] <twb> Everything else just has open drivers and -- if you're lucky -- a well-documented ABI
[01:52] <neezer> hello
[02:14] <ziesemer> I had to replace a failed motherboard with a different replacement, so a new on-board LAN controller.  My configured VLAN is no longer receiving traffic, but everything else is working.  Just ruled out driver issues, as it works on a reinstall to a different hard drive.  Is there anything else that needs to be cleared out due to this, e.g. a MAC address stored somewhere?
[02:22] <twb> ziesemer: yes
[02:22] <twb> ziesemer: udev remembers MAC -> interface name mappings
[02:23] <twb> ziesemer: delete the relevant file in /etc/udev/rules.d/
[02:23] <twb> Or reconfigure everything to operate on eth2
[02:23] <ziesemer> twb: Done, both ways.
[02:23] <twb> That's the only place the MAC is stored on a typical 8.04 system
[02:23] <twb> s/system/server/
[02:24] <ziesemer> Originally tried removing the old rules, to keep everything on eth0 and eth0.*.  Then tried moving to eth1 and eth1.*, in case there was something funny about eth0.
[02:24] <ziesemer> Is actually a Karmic / 9.10 system.
[02:25] <ziesemer> Or what else can I do to essentially "reset the network" without having to re-install the entire system?  (It works on a fresh install to a new HD.)
[02:25] <twb> I have no experience with non-LTS releases, sorry
[02:27] <ScottK> ziesemer: I'd grep -r "[MAC address]" * in /etc
[02:28] <ScottK> I think I was running Feisty the last time I had deal with this.
[02:33] <ziesemer> Only result is in the /etc/udev/rules.d, which I already edited.
[02:34] <ziesemer> I guess a reinstall won't hurt, except for the time.  But I'll probably make up for it by the time I figure this out.  But I really want to figure this out, in case it happens again...
[02:35] <ScottK> You did restart the machine after editing that, right?
[02:36] <ziesemer> Yep.
[04:05] <neezer> hello
[04:05] <neezer> does anyone here know much about getting remote desktop to work via ssh?
[04:09] <ziesemer> By Remote Desktop, do you mean the Windows tool?  I.E., using SSH to secure your RDP traffic?
[04:09] <neezer> I'm not sure.
[04:09] <neezer> I just want to be able to see the desktop on my media server and use my mouse on it in a window.
[04:10] <neezer> I am not exactly sure how I was doing it before, but I had it working with putty on vista. now i just have ubuntu on my laptop with ubuntu also on my server box.
[04:12] <twb> ziesemer: on Windows, RDP is called "tsclient"
[04:12] <ziesemer> twb:  Yes, but that's not what he's looking for here.
[04:12] <twb> neezer: if your media server runs Linux, the easiest thing is to use VNC (over SSH, for security).
[04:13] <ziesemer> neezer: Well, that's kind of off-topic for here, but especially if you're doing Linux -> Linux, you'd either want X11 forwarding, or probably VNC.  Check out https://help.ubuntu.com/community/VNC .
[04:13] <neezer> how do I do that?
[04:13] <twb> "ssh -fX fs oowriter" is also pretty easy, I guess :-)
[04:15] <neezer> I guess I have been doing x11 forwarding. I have been opening things like gedit, firefox just to test it, fahmon.
[04:15] <twb> neezer: that's X forwarding, yes
[04:17] <neezer> I read somewhere that i could use the command gnome-desktop when ssh'd into my server to see the desktop...it gives me errors.
[04:17] <twb> X forwarding just runs applications (or even an entire desktop) remotely.
[04:18] <twb> It doesn't let you view what's on another desktop -- for that, you need VNC
[04:18] <twb> But as ziesemer points out, GUI stuff is off-topic here.
[04:21] <neezer> I guess I'm missing something. You are saying that x forwarding would allow me to run an entire desktop. then right after it you say it doesn't let me view another desktop.
[04:22] <twb> neezer: GNU/Linux can display an arbitrary number of desktops concurrently
[04:24] <neezer> I think I get it.
[04:25] <neezer> if someone were logged into my server at home while I was away, we couldn't share the same desktop and watch each other do work with x forwarding.
[04:25] <neezer> in order for two people to view the same desktop you need vnc?
[04:26] <twb> neezer: or some other desktop *export* system
[04:26] <twb> VNC is the only one that's widely available
[04:26] <neezer> i see.
[04:26] <neezer> so using x forwarding I should be able to pull up a desktop and control it remotely with ssh?
[04:26] <twb> neezer: yes.
[04:26] <neezer> cause that is really all I need.
[04:26] <neezer> thank you.
[04:26] <twb> For example, you could run Firefox remotely
[04:27] <neezer> yes. and I have.
[04:27] <twb> Except for thin clients, you wouldn't normally forward an entire desktop
[04:27] <neezer> I just run into problems when I try to run the desktop.
[04:27] <neezer> oh.
[04:28] <neezer> so I need to go to ubuntu-gui??
[04:28] <twb> Dunno
[05:43] <maxgqc> i'm running a wisp (wireless isp). I have a linux bridge proxy cache server between my router and the lan/wlan. I'd like to get statistics on bandwidth usage of each station. Does anyone know something that could do that ?
[05:54] <ziesemer> So my VLAN issues appear to be due to the physical interface being part of a bridge (bridge_ports in /etc/network/interfaces).  If I remove the bridge, then everything works as expected.  Could this be driver specific?  (It worked with my old motherboard, same installation.)
[05:54] <twb> I've only ever put a bridge on a vlan, not the other way around
[05:55] <ziesemer> Well, I need to bridge VirtualBox to the "untagged VLAN".
[05:56] <ziesemer> So previously, I had eth0 (physical), eth0.5 (vlan), vbox0, and br0.  br0 was made of eth0 and vbox0.
[05:56] <ziesemer> Right now, VirtualBox isn't even in the equation.  The moment I add only eth0 to a bridge "br0", the VLAN transmits, but no longer receives traffic.
[05:58] <twb> ziesemer: that would be a bridge on top of eth0.0
[05:58] <twb> Or eth0.1 or whatever your untagged vlan is
[05:59] <twb> Hmm, does Linux use raw "eth0" for untagged packets?
[05:59] <ziesemer> "eth0" was working for me, prior to replacing the Motherboard and getting a new network controller/driver.
[05:59] <ziesemer> Should eth0.0 work?
[05:59] <ziesemer> Maybe that's my entire issue?
[06:00] <twb> As "ip addr" which interfaces have IPs
[06:00] <twb> Here, eth0.0 and eth0.1 have IPs
[06:00] <twb> (that's on a 2.4 kernel OpenWRT)
[06:00] <ziesemer> I'll try declaring my "eth0" as "eth0.0" instead...
[06:07] <ziesemer> Seems like it must be eth0.0000 .  This fixed communication on my VLAN.  But now I have no communication on the untagged VLAN...
[06:08] <ziesemer> Basically same as before.  eth0.0000 is transmitting traffic, but not receiving.
[06:15] <ziesemer> Looks like someone else had my issue:  http://www.mail-archive.com/bridge@lists.linux-foundation.org/msg01269.html
[06:24] <Jeeves_> ziesemer: Is that box using udev too?
[06:24] <ziesemer> "that box"?  Yes, I'm using udev, I think...
[06:26] <ziesemer> Basically, I mostly solved my previous "VLAN" issue.  It appeared that VLAN was broke on my new network controller with different drivers.  However, it is only "broke" when I attempt to bridge the untagged (physical) interface.
[06:27] <Jeeves_> ziesemer: Udev might be renaming your interface
[06:27] <Jeeves_> look in /etc/udev/rules.d/70-persistent-net.rules
[06:27] <ziesemer> I don't think this is the issue here...
[06:28] <Jeeves_> If your old interface is mentioned in there, you might get weird results
[06:28] <ziesemer> I've now reinstalled since the motherboard replacement.
[06:28] <ziesemer> That rule file has only one line for my physical adapter, naming it to eth0, which I believe is correct for my setup (?).
[06:28] <Jeeves_> Ah ok
[06:29] <Jeeves_> I've never experienced the issues you describe above
[06:30] <ziesemer> Do you have a setup with both bridging and vlans?
[06:31] <Jeeves_> Yes, although without a native vlan
[06:31] <Jeeves_> But i've had that before
[06:31] <ziesemer> As did I - before I had to replace hardware...
[06:31] <Jeeves_> ziesemer: What switching hardware are you using?
[06:32] <Jeeves_> Should be a real issue if you push it tagged to the switch, iirc
[06:32] <ziesemer> A Dell PowerConnect.  Guess I could just reconfigure it to send all untagged traffic to this box as a new tag...
[06:33] <Jeeves_> iirc, with Cisco, if you put the native vlan tagged in the trunk as well, it'll stop using the native vlan and start using the tag
[06:33] <Jeeves_> Not completely sure though
[06:34] <Jeeves_> Anyway, have to go
[06:34] <ziesemer> At least on the PowerConnect, the "untagged" traffic is actually VLAN1 - which is just configured to untag on all ports by default...
[06:34] <ziesemer> Thanks for the insight.
[06:34] <Jeeves_> np, good luck
[08:20] <quietone> newbie here. I'm trying to setup a home network to run a calendar for the family. I followed instructions at UbuntuGeek and it seems to work fine on the host machine (mine). But I can't get another machine to access the calendar or publish.  I've skimmed the server guide but it doesn't seem to fit what I am trying to do.
[08:36] <twb> quietone: what kind of calendar?
[08:37] <twb> The traditional kind of email-based BSD calendaring is, I suspect, not what you mean
[08:38] <Aison> hello
[08:38] <Aison> how can I bring rsyslogd to accept external logmessages over network?
[08:38] <Aison> I uncommented this lines in rsyslog.conf
[08:38] <twb> Aison: isn't that covered in the ubuntu server guide?
[08:38] <Aison> $ModLoad imudp
[08:38] <Aison> $UDPServerRun 514
[08:38] <quietone> I found a page describing how to set up a remote calendar using webDAV and mozilla songbird
[08:38] <Aison> but it dont help
[08:39] <twb> quietone: ITYM sunbird (iceowl).
[08:40] <Aison> twb, maybe? but where?!
[08:40] <twb> Lemme look...
[08:41] <quietone> twb: ? new to chat too and don't know what you are saying
[08:41] <twb> quietone: the Mozilla calendar application is called "sunbird", not "songbird".
[08:42] <twb> Aison: I can't find a mention of it, so ignore me.
[08:42] <quietone> twb: yes, it was a typo.
[08:43] <twb> quietone: where is this page you're reading?
[08:44] <quietone> twb: i'll be a minute as I figure out tinyurl again ... and help a child who just called....
[08:48] <quietone> twb: I used this:   http://tinyurl.com/yfc2xpj
[08:49] <qman__> quietone, well I see the problem
[08:49] <qman__> that doc is from november 2007
[08:49] <qman__> stuff has changed a lot in the last two years
[08:50] <quietone> qman__: ok, where do I start?
[08:51] <qman__> well, I haven't set anything like that up, but you should always start with official documentation first
[08:51] <qman__> the ubuntu server guide, official help and wiki, etc
[08:52] <quietone> qman__: I have read through the ubuntu server guide and it hasn't help me.
[08:52] <qman__> ok, well it looks like a pretty straightforward setup from what I've read so far
[08:53] <qman__> I don't know anything about the calendar bit but I know a lot about apache
[08:53] <qman__> first make sure it's running and what port it's on
[08:56] <quietone> qman__: thanks, yes apache2 is up and running. I have it on 80 but would like the calendar to use another, if possible so apache is listening on two ports.
[08:57] <twb> quietone: I kinda suspect you just need to tell apache to allow remote access instead of just localhost
[08:57] <qman__> quietone, that's possible but it's a little more complicated
[08:57] <qman__> you will need to create a second site configuration, using another virtualhost for it
[08:58] <qman__> but first just try to get it working
[08:58] <twb> I hate vhosting
[08:58] <quietone> qman__: that's fine I am happy to keep it simple and use 80.
[08:59] <twb> Because we don't have split-horizon DNS in the office, so the multi-homed server needs at least foo, foo.office.cybersource.com.au and foo.cybersource.com.au for any given vhost, and whoever sets up each vhost usually forgets two of the three.
[08:59] <twb> That and it means DNS needs to work in order to get to the vhosted pages
[09:00] <qman__> yeah, it can get frustrating when stuff just doesn't want to work
[09:00] <qman__> and I always end up having to mess with /etc/hosts to get apache to stop complaining
[09:00] <qman__> even when DNS is correct
[09:01] <qman__> quietone, the next step is to make sure you're answering web requests, so open up http://localhost/ on the server if you have a browser on it, and open up the server's name on the other computer
[09:02] <qman__> if you get an "It Works!" page or a directory listing, you're good
[09:02] <qman__> on both machines that is, if only localhost works we've narrowed the problem
[09:03] <quietone> qman__: it works on the host only with 127.0.0.1. Both machines fail with my static ip address.
[09:03] <qman__> ok
[09:04] <qman__> I'm guessing you don't have a firewall configured, and in that case apache would only be listening on localhost
[09:04] <qman__> run the following and paste (or pastebin if it's long) the result
[09:04] <qman__> grep -R "Listen" /etc/apache2
[09:05] <quietone> We have three machines behind a router for a firewall.
[09:05] <qman__> I mean on the machine running the calender
[09:05] <qman__> are both the server and client behind the same router?
[09:06] <quietone> yes. since I don't know pastebin yet. Can I just confirm that apache only knows about 127.0.0.1
[09:06] <qman__> well
[09:07] <quietone> qman__: Yes server and client (my machine) are behind the same router.
[09:07] <qman__> if you have any Listen lines (that aren't commented out) that specify an IP address, change them to only specify the port
[09:07] <qman__> grep -R shows you which file each line is in
[09:07] <qman__> if none of them are specifying an IP, then you need to check the site virtualhost configuration
[09:08] <qman__> which, with only one default site, should be *:80
[09:08] <quietone> ok i'll be a few minutes
[09:12] <quietone> qman: both my machine and my partner's' now get the "It works" with my static IP. Yippy!
[09:12] <qman__> great
[09:13] <qman__> hopefully the calendar will work now
[09:13] <qman__> DAV and sunbird are beyond my expertise, so if apache's working that's all the help I can provide anyway
[09:17] <quietone> qman__: you've been extremely helpful. we just tested and hubby got to the calendar! that is all we want to do!
[09:18] <j416> Hi. Does anyone know of a good guide on how to set up a CA and create a root certificate?
[09:20] <qman__> j416, https://help.ubuntu.com/9.10/serverguide/C/certificates-and-security.html
[09:20] <j416> qman__: thank you! reading
[09:21] <j416> perfect
[09:21] <j416> this'll do
[09:21] <j416> I hope
[09:22] <qman__> it really boils down to just a few commands to get going, but you need to understand what's really going on, that's why it's a bit wordy
[09:22] <qman__> CA part is below the certificate part
[09:23] <j416> yeah I found it
[09:23] <j416> thanks
[09:23] <j416> I understand the concepts, but not the complicated syntax
[09:23] <qman__> lots of options
[09:24] <j416> indeed
[11:17] <mcas> hi again
[11:18] <mcas> is there a package for icinga?
[11:18] <mcas> or is it ok if i try to build one?
[11:30] <_ruben> !info icinga
[11:50] <Thugal> icinga is an interesting project, adding some functionality to nagios that has been very slow in coming.  But version 1.0 was released on the 16th of this month.  I'm not aware of anyone packaging it yet
[12:08] <mcas> Thugal: i could try the build
[16:43] <blistov> anyone have openvas-server running on karmic WITH a plugin feed?
[16:43] <blistov> I seem to be missing the binaries to sync.
[16:46] <blistov> nvm.  bug #486790
[17:35] <Matuku> I've just made a bit of a boo-boo whilst messing around with my server; I think i've managed to strip my main account of sudo priveleges...
[17:37] <ScottK> Do you have physical access to the box?
[17:38] <Matuku> No screen attached atm but if necessary I could get one
[17:43] <Matuku> I was attempting to add the user to a new group but forget the -a so it's stripped it from all the others
[17:53] <ScottK> You can reboot and locally select the recovery option.  That'll give you a root shell you can fix it with.
[17:55] <Matuku_14> What do I need to do? Just add them to admin group again?
[17:57] <ScottK> Should be.
[17:58] <Matuku_14> Seems to have done it :)
[18:08] <Mrseek> hello
[18:08] <Mrseek> is there any good documentation on the upstart process for ubuntu ?
[18:26] <tesseracter> im putting my 2 ssds on raid0, with backup to a 2tb external, and want to figure out what settings would be best in terms of stripe size and such.
[19:06] <Hypnoz> in the command "find . -name file -exec chgrp woot {} +"  it seems I need the + at the end, but anyone know what thats for?
[19:20] <Hypnoz> http://www.linuxjokes.com/