Date: Tue, 09 Sep 2014 06:40:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-rc@FreeBSD.org Subject: [Bug 186841] rc.conf ifconfig syntax for binding ip-ranges broken [regression] Message-ID: <bug-186841-4805-8FYT6iIH70@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-186841-4805@https.bugs.freebsd.org/bugzilla/> References: <bug-186841-4805@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186841 Hiroki Sato <hrs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Patch Ready Assignee|freebsd-rc@FreeBSD.org |hrs@FreeBSD.org --- Comment #7 from Hiroki Sato <hrs@FreeBSD.org> --- Created attachment 147097 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147097&action=edit A patch to make the limit user-configurable and bump the default value up to 2048. _IPEXPANDMAX was not intended for a hard limit of this functionality, just a safety-belt though I did not add it as a user-configurable knob. The reason why I added it is that a misconfiguration can unexpectedly generate a very very large number of addresses, especially in IPv6 because range specification handling in a shell-script is not so robust. A typo in IPv6 address can generate over 2^64 addresses. So, the moot point is whether this limit is still problematic even when it is user-configurable and an appropriate warning message is displayed. My proposed patch is attached. With this patch, one can increase it arbitrarily in rc.conf. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-186841-4805-8FYT6iIH70>