This is what we've got
Linux svr26.xxx 2.6.15-1.1833_FC4.vs2.0.2.0.rc10.1 #1 Thu Mar 2 12:57:13
EST 2006 i686 athlon i386 GNU/Linux
util-vserver-devel-0.30.210-4.fc4
util-vserver-build-0.30.210-4.fc4
util-vserver-lib-0.30.210-4.fc4
util-vserver-legacy-0.30.210-4.fc4
On Thursday 23 March 2006 14:43, John Lyons wrote:
This is what we've got
Linux svr26.xxx 2.6.15-1.1833_FC4.vs2.0.2.0.rc10.1 #1 Thu Mar 2
12:57:13 EST 2006 i686 athlon i386 GNU/Linux
util-vserver-devel-0.30.210-4.fc4
util-vserver-build-0.30.210-4.fc4
util-vserver-lib-0.30.210-4.fc4
This is strange. Normally, a vserver is bound to one IP address and even a
bind to 0.0.0.0 should be mapped to this single IP address.
Agreed, we've been runnning vservers since v0.3 and never had a problem like
this.
What's the result of a netstat -tpln and chcontext --xid 1
netstat -tpln
On Thu, Mar 23, 2006 at 05:22:31PM -, John Lyons wrote:
ipv4root: 835f45c3/00ff 017f/00ff
ipv4root_bcast:
why do you add 127.0.0.1 to the guest config?
I didn't think we did but now you mention it, I've found that in the
loopback interface on each vs.
Having