Bug 949303
| Summary: | Bitlbee socket not listening on IPv6 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Grant <mgg+bugzilla> | ||||
| Component: | bitlbee | Assignee: | Robert Scheck <redhat-bugzilla> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | mcepl, mcepl, redhat-bugzilla | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | bitlbee-3.2-6.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-24 22:27:34 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Mike Grant
2013-04-07 15:36:52 UTC
Is that really it? I see 127.0.0.1 all over the place: matej@wycliff: bitlbee (master %)$ grep -ri 127.0.0.1 . ./bitlbee.xinetd: bind = 127.0.0.1 ./bitlbee-forkdaemon.patch:+DaemonInterface = 127.0.0.1 ./bitlbee-3.2/bitlbee.conf:DaemonInterface = 127.0.0.1 ./bitlbee-3.2/doc/bitlbee.xinetd: # bind = 127.0.0.1 ./bitlbee-3.2/utils/bitlbeed.c: cli_txt = "127.0.0.1"; ./bitlbee-3.2/init/bitlbee.socket:ListenStream=127.0.0.1:6667 matej@wycliff: bitlbee (master %)$ That's all I needed to do to get it to work on my machine, which is only using the systemd socket approach. I'm sure you're correct that it should be changed in those other places too, to adjust the complete package. I'm happy to go through all the other ways of running it if that'd help. Created attachment 733991 [details]
suggested patch (just a cosmetic changes from the reporter's one)
Robert, what do you think? It seems to work here correctly.
I am fine with the patch, makes absolutely sense. Do you see chances that we get that one also upstream on the long term? bitlbee-3.2-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/bitlbee-3.2-6.fc19 bitlbee-3.2-6.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bitlbee-3.2-6.fc18 bitlbee-3.2-6.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/bitlbee-3.2-6.el6 bitlbee-3.2-6.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bitlbee-3.2-6.el5 Package bitlbee-3.2-6.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing bitlbee-3.2-6.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11236/bitlbee-3.2-6.el6 then log in and leave karma (feedback). bitlbee-3.2-6.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2-6.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2-6.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |