disable ipv6

5 posts / 0 new
Last post
Anonymous
disable ipv6

i just installed your jabber server and i see that it binds on ipv6
address with 5269 port:
/home/tigase/etc# netstat -anp | grep 5269
tcp6 0 0 :::5269 :::* LISTEN
7013/java

its okay, but it don't work in ipv4 networks...

and my question is:
how i can bind it to ipv4 address?

Thanks!!!

Application: 

Hm, this is very strange. Normally Tigase automatically listens on both IPv4 and IPv6 addresses/interfaces. There are no configuration options to enable/disable one of them.
It discovers both of them automatically and tries to listen on both.

Do you have IPv4 interface/IP address configured for the machine? Can you copy and paste your init.properties file here?

What shows: 'ifconfig' command on your system?

mrpsycho

yes, sure

server is hosted on AWS
here ifconfig:

# ifconfig
eth0 Link encap:Ethernet HWaddr 12:31:39:04:74:e1
inet addr:10.240.123.15 Bcast:10.240.123.255 Mask:255.255.254.0
inet6 addr: fe80::1031:39ff:fe04:74e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:123747827 errors:0 dropped:0 overruns:0 frame:0
TX packets:168607735 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:163578973 (156.0 MiB) TX bytes:4272504790 (3.9 GiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14478879 errors:0 dropped:0 overruns:0 frame:0
TX packets:14478879 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2095598869 (1.9 GiB) TX bytes:2095598869 (1.9 GiB)

init.properties:

# cat /home/tigase/etc/init.properties
--user-db = mysql
--admins = admin@jabber.aws.somegreatname.com
--user-db-uri = jdbc:mysql://localhost:3306/tigase_db?user=tigase&password=tigase
config-type = --gen-config-all
--virt-hosts = jabber.aws.somegreatname.com
--debug = server

ps this link helped me:
http://www.randombugs.com/java/java-networking-problems-debian-squeezesid.html

So this is working for you now I guess. Anyway, very strange, I have no idea why tcp6 would conflict with tcp4....
Thank you for the hint though.

I just stumbled into this same problem, tigase 5.1.0-beta5-b2883 only listening on ipv6 on dual stack RHEL6.. I "fixed" it by adding "-Djava.net.preferIPv4Stack=true" to the JAVA_OPTIONS in tigase.conf.

If we're going to use tigase we'll need a proper fix making it listen to both v4 and v6, but this was good enough to get tigase working for our PoC.