Modify

#1003 closed defect (fixed)

OpenBSD SRV lookup issues

Reported by: wilmer Owned by: wilmer
Priority: normal Milestone:
Component: Jabber Version: 3.0.5
Keywords: patch Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description

This keeps happening, now it's apparnetly broken on (some) OpenBSD machines.

Not sure whether there's one easy fix for this, but at least the Jabber module could use some helpful warnings on this problem.

Attachments (1)

openbsd-ns_parse.diff (3.0 KB) - added by dx at 2014-02-04T18:26:41Z.
Mirror openbsd patch here

Download all attachments as: .zip

Change History (14)

comment:1 Changed at 2013-03-02T18:51:20Z by leva@…

Hey Wilmer!

I'm curious about this issue. I'm currently investigating a case where two bitlbees (same versions, same configurations, same accounts...) behaves differently with jabber (gtalk, to be precise). Bitlbee can connect to a GTalk account on Linux, but can not on OpenBSD. I've narrowed it down to the erronous behaviour in the connection initiation, that bitlbee would query the proper 'SRV _xmpp-client...' records on Linux, whereas on OpenBSD it queries an A record for gmail.com, and then tries to connect to the queried IP on port 5222, which results in a failure to connect the GTalk account. Is this the same issue?

comment:2 Changed at 2013-03-02T18:51:50Z by leva@…

Oh, btw, both bitlbees are 3.2.0.

comment:3 Changed at 2013-03-04T11:06:27Z by Daniel <leva@…>

And I'm very much tempted to suggest that this is almost certainly the same culprit as in bug #421

comment:4 Changed at 2013-03-04T20:22:22Z by Daniel <leva@…>

I can confirm that specifying a fix server address for the gtalk account is a valid workaround for this.

comment:5 Changed at 2013-03-07T08:35:15Z by Daniel <leva@…>

FWIW, I've created a patch to make this work on OpenBSD. I'm currently testing it, and it seems to be working. Are you interested in including this fix (or let's say feature)?

comment:6 Changed at 2014-02-03T20:48:49Z by dx

See #1098 for a patch to possibly related srv lookup issues

comment:7 in reply to:  6 ; Changed at 2014-02-04T08:55:21Z by Daniel

Replying to dx:

See #1098 for a patch to possibly related srv lookup issues

Unfortunatelly, upstream doesn't seem to give a crap about this. We've already integrated a patch in OpenBSD's ports tree; if someone is interested...

comment:8 in reply to:  7 Changed at 2014-02-04T09:36:59Z by dx

Replying to Daniel:

Replying to dx:

See #1098 for a patch to possibly related srv lookup issues

Unfortunatelly, upstream doesn't seem to give a crap about this. We've already integrated a patch in OpenBSD's ports tree; if someone is interested...

What side is upstream? Is that us? I always get confused by those terms.

https://github.com/toddfries/OpenBSD-ports-patches/tree/master/net/bitlbee/patches

Are these the patches you mean? (I don't really know much about openbsd)

comment:10 Changed at 2014-02-04T18:26:20Z by dx

Keywords: patch added

Sweet, thanks.

Changed at 2014-02-04T18:26:41Z by dx

Attachment: openbsd-ns_parse.diff added

Mirror openbsd patch here

comment:11 Changed at 2014-02-04T18:28:12Z by dx

Summary: Investigate SRV lookup troublesOpenBSD SRV lookup issues

comment:12 Changed at 2014-06-30T17:53:30Z by dx

Hey! We've got a new version of the patch over at #1098, now tested on openbsd! Sorry it took so long!

comment:13 Changed at 2014-09-27T14:30:28Z by dx

Resolution: fixed
Status: newclosed

Fixed by the patch in #1098, which has been merged now, and was tested across several platforms.

If there are any openbsd specific issues, feel free to reopen (or open a new ticket)

Modify Ticket

Action
as closed The owner will remain wilmer.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.