[01:01] *** LT has joined #arpnetworks [01:11] *** bob___ is now known as bob^^ [01:26] LT, btw, I found another provider, one in the netherlands - liteserver.nl [01:26] you're really searching hard aren't you? I signed up for portfast a few days back... seems ok so far [01:26] if you check WHT, they have a 128MB VPS for 6 EUR (not sure if they still accept it) [01:27] hehe yeah :) [01:27] good to hear [01:28] the fact they are also a registrar that does v6 glue was a welcome plus [01:28] I didn't know that.. that's pretty cool [01:28] they're a reseller tho right? [01:29] not that it matters really [01:31] not for .uk as far as I can tell, but I think they resell tucows for some other tlds [01:31] *** schmir has joined #arpnetworks [01:32] ah [01:34] fwiw, so far so good with goscomb here [01:37] I'm considering switching to liteserver tho because 1) they're offering 750GB bandwidth (not sure that I'll need it, but just in case) and 2) their routes are amazing from what I've seen here (and about 20ms less on pings than to goscomb) [01:38] for the same price or cheaper too [01:38] with exchange rates [01:38] not sure what their support is like though [01:40] well, coupon(s), exchange rates, and plans [01:40] can't hurt to try it for a month I guess [01:41] yeah, that's what I'm considering doing [01:41] I'll mull it over [01:42] my only worry would be they're xen rather than kvm.. had odd experiences with xen in hvm mode before [01:44] that's actually what goscomb uses (well, Citrix XenServer, the commercial version IINM) [01:45] but yeah, I'm using goscomb in HVM mode [01:45] no problems (yet) ;) [01:49] its not clear tho, whether you can install just whatever you like at liteserver [01:49] kinda sounds like a no ("Other OSes are available on request") [01:50] in other words, they're probably running in PVM mode.. but I'll check later I suppose [01:50] I suspect what it means is we have these OSes as PVM but if you want something else you can have HVM and install yourself [01:51] true, it could mean that [01:51] that's what goscomb does [01:52] yisp do that as well [01:52] have you used yisp btw? [01:53] their web design kinda scared me off for one thing [01:53] I mean, it's not bad.. it, I guess, lacks content more than anything [01:55] *** killring has quit IRC (Ping timeout: 276 seconds) [01:59] yeah... got it half price on wht some time back, their connectivity is ok, but having some issues with the system hanging [01:59] seems like sometimes the disks just drop out... think it's some xen hvm issue and as most of their customers are pvm they haven't really put that much time into working it out [02:00] *** sentabi has quit IRC (Ping timeout: 264 seconds) [02:05] ah [02:06] glad I stayed away then [02:06] btw, are you using linux too, or say freebsd? [02:08] linux... learning freebsd is on my list of things to do on a rainy day [02:09] gotcha [02:23] *** sentabi has joined #arpnetworks [03:09] *** ncullen is now known as Guest13192 [03:10] *** ncullen has joined #arpnetworks [03:52] *** ncullen has quit IRC (Quit: leaving) [04:33] *** schmir has quit IRC (Remote host closed the connection) [04:58] *** Guest13192 has quit IRC (Quit: Lost terminal) [05:03] *** nakano is now known as nakano_ [05:18] *** sentabi has quit IRC (Changing host) [05:18] *** sentabi has joined #arpnetworks [05:28] *** tinono has joined #arpnetworks [06:05] how does arp share out cpu resources? does it guarantee a certain number of cycles with bursting when the rest of the cpu is idle or what? [06:15] *** nakano_ is now known as nakano [06:23] heda: not over-allocating means dividing the cpu power in a given system amongst kvm systems so that each kvm system can have its allotted cpu slices fully w/out degredation [06:26] aka if there is 8 3ghz cpus in a system, there could be 24 1ghz kvm instances .. [06:27] but that is just an example, I am honestly not sure how arpnetworks works that out but they are quite clear about not over-allocating memory and cpu [06:28] it is truly amazing but my physical hardware laptop is slower than my kvm instance at arpnetworks.. md5 speedtest results: [06:28] my laptop: Speed = 76614086.419157 bytes/second [06:29] arp kvm: Speed = 430477830.391735 [06:30] there have been some benchmarks (unofficial of course) that show arp is much faster in general than other vps providers [06:45] *** nakano is now known as nakano_ [06:46] *** ziyourenxiang has joined #arpnetworks [06:50] toddf: thats cool, i know some providers equal split the cpu resources as a 'dedicated' cycles but then if there's a load from one vps and other vps's aren't using their cycles you can burst until the other vps needs them back [06:56] toddf: i'd image also that the md5 test results are down to raid 10 throughput rather than anything else [07:01] *** nakano_ is now known as nakano [07:10] *** nakano is now known as nakano_ [07:10] *** nakano_ is now known as nakano [07:26] *** Hien has joined #arpnetworks [07:28] still Sold out ? [07:31] *** nakano is now known as nakano_ [07:31] *** nakano_ is now known as nakano [07:41] *** Hien has quit IRC (Quit: Page closed) [09:11] *** heda has quit IRC (Quit: heda) [09:13] *** LT has quit IRC (Quit: Leaving) [09:36] removing sold out sign now... [09:42] \o/ [09:51] up_the_irons: you'll always be sold out to me [09:51] heavysixer: whut? ;) [09:51] up_the_irons: you know like "you sold out" [09:52] heavysixer: haha [09:52] *** ziyourenxiang has quit IRC (Quit: ziyourenxiang) [09:52] http://en.wikipedia.org/wiki/Wikipedia [09:52] haha [09:55] lol [10:14] *** nakano is now known as nakano_ [10:33] *** wallshot has joined #arpnetworks [10:34] *** killring has joined #arpnetworks [10:41] *** schmir has joined #arpnetworks [10:47] *** heda has joined #arpnetworks [11:02] *** heda has quit IRC (Quit: heda) [11:06] *** schmir has quit IRC (Remote host closed the connection) [11:12] *** tinono has quit IRC (Quit: leaving) [11:32] *** Hien has joined #arpnetworks [11:32] *** schmir has joined #arpnetworks [11:40] *** nynex_ has joined #arpnetworks [11:41] *** Hien has quit IRC (Quit: Page closed) [11:41] *** nynex_ has left [12:10] *** heda has joined #arpnetworks [12:21] *** tinono has joined #arpnetworks [12:24] *** heda has quit IRC (Quit: heda) [12:30] *** schmir has quit IRC (Ping timeout: 276 seconds) [12:33] *** schmir has joined #arpnetworks [12:36] *** iaaron has joined #arpnetworks [12:37] *** iaaron has quit IRC () [13:10] *** tinono is now known as _tinono_ [13:10] *** _tinono_ is now known as tinono [13:11] *** nakano_ is now known as nakano [13:12] *** tinono has quit IRC (Quit: leaving) [13:23] *** mattx86 has quit IRC (Read error: Operation timed out) [13:26] *** mattx86 has joined #arpnetworks [13:43] *** tinono has joined #arpnetworks [13:47] *** schmir has quit IRC (Remote host closed the connection) [14:56] *** mattx86 has quit IRC (Read error: Operation timed out) [14:57] *** mattx86 has joined #arpnetworks [16:03] *** wallshot has quit IRC (Quit: Leaving.) [16:33] hm.. anyone know if nagios would allow you to run a traceroute if latency/packet loss flaps to and from certain thresholds during a specified period of time, and e-mail you the traceroute(s)? [16:34] I'm not running nagios (or anything at the moment), but I've been considering writing my own network monitor app [16:36] specified period of time = say, within a 20 second window [16:42] you can write arbitrary nagios plugins in whatever language, it's just got a specified output format [16:43] so the email would have to be out-of-band, as nagios just gets pass/warn/fail I think [16:43] wouldn't be that difficult though [16:44] sounds doable [16:44] you can give exteneded output in the status [16:44] arbitrary text [16:44] you'll have to drill down in the interface though [16:45] or wait... you can have it be part of the email [16:45] might be by default [16:45] ... http://nagios.sourceforge.net/docs/3_0/pluginapi.html [16:46] see the "long text line 1" [16:46] $LONGSERVICEOUTPU$ macro for the email [16:47] so yeah, you can do it... just gotta write your plugin to do what you want [16:48] I think I'm still leaning towards implementing it for my own network monitor app [16:48] I've got a lot of great ideas for one [16:49] you and 50 others :) [16:49] Only 50? [16:49] RandalSchwartz: what was the idea you had the other day, if you don't mind telling me? [16:50] where 50 means "uncountable" :) [16:50] which idea? [16:50] Ah, I sit corrected. [16:50] something about when to send notifications, like queue them until the 9-5 period of the day, I believe [16:50] yeah, researching network monitors always felt like a million monkeys on typewriters to me [16:50] ahh. lemme think [16:51] there's another idea - allow the user to specify the timezone for notifications too [16:51] that's already there [16:51] e.g., for international cooperation [16:51] Just don't bring the pager home. :-) [16:51] lol yeah [16:51] mv pager /dev/toilet [16:52] Mine just stays at work. :D [16:52] the flapping on the wireless network forced my last boss to stop using his pager until I adjusted the thresholds to something that 'worked' ;) [16:53] flapping on wireless networks was worthy of a page? [16:53] nagios at least has that figured out [16:53] notify at first breakage [16:53] it was important to me anyways. we'd normally get 1 to 10ms on a good link [16:53] then don't notify "up again" until up again in a long enough ratio [16:54] maybe 25ms [16:54] I liked the idea of having a "flapping" status, too [16:54] we currently use ipMonitor 9, which is way too basic for what we do [16:54] I hate it [16:55] every other NMS sucks worse though [16:55] btw, does nagios properly do notifications in a network hierarchy? [16:56] yes [16:56] you can tell it "this hides that" [16:56] last time I tried nagios, despite specifying parent nodes, it would notifying me of everything below the parent that was down [16:56] so it will only complain about the nearest border [16:56] nagios is a bit of a whore to configure, true [16:56] s/notifying/notify/ [16:57] this was actually nagios 2.0b3 or something :P [17:00] i'm late to this discussion, but if you like nagios, take a look at Opsview [17:01] it's nagios (but with improvements) and a *very* useful/usable/stable frontend [17:01] also makes scaling nagios across multiple servers very simple indeed [17:03] interesting.. is the community version just as good? [17:04] yup [17:04] we use the community version in work at the moment (i work for an ISP) [17:04] one master server, three slaves which run checks and a dedicated database [17:04] nice [17:05] I'll take a better look at it later [17:05] I'll bbl [17:05] there's #opsview if you need info :) [17:05] or just give me a shout [17:06] cool, thanks :) [17:17] bob^^: will it run on openbsd? :) [17:19] i've been meaning to migrate my old nagios setup to my new openbsd atom box [17:21] if nagios works but you hate how it looks, why not just look at the alternate frontends? [17:21] I mean I hate how nagios looks, but it's not like I have to look at it on a regular basis or anything. [17:26] if you do, you're doing something wrong [17:26] or other people are ;) [17:27] I dunno, we have the dashboard thing up on a monitor here, but that's more just a convenient status board. [17:58] *** bob___ has joined #arpnetworks [17:58] *** bob^^ has quit IRC (Read error: Operation timed out) [18:00] *** bob___ has quit IRC (Read error: Connection reset by peer) [18:01] *** mattx86 has quit IRC (Read error: Operation timed out) [18:01] *** mattx86 has joined #arpnetworks [18:07] *** bob^^ has joined #arpnetworks [18:44] *** fink has joined #arpnetworks [18:50] *** fink has quit IRC (Remote host closed the connection) [18:51] *** fink has joined #arpnetworks [19:18] "will it run on openbsd" is related to "will it blend?" :) [19:18] up_the_irons - how's your health? [19:28] things tend to blend way easier than they tend to run on OpenBSD ~_~ [19:48] *comming for an obsd guy* :-p [19:48] from* [20:12] *** tinono has quit IRC (Ping timeout: 255 seconds) [20:21] *** bob^^ has quit IRC (Read error: Connection reset by peer) [20:54] *** tinono has joined #arpnetworks [21:04] *** mattx86 has quit IRC (Read error: Operation timed out) [21:05] *** bob^^ has joined #arpnetworks [21:10] *** fink has quit IRC (Read error: Connection reset by peer) [21:13] *** fink has joined #arpnetworks [21:20] *** mattx86 has joined #arpnetworks [22:05] *** fink has quit IRC (Quit: fink) [23:08] *** killring has quit IRC (Quit: leaving) [23:12] Even bricks, for instance [23:52] *** nakano is now known as nakano_ [23:54] *** tinono has quit IRC (Changing host) [23:54] *** tinono has joined #arpnetworks