Bug#496461: closed by Adrian Perez <adrianperez.deb at gmail.com> (Re: azureus: does not bind to tcp/udp4)

[Achim Schaefer]

Hi,

I'm not aware of any kind of port forwarding on this box.
I assume iptables is not used at all, but I'm no expert so I don't know how to 
check for any rule anywhere.

data:~# iptables -L
WARNING: All config files need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will 
be ignored in a future release.
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
data:~#

I've got a little bit strange network interfaces:
data:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0e:2e:8c:b2:1b
          inet addr:192.168.77.233  Bcast:192.168.77.255  Mask:255.255.255.0
          inet6 addr: fe80::20e:2eff:fe8c:b21b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4314545 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2898497 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:248817746 (237.2 MiB)  TX bytes:378059811 (360.5 MiB)
          Interrupt:18 Base address:0xa800

eth1      Link encap:Ethernet  HWaddr 00:13:d3:a2:73:f0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 Base address:0x8000

extern    Link encap:Ethernet  HWaddr 00:0e:2e:8c:b2:1b
          inet addr:192.168.77.233  Bcast:192.168.77.255  Mask:255.255.255.0
          inet6 addr: fe80::20e:2eff:fe8c:b21b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:37274 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26367 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:39655431 (37.8 MiB)  TX bytes:3707640 (3.5 MiB)

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:249560 errors:0 dropped:0 overruns:0 frame:0
          TX packets:249560 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:64539708 (61.5 MiB)  TX bytes:64539708 (61.5 MiB)

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

data:~#

Basically extern (which is a bridge to eth0) should normally be used.
since I installed hte kde-network-manager package, eth0 got an ip adress.
So after boot, I need to ifdown extern, ifup extern to have network back.
I was not able to digg into this till now.

Achim
Am Montag 17 August 2009 18:55:08 schrieb Adrian Perez:
> What kind of port forwarding you're performing? iptables?
> Could you please provide more information.
> Binding to :: will comprise ipv4 too, AFAIK.
>
> On Fri, 2009-08-14 at 19:44 +0200, Achim Schaefer wrote:
> > which seems not allowed any more
> > to port 46949. now I can see only ipv6 ports open:
> > achim at data:~$ netstat -an | grep 46949
> > tcp6       0      0 :::46949                :::*
> > LISTEN
> > udp6       0      0 :::46949                :::*
> > achim at data:~$
> >
> > Achim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20090820/7a0ba377/attachment.pgp>