View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004336 | unreal | ircd | public | 2014-10-25 09:51 | 2015-05-25 17:05 |
Reporter | syzop | Assigned To | syzop | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | resolved | Resolution | duplicate | ||
Product Version | 3.4-alpha1 | ||||
Target Version | 3.4-alpha2 | ||||
Summary | 0004336: set::bind-ip | ||||
Description | Create a set::bind-ip which will specify the default IP to bind to for all operations. So for: listen, link, etc. That makes the bind-ip (&friends) optional everywhere of course. If it's not set then we use the default from set::bind-ip. Means listen should accept the following format: listen 6667; If it does not already. We still want.. listen *:6667; ..to bypass any bind-ip as it's perfectly legit after all to set a set::bind-ip but have a wide listener. uncommon.. but legit.. How to deal with IPv6? I suggest to just permit the use of two bind-ip blocks: set { bind-ip 1.2.3.4; bind-ip 2001:470:b163::8; }; That, rather than something comma or space separated. | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
Instead of both being "bind-ip", I suggest making on "bind-ip" and the other "bind-ip6" Even though the world was supposed to switch entirely to IPv6 over 5 years ago... |
|
+1 for stealth's idea. |
|
Well, of course I thought about that, that is the most logical given our current way of thinking. But thinking of the future I think we shouldn't create new "bind-ip6" like things. |
|
Turns out this was already done in 0004246 a year ago (.. but.. it doesn't handle ipv6? hm) |
Date Modified | Username | Field | Change |
---|---|---|---|
2014-10-25 09:51 | syzop | New Issue | |
2014-10-25 09:52 | syzop | Relationship added | related to 0003581 |
2014-10-28 04:53 | Stealth | Note Added: 0018266 | |
2014-10-28 16:58 | katsklaw | Note Added: 0018270 | |
2014-11-05 16:43 | syzop | Note Added: 0018273 | |
2015-05-25 17:05 | syzop | Note Added: 0018344 | |
2015-05-25 17:05 | syzop | Status | new => resolved |
2015-05-25 17:05 | syzop | Resolution | open => duplicate |
2015-05-25 17:05 | syzop | Assigned To | => syzop |