View Issue Details

IDProjectCategoryView StatusLast Update
0003581unrealircdpublic2014-10-25 09:52
Reportertwizted Assigned Tosyzop  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionno change required 
OSLinuxOS Version2.4.3 
Product Version3.2.7 
Summary0003581: Problem with link block
DescriptionBasically this is the issue, i'm having with centos and linking

error with bind-ip

Since i have my listen block set up correct to listen on 1 ip rather than all that are owned:

Bug is this

While linking to a network
u have like
Hostname there.ip.here;
bind-ip *; < this is where the bug is for me, because the box has more than 1 ip, i cant do bind-ip as *; it will rehash correctly, but when i /connect other.server.here, i get connected refused until i set bind-ip to the the listning ip, which defeats the purpose of having the option anyways seeing as its not going to work until i set it to the exact ip i'm listning on.

so the suggestion i have which i also listed in additional information is just making * default as the listning ip, just without actually havning to enter it over and over and over again.
Steps To ReproduceProblem is it dosent happen on all centos-boxes so i'm not sure if it can be reproduced on all,
Additional InformationSuggestion is to make the link block
by default, if i'm using * for bind-ip, rather than havning to add my ip for all links i do, make * (for this particular catagory) by default be my ip

so instead of having

bind-ip 66.252.x.x;
i could still use bind-ip *; and its defaulted as the ip i'm listning on.

simply because I obviously want to bind to the same ip i'm listning on anyways, so i shouldn't have to add the ip for every link block
TagsNo tags attached.
3rd party modules

Relationships

related to 0004336 resolvedsyzop set::bind-ip 

Activities

Stealth

2008-02-07 21:40

reporter   ~0015035

No need for issue to be private.

syzop

2014-10-25 09:45

administrator   ~0018259

Previously UnrealIRCd had this, or.. a somewhat broken implementation of it. It would bind by default to IP you specified in the last (or first.. I forgot) listen block.

I found this too much magic, and it created a lot of confusion. Hence it was fixed/removed (forgot which version).

We could, of course, add some set::bind-ip that makes everything default to that if there's no IP specified.

syzop

2014-10-25 09:52

administrator   ~0018260

I just submitted issue 0004336 to do what I just said. I think that's the best solution.

Issue History

Date Modified Username Field Change
2008-01-18 18:05 twizted New Issue
2008-02-07 21:40 Stealth QA => Not touched yet by developer
2008-02-07 21:40 Stealth U4: Need for upstream patch => No need for upstream InspIRCd patch
2008-02-07 21:40 Stealth U4: Upstream notification of bug => Not decided
2008-02-07 21:40 Stealth U4: Contributor working on this => None
2008-02-07 21:40 Stealth Note Added: 0015035
2008-02-07 21:40 Stealth View Status private => public
2014-10-25 09:45 syzop Note Added: 0018259
2014-10-25 09:45 syzop Status new => closed
2014-10-25 09:45 syzop Assigned To => syzop
2014-10-25 09:45 syzop Resolution open => no change required
2014-10-25 09:52 syzop Relationship added related to 0004336
2014-10-25 09:52 syzop Note Added: 0018260