1327111430 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1327133216 J * Marbug ~Marbug@83.101.67.3
1327136180 Q * ensc|w Remote host closed the connection
1327136190 J * ensc|w ~ensc@www.sigma-chemnitz.de
1327138087 J * bonbons ~bonbons@2001:960:7ab:0:a4e0:5bce:a17:e9b
1327141529 J * fisted ~fisted@xdsl-87-78-219-73.netcologne.de
1327141735 Q * fisted_ Ping timeout: 480 seconds
1327147822 J * sannes ~ace@cm-84.209.106.118.getinternet.no
1327150747 Q * Aiken Remote host closed the connection
1327159288 N * ensc Guest75
1327159298 J * ensc ~irc-ensc@p54ADFAFB.dip.t-dialin.net
1327159708 Q * Guest75 Ping timeout: 480 seconds
1327163418 Q * fisted Remote host closed the connection
1327163432 J * fisted ~fisted@xdsl-87-78-219-73.netcologne.de
1327164603 J * sweil ~stefan@p5086F706.dip.t-dialin.net
1327164623 Q * sweil Remote host closed the connection
1327164628 J * sweil ~stefan@p5086F706.dip.t-dialin.net
1327165151 J * MikePer ~saradoc@91-115-213-67.adsl.highway.telekom.at
1327165427 M * MikePer Hello. I am new to vserver and I wonder how to set the networking interface for a new vserver. I gave the new guest eth0:0 and a different IP than the host has and I can ping it but I cannot see eth0:0 anywhere on the host. And the networking from guest seems to be flakey, if I do something the networking will stop working.
1327165537 M * MikePer Host is debian squeeze, guest is the same. I read some FAQs but it seems that I don't have to set something special, according to the vserver FAQ.
1327166769 M * Bertl_oO well, first, what kernel/util-vserver do you use?
1327166782 M * Bertl_oO (debian is known for broken kernels and outdated tools)
1327167638 Q * LuckyLuke Ping timeout: 480 seconds
1327167930 Q * sweil Remote host closed the connection
1327168655 M * MikePer Well... kernel 2.6.32, util-vserver is 0.30.216, debianized. I am not sure what vserver-debiantools does though, it seems outdated?
1327168686 M * MikePer At least I read that somewhere so I didn't use newvserver but vserver build...
1327168905 J * cehteh ~ct@HSI-KBW-085-216-123-195.hsi.kabelbw.de
1327168958 M * Bertl_oO yeah you should definitely get rid of vserver-debiantools
1327168980 M * Bertl_oO at best it will not work, at worst it will mess up your system completely
1327169005 M * Bertl_oO note that 0.30.216 is not released (yet), so that's another debian oddity
1327169020 M * Bertl_oO anyway, how did you configure your guest IP?
1327169174 M * MikePer well... I just did vserver build --hostname --netdev --interface and so on.
1327169234 M * Bertl_oO okay, please provide that line for us to look at, feel free to anonymize IP infos if relevant
1327169444 M * MikePer straight from the docs:
1327169447 M * MikePer vserver vserver2 build -m debootstrap --hostname vserver1.privat --interface eth0:192.168.0.180/24 -- -d squeeze -m http://ftp.at.debian.org/debian
1327169479 M * MikePer but I tried to change the device to eth0:0 and the IP to 192.168.0.182 and it works too
1327169493 M * Bertl_oO okay, and where do you have the idea that there should be an eth0:0?
1327169531 M * MikePer ah no, eth0:2
1327169549 M * Bertl_oO same question for eth0:2 :)
1327169590 M * MikePer I had the same question and tried it to see if it would stop working but... :)
1327169614 M * Bertl_oO btw, I presume it will sooner or later confuse the hell out of you if you name your 'vserver2' 'vserver1' :)
1327169631 M * Bertl_oO anyway, the IP was configured (by you) as secondary IP
1327169639 M * Bertl_oO you will see it with 'ip a l'
1327169643 M * MikePer ah yes, sorry, it was vserver2
1327169666 M * Bertl_oO ifconfig doesn't see secondaries, because it was superceeded by iproute2 about 10 years ago
1327169697 M * MikePer oh
1327169737 M * MikePer ok... is eth0 correct for the guest or do I have to use another dev?
1327169744 M * MikePer I guess it should be eth0 then
1327169770 M * Bertl_oO eth0 is probably fine, but I don't know the details of your network setup
1327169810 M * Bertl_oO now regarding the 'network flakey' part, what effects/problems do you see?
1327169816 M * MikePer only one nic, local address
1327169828 M * Bertl_oO then it is definitely fine
1327169831 M * MikePer nothing special, no router
1327169995 M * MikePer Well, I am ssh-ing to the host box. When I start vserver2 (now changed back to dev eth0) and enter it and for instance do 'apt-get install joe' my ssh session breaks down.
1327170060 M * Bertl_oO breaks down means?
1327170077 M * Bertl_oO you get logged out or you are stuck or what?
1327170103 M * MikePer stuck and aborted
1327170148 M * Bertl_oO i.e. nothing happens, you then abort the connection, yes?
1327170228 M * MikePer I am using putty, I get a 'Network error: Software caused connection abort'
1327170287 M * Bertl_oO that sounds more like a broken setup
1327170323 M * MikePer I had the same feeling
1327170513 M * MikePer even if I do 'apt-get update' the ssh hickups for few seconds
1327170529 M * Bertl_oO well, I'd try with a direct console/terminal and/or a linux machine as client
1327170554 M * Bertl_oO it is rather unlikely that this is related to Linux-VServer and/or the guest setup, although it could be a debian bug
1327170562 M * MikePer can do that. I can ssh to another linix box and ssh from there if you think it would help
1327170578 M * Bertl_oO give it a try
1327170609 M * Bertl_oO the 192.168.0.180 is an otherwise unused IP you assigned to the guest, yes?
1327170655 M * MikePer yes
1327170765 M * MikePer huh...
1327170773 M * MikePer it seems to work now
1327170832 M * Bertl_oO so it's probably more your windows client which gets confused (for whatever reason)
1327170861 M * MikePer strange
1327170902 M * MikePer indeed it seems you are right
1327170979 M * MikePer I never encountered problems with putty so far
1327171027 M * MikePer oh besides, is it possible to use dhcp for the guest?
1327171040 M * Bertl_oO yes and no
1327171064 M * Bertl_oO you can use dhcp, but you have to script it (on the host) to acquire and manage the IP
1327171082 M * Bertl_oO then you simply assign that IP to the guest (which could happen dynamically)
1327171296 M * MikePer I see
1327171332 M * MikePer oh I just see that starting apache2 isn't that easy too, cant bind to 0.0.0.0:80
1327171340 M * Bertl_oO so for example, if your dhcp server supports client ids, just request another IP via adifferent client IP
1327171367 M * Bertl_oO this (apache) is most likely because you already have apache running on the host, and it isn't restricted there
1327171387 M * Bertl_oO in return, the host apache will bind _all_ IPs, including those assigned to the guest
1327171391 M * MikePer ah I see! I have to restrict it to the primary interface
1327171403 M * Bertl_oO to host IPs, yes
1327171404 M * MikePer eh, primary IP
1327171423 M * MikePer I see, I see...
1327171462 N * Bertl_oO Bertl
1327171480 M * MikePer well, thank you for your help so far! I might be coming back soon with some other questions, but I hope not
1327171508 M * Bertl you're welcome! no problem ... feel free to hang around whenever you like
1327171904 M * MikePer but it's quite strange though... if I use putty to ssh to the host and ssh from there to guest it works, but if I don't ssh to guest but do vserver enter I am disconnected after apt-get update...
1327171926 M * MikePer But oh well, I don't care if it's a putty problem
1327172073 M * Bertl could as well be an apt-get problem
1327172109 M * Bertl note that 'vserver guest enter' is not identical to ssh-ing into the guest
1327172112 M * MikePer how? apt-get shouldn't be aware of how I call it
1327172125 M * Bertl environment?
1327172145 M * Bertl like for example, your terminal setting, or similar
1327172199 M * MikePer well ok, but shouldn't I have experienced that problem earlier with one of my other debian queeze boxes?
1327172207 M * MikePer squeeze
1327172361 M * MikePer oh I see the problem now... it don't work with vserver enter...
1327173616 M * Bertl could be, different environment there too, so if apt-get dislikes it for whatever reason and crashes ...
1327174228 M * Bertl http://paste.linux-vserver.org/20725
1327174271 M * Bertl i.e. I just installed a similar guest (same command you gave me), and ran apt-get on enter, which worked fine
1327174509 M * Bertl note that this was done with util-vserver-0.30.216-0.pre3004 on a recent kernel
1327179464 M * MikePer But you didn't use putty to ssh to host, did you?
1327180276 M * Bertl nope, no windows here
1327180483 M * MikePer Huh, my vserver-build seems not to know the --arch option
1327180557 M * MikePer oh...
1327180833 M * Bertl it is an option to the debootstrap actually
1327180881 M * Bertl I have to add it because my distros use x86_64 (instead of amd64)
1327180897 M * MikePer yes, I saw it
1327180915 M * MikePer I tried that too but: 'W: Failure trying to run: chroot /etc/vservers/.defaults/vdirbase/vserver1 mount -t proc proc /proc'
1327180935 M * MikePer Interesting, did work without the arch option
1327180944 M * Bertl if your host is 64bit, no need to specify it
1327180967 M * Bertl if your host is 32bit, no point in specifying it, as a 64bit guest won't work
1327181003 M * MikePer ah, but 32 bit guests in 64 bit host work?
1327181040 M * Bertl as long as the kernel supports 32bit executeables, yes
1327181062 M * MikePer hrm, I should install a 64 bit kernel...
1327181416 M * Bertl probably, simplifies a lot of things
1327185491 J * fisted_ ~fisted@xdsl-87-78-220-7.netcologne.de
1327185534 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1327185841 Q * fisted Ping timeout: 480 seconds
1327185933 Q * sannes Remote host closed the connection