Issues with --bind and Jabber
Christian "Khark" Lauf <Khark@...
2007-08-16 14:09:26 GMT
today I noticed a strange problem which source I cannot identify.
I own a dedicated Debian Etch rootserver with 6 IP-Addresses.
1 physical (eth0) and 5 virtual (eth0:1 to eth0:5).
At startup centericq always picks eth0:5 as IP-Address to listen on.
Because I don't want centericq to listen there, I start centericq as
centericq --bind ip.of.device.eth0 (IP-Address of the physical eth0 device)
But if I do that, centericq refuses to connect to the Jabber network.
ICQ works fine. For others I can't tell, because I don't use other
The status window shows:
[icq] connecting to the server
[jab] connecting to the server
[icq] logged in
I captured the traffic with wireshark and noticed that the DNS A-Record
for jabber.com (IP: 126.96.36.199) is lookep up and returned to me.
But not one single packet is sent out to this IP or any other
Jabber-Host. Not even a TCP-SYN.
Centericq started without --bind works perfectly. Lookup DNS A-Record,
send a TCP-SYN to 188.8.131.52, receive SYN,ACK, send ACK. All fine.