1250294945 Q * dowdle Remote host closed the connection 1250296434 Q * vargadanis Read error: Connection reset by peer 1250296910 Q * ruskie Quit: Caught sigterm, terminating... 1250297370 N * Snow-Man_ Snow-Man 1250298333 Q * dna Ping timeout: 480 seconds 1250298986 Q * scientes Ping timeout: 480 seconds 1250303234 Q * gnarface Quit: happy friday people 1250303440 J * derjohn_foo ~aj@p5B23D293.dip.t-dialin.net 1250303885 Q * derjohn_mob Ping timeout: 480 seconds 1250304680 Q * geb Ping timeout: 480 seconds 1250306979 M * Bertl off to bed now .. have a good one everyone! 1250306979 J * docelic_ ~docelic@78.134.199.152 1250306988 N * Bertl Bertl_zZ 1250307387 Q * docelic Ping timeout: 480 seconds 1250309843 J * balbir_ ~balbir@122.172.32.209 1250311572 J * doener ~doener@i59F57F2D.versanet.de 1250311675 Q * doener_ Ping timeout: 480 seconds 1250312282 J * mib_0u1h0pgm 4ca7aa9f@webchat.mibbit.com 1250312579 Q * mib_0u1h0pgm 1250312808 J * ktwilight__ ~keliew@214.79-65-87.adsl-dyn.isp.belgacom.be 1250312808 Q * ktwilight_ Read error: Connection reset by peer 1250313572 Q * derjohn_foo Ping timeout: 480 seconds 1250313771 J * scientes ~scientes@174-21-104-37.tukw.qwest.net 1250317040 J * mxs_ mxs@p4FCCB881.dip.t-dialin.net 1250317340 Q * mxs Ping timeout: 480 seconds 1250318529 J * derjohn_mob ~aj@p5B23D293.dip.t-dialin.net 1250321210 J * ruskie ruskie@ruskie.user.oftc.net 1250322265 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250322387 Q * derjohn_mob Ping timeout: 480 seconds 1250322711 J * ktwilight_ ~keliew@162.83-240-81.adsl-dyn.isp.belgacom.be 1250322777 Q * ktwilight__ Read error: Connection reset by peer 1250323407 Q * nkukard Ping timeout: 480 seconds 1250324074 J * nkukard ~nkukard@196.209.243.54 1250324112 J * SKaReCRoW ~skarecrow@96.57.183.37 1250324138 M * SKaReCRoW I'm running vserver on one of my servers with 2 NIC's. The first guest has an external IP on eth0, the second has an internal IP on eth1, and the host also has an internal IP on eth1. The host can access the internet, but neither of the guests can. The guests can only access machines on my network. 1250324264 M * SKaReCRoW btw, I'm running a fresh install of Debian Lenny with kernel 2.6.26-2-vserver-686 1250324266 Q * AndrewLee Quit: leaving 1250324292 M * SKaReCRoW How do I get my guests to be able to access the internet? 1250324316 M * SKaReCRoW I can access them FROM the internet, well, at least the first guest that has an external IP. 1250324598 M * SKaReCRoW Anyone awake?!? 1250325003 J * AndrewLee ~andrew@u7.hlc.edu.tw 1250325056 M * SKaReCRoW Anyone? 1250325105 M * sannes SKaReCRoW: Doesn't seem like to many are awake, just hang in there! :P 1250325124 M * sannes SKaReCRoW: Anyways, if you assign that external ip to the host, does it work? 1250325147 M * SKaReCRoW I don't have any more external IPs, and I don't want the host accessible from outside anyway. 1250325147 M * sannes SKaReCRoW: (without a vserver guest) 1250325158 M * SKaReCRoW The host can get out just fine with its internal IP. 1250325196 M * SKaReCRoW I was able to get out with the guests when I first set them up, but now they don't work. I can't imagine what I might have changed to stop them from getting out. 1250325259 J * ktwilight__ ~keliew@85.169-247-81.adsl-dyn.isp.belgacom.be 1250325270 M * sannes Okay, so what have you changed? 1250325288 M * SKaReCRoW The guest with the external IP can ping ANY IP on my network, whether it be internal or external IP. The second guest with the internal IP can only ping other internal IPs. 1250325325 M * sannes And the host can ping anything right? 1250325368 M * SKaReCRoW Yeah, host works fine. 1250325551 M * sannes SKaReCRoW: uhm, I'm trying to understand your setup .. you have a vserver with two nics, one that is connected to the internet (and has an external ip) and one nic for the local network which has internal ips .. 1250325554 M * SKaReCRoW Only thing I changed was the router box... It's configured identical to the old one though. Both running the same version of shorewall with the same config files. 1250325609 M * sannes Heh, does it work if you plugin the old one? :P 1250325613 M * SKaReCRoW eth0 has external IP and connects to the vlan with the rest of the external IPs. 1250325652 Q * ktwilight_ Ping timeout: 480 seconds 1250325654 M * SKaReCRoW eth1 has 2 internal IPs, 1 for the host, 1 for the guest, and is plugged into the vlan with the rest of the servers with internal IPs, and they can all access the internet just fine. 1250325675 M * SKaReCRoW So I know it's not the router. 1250325758 M * sannes How does your routing table look like? 1250325940 Q * AndrewLee Quit: leaving 1250325945 J * AndrewLee ~andrew@u7.hlc.edu.tw 1250326003 M * SKaReCRoW for the guest with the external IP it has "xx.xx.xx.32 0.0.0.0 255.255.255.248 U 0 0 0 eth0" 1250326016 M * SKaReCRoW Then "172.16.10.0 0.0.0.0 255.255.255.0 U 0 0 0 *" 1250326019 M * SKaReCRoW Nothing else. 1250326045 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1250326118 M * SKaReCRoW Heh, the host didn't have a default gateway set. Weird, cuz the host could get out with no problem. 1250326152 M * SKaReCRoW Now it looks like the guest with the external IP can access anything, but hte one with the internal IP still can't access my external IPs. 1250326316 M * sannes Probably because you do not have a default gateway with an internal ip in your routing table .. ? 1250326335 M * SKaReCRoW I'm thinking I have something configured wrong with the networking. It should have come up with a default gateway. The host has "gateway 172.16.10.1" in /etc/network/interfaces 1250326408 M * SKaReCRoW In my host ifconfig reports eth1 as having 172.16.10.138 and in the guest it shows eth1 as having 172.16.10.38... Shouldn't one of those be eth1:0? 1250326437 M * sannes SKaReCRoW: in the good old days :P 1250326474 M * SKaReCRoW I gotta get this thing working so I can get home and get to sleep before the sun is fully up. :-( 1250326512 M * sannes "ip addr show" shows all addresses 1250326563 M * SKaReCRoW I've read that bringing a guest down will bring the whole interface down with it... Is it possible when the guest is started it's overwriting the hosts routing table? 1250326647 M * sannes In the external ip interface, I think maybe, but where there still are other addresses it should be fine .. not that I have looked at it in recent times :P 1250326692 Q * ensc Remote host closed the connection 1250326733 M * SKaReCRoW Weird, I did "ip addr show" on the host and it only showed 172.16.10.38 for eth1. 172.16.10.138 was not there. 1250326980 M * sannes SKaReCRoW: what kernel version + patch are you running? 1250327076 M * SKaReCRoW Linux onixhost 2.6.26-2-vserver-686 #1 SMP Mon Jul 27 00:18:24 UTC 2009 i686 GNU 1250327139 M * sannes hm, I don't have any compareable systems, so I can't say that not seeing those ips is a good or bad thing ... 1250327171 M * SKaReCRoW I did ifconfig eth1:0 172.16.10.138 on the host and now it's showing up with "ip addr show" and with ifconfig -a 1250327239 M * SKaReCRoW guest with internal IP now seems to be able to access anything in the world EXCEPT my external IPs, but that's not a big deal, there's no reason for the guest to access those anyway. It's just a database server. 1250327267 M * SKaReCRoW But it SHOULD be able to get to my external IPs, so something must still be configured wrong. 1250327352 M * SKaReCRoW Well, it can ping the external IP that's on eth0, but none of my other servers. 1250327457 Q * ghislainocfs2 Ping timeout: 480 seconds 1250328156 M * SKaReCRoW No more ideas? 1250328731 M * SKaReCRoW On reboot the host is not coming up with an IP, but it IS setup properly. Normally the machine wouldn't be rebooted, and it has redundant power supplies, each plugged into a different UPS, so it SHOULD stay up, but in case I ever do need to reboot it, I need the network to come up correctly. Seems the guest is overwriting the hosts IP instead of adding to it. 1250328808 M * SKaReCRoW Also there's no default gateway set on boot. What could be causing this? 1250328847 M * SKaReCRoW I am positive I have the host configured correctly. I've done dozens of Debian Lenny installs, so I'm sure it's right. 1250328999 J * ktwilight_ ~keliew@208.56-240-81.adsl-dyn.isp.belgacom.be 1250329026 Q * ktwilight__ Read error: Connection reset by peer 1250329110 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250329942 J * dothebart ~willi@xdsl-81-173-225-30.netcologne.de 1250330362 Q * tudenbart Ping timeout: 480 seconds 1250331346 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250331472 M * SKaReCRoW Only way to get it working is to login after boot and type "sudo /etc/init.d/networking restart"... I should _NOT_ have to do that. 1250331632 Q * ghislainocfs2 Ping timeout: 480 seconds 1250331746 J * Evet_ ~root@88.254.74.60 1250331851 Q * Evet Ping timeout: 480 seconds 1250332307 Q * ghislainocfs21 Ping timeout: 480 seconds 1250333895 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250335083 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250335271 N * Bertl_zZ Bertl 1250335275 M * Bertl morning folks! 1250335384 M * Bertl SKaReCRoW: sounds like a debian oddity/bug 1250335457 Q * ghislainocfs2 Ping timeout: 480 seconds 1250336091 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250336456 J * geb ~geb@earth.gebura.eu.org 1250336467 Q * ghislainocfs21 Ping timeout: 480 seconds 1250337441 J * dna ~dna@55-197-103-86.dynamic.dsl.tng.de 1250337890 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250338195 Q * ghislainocfs2 Ping timeout: 480 seconds 1250338539 M * theocrite 10:33 < SKaReCRoW> I was able to get out with the guests when I first set them up, but now they don't work. I can't imagine what I might have changed to stop them from getting out. 1250338553 M * theocrite oop 1250338557 M * theocrite sorry 1250339152 Q * ghislainocfs21 Ping timeout: 480 seconds 1250339290 Q * scientes Ping timeout: 480 seconds 1250339835 M * Bertl off for now .. bbl 1250339839 N * Bertl Bertl_oO 1250341679 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1250342713 Q * bragon Remote host closed the connection 1250343837 Q * pmenier Quit: Konversation terminated! 1250343931 J * ensc ~irc-ensc@77.235.160.26 1250344233 N * Bertl_oO Bertl 1250344236 M * Bertl back now ... 1250345611 Q * SKaReCRoW Ping timeout: 480 seconds 1250346269 J * weincunn ~iurewhhf@88-105-241-51.dynamic.dsl.as9105.com 1250346358 M * weincunn Hello all. I've tried the vs2.3.0.36.14-grsec2.1.14 patch (to try and protect against the latest Linux vuln), but I get a lot of segfaults with it. Is this known about? 1250346398 M * Bertl I'd suggest to be carefull with the grsec patches 1250346417 M * weincunn Well, the thing is that there isn't a Vserver patch for a non-vulnerable kernel 1250346427 M * weincunn So it's the best way I can think to defend against it. 1250346427 M * Bertl always make sure to grab the latest, and if in doubt better stay with mainline (i.e. Linux-VServer without grsec) 1250346572 M * weincunn The advisory says that versions affected are "Linux 2.6, from 2.6.0 up to and including 2.6.30.4". 1250346602 M * weincunn And the latest stable is 2.6.22.19 1250346648 M * Bertl yes, and the 'fix' is kind of trivial, i.e. you can add it without any issues to any kernel version 1250346655 M * weincunn Is it? 1250346661 M * Bertl (we probably add it on the next round) 1250346670 M * Bertl yes, it is a one line change 1250346692 M * Bertl but, inside a Linux-VServer guest, you are not affected anyways 1250346697 M * weincunn OK, so I should run with 2.6.22.19 + manual patch + vs2.2.0.7 1250346713 M * Bertl should work fine, yes 1250346724 M * weincunn Oh really? I assumed that if the problem was in the host kernel, it would be exposed via the guests 1250346795 M * weincunn As guest kernel = host kernel. 1250346827 M * Bertl yes, but the problem is with non-ip protocols 1250346835 M * weincunn Yes, I read that 1250346838 M * Bertl exotic protocols like IPX or apple talk 1250346842 M * weincunn IPX, Bluetooth, IRDA, etc 1250346848 M * Bertl inside a guest, you ar elimited to IP protocols 1250346852 M * Bertl *are 1250346852 M * weincunn Aaah. 1250346868 M * weincunn And I only run SSH on a non-standard port on the host anyway 1250346877 M * Bertl so no real danger there 1250346890 M * weincunn And I compile the kernel quite tightly. 1250346917 M * weincunn What's the problem with Grsec then? Are you phasing out support for it? 1250346963 M * Bertl we never had 'official' support for grsec, harry is maintaining the patches every now and then (kind of on demand, event driven) because a lot of folks seem to 'want' grsec 1250346994 M * Mr_Smoke weincunn: FWIW, 2.2.0.7 works fine with grsec. 1250347004 M * Mr_Smoke Been using it in production for ... 1250347005 M * Bertl in my opinion, grsec is not really a big benefit to a Linux-VServer setup, and it definitely is not worth the instability it brings 1250347016 M * Mr_Smoke Months :) 1250347038 M * Bertl nevertheless, there a patches and setups which work flawlessly with grsec patched Linux-VServer kernels 1250347050 M * weincunn Bertl, perhaps that opinion comes from knowing how Vserver handles "bad" people in guests.... 1250347064 M * Bertl it seems all to depend on the config and the actual grsec patch 1250347191 M * weincunn One other problem - my filesystem seems to be a little confused (probably from the segfault/hang problem earlier). I've fscked everything as much as I can remotely, but I get this problem: 1250347196 M * weincunn #vserver foo start 1250347199 M * weincunn vsysctl: open("."): Permission denied 1250347212 M * weincunn The perms look absolutely fine on everything. 1250347236 M * Bertl that looks more like a config/util-vserver issue 1250347256 M * Bertl but maybe just a barrier flag in the wrong place :) 1250347263 M * weincunn Yes, it could be that. 1250347275 M * weincunn I get this: 1250347277 M * weincunn Filesystem "cciss/c0d0p2": Disabling barriers, not supported by the underlying device 1250347288 M * weincunn And : vxW: [�vsysctl�,2062:#1235|1235] denied access to f75ab218[#211,180546404] �/home/vservers/foo 1250347363 M * weincunn The "underlying device" always supported them in the past! :) 1250347446 M * Bertl check that the barrier for /home/vservers/foo is not set, and /home/vservers has it 1250347479 M * weincunn I think it was /home/vservers/foo/.. or something - you advised me about this before 1250347592 M * Bertl yep, but not /home/vservers/foo (check that) 1250347651 M * weincunn setattr --barrier /home/vservers/foo/.. is the command I run in /etc/conf.d/local.start 1250347918 M * Bertl check with showattr /home/vservers/foo 1250347978 M * weincunn http://pastebin.ca/1530545 1250347988 M * weincunn That's from the --debug output of starting the VM 1250348018 M * weincunn The dir and subdirs are ----bui- 1250348027 M * weincunn Apart from fastboot which is -ui- 1250348072 M * weincunn /home/vservers/ is ----Bui- btw 1250348087 M * Bertl looks good 1250348179 M * Bertl http://irc.13thfloor.at/LOG/2007-09/LOG_2007-09-05.txt @1188994169 1250348194 M * Bertl i.e. check that your guest tagging is intact and correct 1250348208 M * weincunn 2 secs 1250348239 M * weincunn Hmm 1250348249 M * weincunn Do I use tag/tagxid? 1250348259 M * weincunn Not really sure what that is. 1250348288 M * weincunn Perhaps (compiling the new kernel) I've enabled it without knowing. 1250348294 M * weincunn Let me check menuconfig 1250348335 M * weincunn (X) UID24/GID24 - is that it? 1250348366 M * Bertl yep, but your filesystem needs to be mounted with tagging enabled (tagxid, tag flag) 1250348383 M * weincunn /home type xfs (rw,noatime,prjquota) 1250348406 M * Bertl is that from /proc/mounts ? 1250348416 M * weincunn Nope. 2 secs 1250348431 M * weincunn /home xfs rw,noatime,prjquota 0 0 <-- that is. 1250349318 Q * ensc Remote host closed the connection 1250349410 M * weincunn Any ideas, Bertl? Shall I try changing the tags anyway/ 1250349415 M * weincunn ? 1250349502 M * weincunn Hm, just lots of "Invalid arguments" 1250349571 M * Bertl nah, no tagging enabled means no tags to be changed 1250349773 M * weincunn I've got to go now. But I'm a bit stuck without it 1250349780 M * weincunn Back later... 1250349785 Q * weincunn Quit: Leaving 1250350119 J * mib_p53mbcvu 769ba696@webchat.mibbit.com 1250350127 Q * mib_p53mbcvu 1250350566 J * julius ~chatzilla@schwartzenberg.xs4all.nl 1250350569 N * julius Z_God 1250350670 M * Z_God I'm running vserver on debian lenny, but I don't see any IPv6 addresses, I understand IPv6 is supported in the version included with lenny, do I need to enable smth specific to get ipv6 to work inside my vservers? 1250350766 M * Mr_Smoke What's your full kernel version ? 1250350799 M * Mr_Smoke (uname -r) 1250350818 M * Z_God 2.6.26-2-vserver-amd64 1250350883 M * Mr_Smoke Huh, no vserver version info. Nice. 1250350903 M * Mr_Smoke Did you aactually attribue IPv6 addresses to the guests ? 1250350933 M * Z_God according to http://linux-vserver.org/Installation_on_Debian I should have version 2.3.0.35 1250350933 M * Mr_Smoke Also, I seem to recall that the kernel might support IPv6 in the *host* but not in the *guest* 1250350937 M * Mr_Smoke Oh 1250350945 M * Mr_Smoke If it's a devel branch then indeed IPv6 should be included 1250350956 M * Z_God should I just specify an IPv6 address with --ip? 1250350977 M * Z_God what if I would want both ipv4 and ipv6? can I specify multiple IPs? 1250351001 M * Mr_Smoke Yes 1250351022 M * Mr_Smoke You can do it live with naddress and offline in the vserver conf dir 1250351031 M * Z_God ok :) 1250351062 M * Z_God and one more question I had, because I still don't fully understand how networking works 1250351107 M * Z_God is it indeed possible to specify the same IP the host interface already has and then let applications both inside and outside the vserver bind to it? 1250351187 M * Mr_Smoke Hm I doubt that, but I haven't tried 1250351214 M * Mr_Smoke Thing is, when you assign an IP to the guest's interface, it will also come up on the host's interface (at least that's how it's done in 2.2) 1250351280 M * Mr_Smoke So technically, I suppose you could have applications binding to that IP both inside the guest and outside 1250351315 M * Mr_Smoke And then the kernel would complain as usual if you'd try to bind twice on the same port 1250351319 M * Mr_Smoke Yep, that sounds alright :) 1250351335 M * Z_God yes, of course on different ports :) 1250351345 M * Mr_Smoke And it works, i've got that on one of my machines actually 1250351349 M * Mr_Smoke Just couldn't remember :p 1250351378 M * Z_God the issue is that I also have only one single ipv6 address and port forwarding for ipv6 is not available yet I think 1250351419 M * Z_God but this would be perfect :) 1250351522 M * Mr_Smoke Huh ? 1250351524 M * Z_God now I have another problem though, I copied my vserver (with the dupvserver command), but I can only start one of them at the same time 1250351528 M * Mr_Smoke Only 1 IPv6 ? 1250351545 M * Z_God yep, I guess it'll change in the future 1250351546 M * Mr_Smoke How come ? 1250351571 M * Z_God I'm not the network admin, we have a server hanging in a co-lo space 1250351571 M * Mr_Smoke I mean the whole point of IPv6 is there are so many available you can get as many as the average population of a large country ... 1250351580 M * Z_God and it just get assigned one address 1250351595 M * Mr_Smoke I'm not even a professional and I have 2 /48 and 1 /64 1250351600 M * Z_God they're still working on assigning address spaces to people 1250351601 M * Mr_Smoke DUH. 1250351632 M * Z_God yep, my parents also got a /48 at home :) 1250351641 A * Wonka wants Mobile IPv6 1250351659 M * Mr_Smoke Hm yeah, that should be fun :) 1250351680 M * Mr_Smoke and hopefully less tedious than VPN'ing 1250351715 M * Wonka i'd want encryption anyway 1250351725 M * Z_God but when I try to start a 2nd vserver, I now get: vcontext: vc_ctx_create(): File exists 1250351731 M * Wonka end-to-end opportunistic ipsec would be nice 1250351738 M * Bertl Z_God: yes, you can assign the 'host' ip (actually all IPs are host IPs) to a guest 1250351747 M * Z_God ok :) 1250351762 M * Bertl Z_God: but usually, you assign a private IP to the guest, and S/DNAT certain ports 1250351764 M * Z_God Wonka: important things should already use SSL now I think 1250351775 M * Wonka Z_God: still. 1250351784 M * Bertl Z_God: did you specify a unique context id for each guest? 1250351796 M * Wonka Z_God: DNS does not. And I don't want everyone to see which whom i make SSL connections. 1250351798 M * Z_God Bertl: yep I read that on the site, but as I said I think it won't work so well with IPv6 1250351803 M * Z_God no? 1250351821 M * Wonka Z_God: bad enough to have them see to which IPs I talk 1250351842 M * Z_God ipsec won't solve that 1250351844 M * Bertl Z_God: well, that's what the vc_ctx_create() tries to tell you :) 1250351901 M * Z_God alright, I'll read up on context ids :) 1250351954 M * Wonka Z_God: it will at least hinder the MITM to see what protocol I talk, because they only see ipsec esp 1250351983 M * Bertl not much to read up on .. just assign a unique one to each guest, avoid 0 and 1 (they are special) and stay below 49151 1250352018 M * Z_God what is the purpose of these IDs? 1250352026 M * Z_God Wonka: true :) 1250352061 M * Bertl they are the unique identifiers for the process context (there is a similar one for the network) 1250352104 M * Mr_Smoke Z_God: I tend to use 100-255 id's, so then I can map them to IP address. Ie guest with xid 154 is 192.168.42.154 for example 1250352113 M * Mr_Smoke And has IP 2001:758:1337::154 1250352118 M * Mr_Smoke It's quite handy 1250352156 M * Z_God but what's wrong with a name? I read there are also dynamic context IDs, but they are not recommended 1250352190 M * Mr_Smoke Z_God: guests have *both* a name and a context ID 1250352208 M * Bertl Z_God: did you do some programming at some point? 1250352226 M * Z_God yes, I understand that internally a number is more handy to work with 1250352255 M * Z_God but why would a user need to care about it? 1250352258 M * Bertl good, so the number is the 'unique' part, and the name can be assigned, sounds reasonable? 1250352268 M * Z_God yep 1250352276 M * Bertl the user doesn't .. recent util-vserver assigns the numbers for you 1250352282 M * Z_God ok :) 1250352310 M * Bertl it makes them system/host unique .. unless you specify them manually with --context 1250352344 M * Bertl (which makes sense if you want some more control over it, e.g. for cluster wide unique ids) 1250352399 M * Z_God yep, I see 1250352423 M * Z_God I'd expect them to be generated dynamically, because that would seem to make migrations easier 1250352437 M * Z_God I'll have to go now, thanks a lot for all the help! 1250352588 M * Bertl np 1250356083 J * TobiX_ tobias@zoidberg.org 1250356181 Q * TobiX Ping timeout: 480 seconds 1250357762 J * ktwilight__ ~keliew@97.3-240-81.adsl-dyn.isp.belgacom.be 1250357958 Q * Piet Ping timeout: 480 seconds 1250358195 Q * ktwilight_ Ping timeout: 480 seconds 1250358353 J * Elton02622 ~Delphi@189.82.173.67 1250358841 Q * Elton02622 Read error: Connection reset by peer 1250359608 Q * geb Ping timeout: 480 seconds 1250360502 J * ktwilight_ ~keliew@209.255-64-87.adsl-dyn.isp.belgacom.be 1250360918 Q * ktwilight__ Ping timeout: 480 seconds 1250362426 J * Piet ~piet@659AABSZ4.tor-irc.dnsbl.oftc.net 1250363008 J * ensc ~irc-ensc@77.235.160.26 1250363703 J * geb ~geb@earth.gebura.eu.org 1250365883 Q * larsivi Ping timeout: 480 seconds 1250365908 J * larsivi ~larsivi@70.84-48-63.nextgentel.com 1250366923 Q * sannes Ping timeout: 480 seconds 1250369727 J * fancy ~phati@host23-210-dynamic.31-79-r.retail.telecomitalia.it 1250369893 Q * fancy 1250370136 J * scientes ~scientes@174-21-104-37.tukw.qwest.net 1250370946 Q * dna Quit: Verlassend 1250371538 Q * saulus Ping timeout: 480 seconds 1250371742 J * saulus ~saulus@c207060.adsl.hansenet.de 1250373615 Q * ghislainocfs2 Quit: Leaving. 1250375499 Q * bonbons Quit: Leaving 1250376427 J * tudenbart ~willi@xdsl-213-196-253-20.netcologne.de 1250376845 Q * dothebart Ping timeout: 480 seconds