From: David (needoo_at_excite.com)
Date: Mon 02 Feb 2004 - 11:11:42 GMT
Hi!
I'm posting a bug report considering broadcast addresses and the config file for vservers.
The problem exists if you want to assign a vserver a broadcast address other than the default. Normally, you would set it in the config file, but doing so does nothing.
Here's /proc/self/status before setting the broadcast to 255.255.255.255 (IP is 192.168.1.100) :
grep ipv4root /proc/self/status
ipv4root: 6401a8c0/00ffffff
ipv4root_bcast: ff01a8c0
ipv4root_refcnt: 20
...and after setting IPROOTBCAST=255.255.255.255, and restarting the vserver:
grep ipv4root /proc/self/status
ipv4root: 6401a8c0/00ffffff
ipv4root_bcast: ff01a8c0
ipv4root_refcnt: 20
it's the same.
The problem this bug raises is, if you want to set your broadcast address, you'll have to do it with chbind. That works fine from the main server with the --bcast option (but it's really pointless running chbind on an existing vserver's IP), and it also works from within the vserver.
This has a huge disadvantage though, because running chbind requires special privileges (CAP_NET_ADMIN), which normally you woulnd't want to give away.
The bug was discovered by running the UDP server avp2linux (that's available at: http://www.avpnation.com/main.asp?page=download&file=265)
--Dave (needoo_at_excite.com)
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver