1204762066 Q * harry Ping timeout: 480 seconds 1204762603 Q * xdr Ping timeout: 480 seconds 1204764112 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1204765543 J * xdr ~xdr@141-173-96-87.cust.blixtvik.se 1204767751 J * doener_ ~doener@i577B92DE.versanet.de 1204767949 J * harry ~harry@d54C363EF.access.telenet.be 1204768157 Q * doener Ping timeout: 480 seconds 1204768933 Q * tam Remote host closed the connection 1204769316 J * padde ~padde@patrick-nagel.net 1204771439 Q * nenolod Ping timeout: 480 seconds 1204774174 Q * balbir Ping timeout: 480 seconds 1204774842 J * balbir ~balbir@122.167.210.53 1204777552 M * Bertl okay, off to bed .. have a good one everyone! 1204777556 N * Bertl Bertl_zZ 1204777567 Q * fatgoose Quit: fatgoose 1204779748 J * tam ~tam@gw.nettam.com 1204780384 Q * balbir Ping timeout: 480 seconds 1204780973 Q * nkukard Ping timeout: 480 seconds 1204781724 J * nkukard ~nkukard@196.212.73.74 1204785860 J * balbir ~balbir@59.145.136.1 1204789113 J * Slydder ~chuck@194.59.17.53 1204789149 M * Slydder morning all 1204789570 J * JonB ~NoSuchUse@77.75.164.169 1204789986 J * gebura ~gebura@77.192.186.197 1204790051 M * gebura hi 1204790181 Q * JonB Quit: This computer has gone to sleep 1204791662 J * dna ~dna@134-193-dsl.kielnet.net 1204792450 J * maddoc maddoc@social.ostruktur.com 1204792504 J * JonB ~NoSuchUse@77.75.164.169 1204793614 M * maddoc Was http://www.debian.org/security/2008/dsa-1494 fixed at 20080212 if you're using the vserver-grsec-patch? And why is the patch now called patch-2.6.22.19-vs2.2.0.6-grsec2.1.11-20080304.diff, even though there's no entry in the changelog for 20080304? 1204793646 M * harry because i didn't do a changelog there 1204793680 M * harry you want a changelog? 1204793689 M * harry it's just an update from 2.6.22.18 1204793735 M * harry there you go... your changelog ;) 1204793757 M * maddoc Hehe, k. 1204793889 M * maddoc But the first question? Was it fixed back then? 1204794060 M * harry it was fixed in 2.6.22.18 1204794065 M * maddoc Nice. 1204794089 M * harry http://people.linux-vserver.org/~harry/patch-2.6.22.18-vs2.2.0.6-grsec2.1.11-20080212.diff 1204794110 M * harry it was fixed there... and also for 2.6.22.19;) 1204794207 J * virtuoso ~s0t0na@ppp91-122-138-63.pppoe.avangarddsl.ru 1204794244 M * maddoc Good. :-) Was just thinking if I needed to upgrade the servers who run 2.6.22.18. 1204794622 Q * virtuoso_ Ping timeout: 484 seconds 1204795285 M * harry ah, no :) 1204795285 Q * vasko Read error: Connection reset by peer 1204795300 J * vasko ~vasko@unreal.rainside.sk 1204795300 A * vasko is gone. Gone since Sun Mar 2 23:50:00 2008 1204795710 J * pmenier ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr 1204796384 Q * balbir synthon.oftc.net oxygen.oftc.net 1204796384 Q * nkukard synthon.oftc.net oxygen.oftc.net 1204796440 J * fosco fosco@konoha.devnullteam.org 1204796671 J * balbir ~balbir@59.145.136.1 1204796671 J * nkukard ~nkukard@196.212.73.74 1204796938 Q * vasko Quit: Time wasted on IRC: 3 days 11 hours 4 minutes 47 seconds 1204796945 J * vasko ~vasko@unreal.rainside.sk 1204797615 Q * jsambrook Quit: Leaving. 1204797653 J * friendly12345 ~friendly@ppp121-44-240-71.lns4.mel4.internode.on.net 1204797693 J * nenolod ~nenolod@ip70-189-74-69.ok.ok.cox.net 1204797794 J * jsambrook ~jsambrook@aelfric.plus.com 1204798179 Q * JonB Quit: This computer has gone to sleep 1204801795 J * ktwilight ~ktwilight@112.96-66-87.adsl-dyn.isp.belgacom.be 1204802033 Q * ktwilight_ Ping timeout: 480 seconds 1204803435 Q * Aiken Remote host closed the connection 1204803881 J * tubb ~tobi@e177041199.adsl.alicedsl.de 1204804319 Q * pmenier Quit: Konversation terminated! 1204806377 Q * tubb Quit: Verlassend 1204807293 Q * balbir Ping timeout: 480 seconds 1204807803 J * xxxx ~Nuhks@bl7-149-44.dsl.telepac.pt 1204808232 Q * Linus Ping timeout: 480 seconds 1204808234 Q * friendly12345 Quit: Leaving. 1204808368 J * chigital ~chigital@91.90.144.102 1204808452 J * ftx ~ftx@dslb-084-062-252-132.pools.arcor-ip.net 1204812765 Q * FireEgl Quit: Leaving... 1204814302 Q * dowdle Remote host closed the connection 1204814307 J * dowdle ~dowdle@scott.coe.montana.edu 1204814439 J * JonB hidden-use@192.38.9.151 1204814873 J * ste ~stejules@dslb-084-056-177-102.pools.arcor-ip.net 1204814879 M * ste hello 1204814920 J * hparker ~hparker@linux.homershut.net 1204814920 M * JonB hi 1204815101 M * hparker Morning 1204815113 Q * ste Read error: Connection reset by peer 1204815314 J * ste ~stejules@dslb-084-056-177-102.pools.arcor-ip.net 1204815680 M * ste hello 1204815786 Q * ste Quit: Verlassend 1204815824 J * ste ~stejules@dslb-084-056-177-102.pools.arcor-ip.net 1204816721 J * yarihm ~yarihm@p54BD71F3.dip.t-dialin.net 1204818188 Q * JonB Quit: Leaving 1204818196 J * JonB hidden-use@192.38.9.151 1204818379 Q * mick_work Ping timeout: 480 seconds 1204818542 N * Bertl_zZ Bertl 1204818547 M * Bertl morning folks! 1204818562 M * hparker Morning Bertl 1204818608 M * gebura morning 1204818710 M * Bertl is freenode dead again? (or what's up there?) 1204818723 Q * JonB Quit: This computer has gone to sleep 1204818782 M * hparker I'm attached still 1204818786 M * gebura freenode work fine, i am connected 1204818800 Q * Slydder Quit: Leaving. 1204818812 M * gebura nothing else interesting to say , sorry :) 1204818841 M * Bertl hmm, obviously not for me .. I get timeouts on irc.freenode.net [213.92.8.4] port 6667 1204818914 M * gebura must be a problem from your operator 1204818918 M * gebura try a traceroute 1204819016 M * Bertl well, not that important atm :) will try later ... 1204819085 M * Bertl it seems to be a routing loop in washington ... don't ask me why I get that IP (from Austria :) 1204819169 M * gebura haha i didn't know the better route to us or europe from .at was in autralia :) 1204819176 M * gebura that the... 1204819259 N * DoberMann[ZZZzzz] DoberMann 1204819516 A * ard6 uses ipv6 1204819528 M * ard6 that lessens the amount of servers you can get on :-) 1204820058 J * mick_work ~clamwin@adsl-068-157-089-099.sip.bct.bellsouth.net 1204820959 Q * mick_work Ping timeout: 480 seconds 1204821703 J * mick_work ~clamwin@adsl-068-157-089-099.sip.bct.bellsouth.net 1204821867 Q * nenolod Quit: i'm always up for some rough cybersex on sundays 1204822151 J * nenolod ~nenolod@ip70-189-74-69.ok.ok.cox.net 1204822870 Q * gebura Quit: Quitte 1204824157 J * JonB hidden-use@192.38.9.151 1204824267 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1204824651 A * xxxx hi :) 1204824710 M * JonB hi 1204824847 N * DoberMann DoberMann[PullA] 1204824954 M * cehteh # vserver devel stop -v 1204824954 M * cehteh A timeout occured while waiting for the vserver to finish and it will 1204824954 M * cehteh be killed by sending a SIGKILL signal. The following process list 1204824954 M * cehteh might be useful for finding out the reason of this behavior: 1204824954 M * cehteh ---------------------------------------------------------------------- 1204824955 J * weeti ~weeti@3ecc0014.tietoverkkopalvelut.fi 1204824969 M * cehteh .. kills the whole server, anyone knows the cause of that? 1204824999 Q * yarihm Ping timeout: 480 seconds 1204825015 M * weeti Hello. Is it possible to bind the real interface (like eth0.10) to certain vserver? All the eamples I've seen deal with dummy-adapters 1204825036 M * Bertl weeti: you cannot 'bind' any interface to a guest 1204825051 M * Bertl weeti: but you can assign IP addresses from all kind of interfaces to them 1204825069 J * yarihm ~yarihm@p54BD71F3.dip.t-dialin.net 1204825112 M * weeti Hmm. Ok. how about then from routing point of view, Can I do routing changes in guest to have them reflected back to main kernel? 1204825148 M * Bertl nope, as there is only one kernel running (the 'main' kernel) a guest is not allowed (by default) to do routing setups 1204825149 M * weeti I'm looking for a solution how to virtualize xorp (as it does not have any notion of being aware of logical routers) 1204825162 M * weeti k. 1204825168 M * weeti darn 1204825172 M * Bertl but, you can configure the routing on the host to match your guest's need 1204825215 M * Bertl note: Linux-VServer uses IP isolation, so you are one layer higher than ethernet and friends 1204825227 M * weeti But If i need dynamic routing (mostly multicast routing to be precise) done with two instances of xorp and they cannot be run parallel in same environment. 1204825258 M * Bertl well, they probably will interfere with eachother anyway 1204825275 M * Bertl (unless you do full virtualization of the network stack) 1204825275 M * weeti yep. so i thought first. just trying to avoid using xen/uml/kvm and a way too expensive context-switches between guest and host. 1204825299 M * cehteh mhm 1204825321 J * DLange ~dlange@p57A3115C.dip0.t-ipconnect.de 1204825345 Q * DLange 1204825386 M * weeti but thanks. I can drop vserver from my list of things to decide between :p 1204825411 M * Bertl you're welcome! 1204825430 M * weeti and of course if you happen to know something i've missed .. well ;) 1204825451 M * Bertl for now, I don't have an idea what you are trying to do :) 1204825472 M * weeti run two logical routers in one box 1204825523 M * Bertl how is that supposed to work? what decides what packets are handled by what router? 1204825533 M * weeti like eth0.10 eth0.11 eth1.10 and eth1.11 in one router and eth0.20, eth0.21, eth1.20 and eth2.21 in one. no interaction between those routers and running the usual ospf+bgp+pim 1204825546 M * weeti the interface it is listening decides 1204825566 M * weeti just like they do with cisco and junper and almost every commercial router. concept of vrfs 1204825606 M * Bertl yep, but that's a feature of the network stack of those devices .. but in the near future, Linux kernels will probably get a similar feature 1204825610 M * weeti and because of pim i'm pretty much stuck with xorp which unfortunately is designed to be 'the one and only no virtualization of any kind' -router. 1204825642 M * weeti actually that doesn't need any modifications to current networking stack 1204825642 J * Punkie ~Punkie@goc.coolhousing.net 1204825655 M * Bertl weeti: how so? 1204825666 M * weeti we already have multiple routing tables we can use depending on incoming interface 1204825706 M * weeti so we could create table 2 for all routes originating from lr1 and table 2 for lr2 likewise.. 1204825712 M * Bertl yes, but certain network stack oddities will definitely mess up your setup 1204825720 M * weeti no they wont. 1204825727 M * weeti i've done it with other software already 1204825739 M * weeti many many times in fact :D 1204825742 M * Bertl so you are fine with policy routing then, and that suffices for your purpose? 1204825773 M * Bertl if that is true, you could get it working with Linux-VServer too 1204825776 M * weeti actually only policy that is needed is the one that classfies packets to different routing tables 1204825811 M * weeti Bert1 but if guests are not supposed to edit routing information and moreover how about mfc-related calls... 1204825842 M * Bertl what you need to do in this case is to relay the routing setup commands to the host, which in turn will apply them to the proper tables 1204825851 M * weeti with mfc I'm quite sure that kcurrent kernel cannot handle the task 'in general setup' but if keeping the groups separate that does work. 1204825925 M * weeti so there won't be problem of creating multicast listeners in guests? and also there is no weird restrictions of igmp and such? 1204825995 Q * xxxx Quit: I'll by back 1204826018 M * Bertl multicast works (at least it was reported working) no idea about IGMP 1204826043 M * weeti k. well it is easy enough to test out anyways. 1204826059 M * Bertl but as I said, you would need to relay the routing commands somehow 1204826101 M * weeti vserver concept would be better from my point of view as it means several steps omitted.. (like for example with uml in need to do ethernet bridging between vif and real interface and then that expensive switch between host and guest) 1204826137 Q * chigital Ping timeout: 480 seconds 1204826138 M * weeti Bertl: normal routing commands should not pose problem but mfc related stuff.. well. have to work out something :D 1204826139 M * Bertl yep, that's one reason why Linux-VServer uses IP isolation for services 1204826196 M * weeti k. I'll test it out and let you know 1204826203 M * Bertl please do so 1204826637 M * cehteh Bertl: what process gets named "--------------" (lots of dashes) when shutting a vserver down? some bug? 1204826781 M * Bertl cehteh: I'd say that's a separator line :) 1204826803 M * Bertl cehteh: talk to daniel_hozac, IIRC that is a known issue of (older?) tools 1204826806 M * cehteh looks up in 'top' as --------/0 1204826822 M * cehteh no just fresh install on a hetzner server 1204826834 M * Bertl in top? that sounds interesting 1204826969 M * cehteh well .. i didnt fully figure out because it just freezes while trying to vserver stop 1204827088 M * cehteh how turn i util-vserver debugging on ? 1204827105 A * cehteh does that too rarely, forgotten 1204827113 M * Bertl add --debug (for the tools) 1204827290 J * fatgoose ~samuel@76-10-149-199.dsl.teksavvy.com 1204827475 M * cehteh mhm 1204827844 M * cehteh *freeze* 1204827883 A * cehteh installs a debian vserver kernel 1204828046 J * balbir ~balbir@122.167.182.3 1204828510 M * cehteh doh 1204828516 M * cehteh freezes too 1204828981 Q * JonB Quit: This computer has gone to sleep 1204829056 J * NetAsh ~arturas@client-87-247-101-146.inturbo.lt 1204829076 M * NetAsh hello 1204829197 M * NetAsh I have a question you all are bored to death: what's about 2.6.24.x support 1204829206 M * NetAsh the newest I found 1204829273 M * Bertl what about it? 1204829296 M * NetAsh is the experimental patch http://vserver.13thfloor.at/Experimental/patch-2.6.24-rc7-vs2.2.0.5.0.7-pre.diff 1204829313 M * NetAsh and this one is pretty old 1204829321 M * NetAsh is there anything newer 1204829328 M * Bertl nope, that's the current state 1204829350 M * NetAsh or some svn repository or smth 1204829355 M * NetAsh oh 1204829415 M * NetAsh last time I tried to apply it onto vanila 2.6.24 it failed due one line mismatch 1204829439 M * cehteh be happy .. when you fix it and try to use it youll discover that it is not fully working yet 1204829483 M * NetAsh you ansvered the question I still wanted to ask :D 1204829590 M * NetAsh i just wondered about it, because debian intents to relese "etch and a half" 1204829608 M * NetAsh and they are preparing 2.6.24 kernel updates 1204829666 M * NetAsh and so far vserver flavor of kernels are left out 1204829893 M * Bertl well, I didn't receive any specific request from debian yet 1204829948 M * cehteh hmpfs 1204829975 M * NetAsh I guess debian kernel teem is more understanding and do not bothers you with such questions :D 1204829987 M * cehteh vserver xxx stop seems to kill the host server .. sshd or whatever 1204829998 M * cehteh any idea what might cause this? 1204830014 M * Bertl cehteh: could it be that you are removing your network interface (accidentially, see FAQ) 1204830027 M * cehteh ah 1204830034 M * cehteh good explanation 1204830205 M * cehteh mhm 1204830813 Q * Punkie Quit: Odcházím 1204831132 J * chigital ~chigital@p4FE5FE4A.dip.t-dialin.net 1204831494 J * JonB ~NoSuchUse@77.75.164.169 1204835109 J * worckkak worckkak@host135-72-dynamic.22-79-r.retail.telecomitalia.it 1204835111 P * worckkak 1204835772 J * Piet ~piet@tor.noreply.org 1204836634 J * Julius ~julius@p57B2717C.dip.t-dialin.net 1204837296 J * Aiken ~james@ppp118-208-56-200.lns4.bne1.internode.on.net 1204837531 Q * eyck Remote host closed the connection 1204837563 Q * ste Quit: Verlassend 1204837691 P * NetAsh 1204838036 Q * chigital Quit: Leaving 1204838100 J * eyck L5YnL6QS@nat05.nowanet.pl 1204838718 Q * bonbons Quit: Leaving 1204838988 Q * ftx Remote host closed the connection 1204841824 Q * Julius Quit: Verlassend 1204842237 Q * DuckMaster Remote host closed the connection 1204842258 J * duckx ~Duck@81.57.39.234 1204842665 Q * duckx Remote host closed the connection 1204842680 J * duckx ~Duck@81.57.39.234 1204843675 Q * yarihm Quit: This computer has gone to sleep 1204844496 Q * JonB Quit: This computer has gone to sleep 1204844517 J * dna_ ~dna@134-193-dsl.kielnet.net 1204844896 J * virtuoso_ ~s0t0na@ppp91-122-26-156.pppoe.avangarddsl.ru 1204844920 Q * dna Ping timeout: 480 seconds 1204845018 Q * maddoc Remote host closed the connection 1204845020 J * maddoc maddoc@social.ostruktur.com 1204845153 Q * virtuoso Ping timeout: 480 seconds 1204845168 P * TrueBrain So long and tnx for all the fish 1204845221 J * yarihm ~yarihm@brln-4d051c08.pool.mediaWays.net 1204846912 Q * maddoc Remote host closed the connection 1204846917 J * maddoc maddoc@social.ostruktur.com