linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #04877
Re: [Bug 882961] Re: Binding problem with 2 network interfaces
Oeps i see you changed things last evening, i did this test before them so
hold my comment untill i get a mingw build of rev 2703 ...
--------------------------------------------------
From: "Pirre" <882961@xxxxxxxxxxxxxxxxxx>
Sent: Wednesday, December 07, 2011 8:00 AM
To: <pierreparys@xxxxxxxxxxx>
Subject: [Bug 882961] Re: Binding problem with 2 network interfaces
> It does not work for me. now i get the error dialog that the ports are
> altready in use.
>
> Tryed it with 1 and several nic's working, same result and gdb provides
> no info in what he is trying to bind,
>
> Have done it on 2 pc's both XP's , turning back to a older dc++ revision
> works aslong there is only 1 nic :)
>
> Probebly XP ?
>
> --
> You received this bug notification because you are a member of
> Dcplusplus-team, which is subscribed to DC++.
> https://bugs.launchpad.net/bugs/882961
>
> Title:
> Binding problem with 2 network interfaces
>
> Status in DC++:
> Invalid
>
> Bug description:
> XP up to date, DC rev 2655
>
> When i have my normall lan and a ip6 tunnel both enabled, and i try to
> use manual portforwarding somethng seems wrong, even when i specify the
> lan interfaceas binding address the ports are indicated as listning but do
> not work.
> Using a extern port verification i get "connection refused"
>
> When i disable the 2 interface , restart dc all works ... and ports
> look to bind correct, port verification then sees the service and
> downloads work. (with or without specified binding)
>
> Resolved :20888 to 10.0.0.1, next is 00000000
> [New Thread 2404.0x988]
> Resolved :20889 to 10.0.0.1, next is 00000000
> [New Thread 2404.0xd28]
> Resolved :20888 to 10.0.0.1, next is 00000000
>
> Enabling the 2the interface again and restart dc .... with binding
> specified to 10.0.0.1
>
> Resolved :20889 to 169.254.123.195, next is 00296600
> [New Thread 2012.0xee4]
> Resolved :20888 to 169.254.123.195, next is 00298910
> [New Thread 2012.0x9f8]
>
> it binds to the tunnel addapters local ip4 address that it uses for
> local communication (conform specs)
>
> And no transfersare offcourse possible. NATT seems to work fine with
> both interfaces running.
>
> If more info needed i can provide the 2 netstat and ipconfig results
> with and without the 2the addapter :)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dcplusplus/+bug/882961/+subscriptions
>
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/882961
Title:
Binding problem with 2 network interfaces
Status in DC++:
Invalid
Bug description:
XP up to date, DC rev 2655
When i have my normall lan and a ip6 tunnel both enabled, and i try to use manual portforwarding somethng seems wrong, even when i specify the lan interfaceas binding address the ports are indicated as listning but do not work.
Using a extern port verification i get "connection refused"
When i disable the 2 interface , restart dc all works ... and ports
look to bind correct, port verification then sees the service and
downloads work. (with or without specified binding)
Resolved :20888 to 10.0.0.1, next is 00000000
[New Thread 2404.0x988]
Resolved :20889 to 10.0.0.1, next is 00000000
[New Thread 2404.0xd28]
Resolved :20888 to 10.0.0.1, next is 00000000
Enabling the 2the interface again and restart dc .... with binding
specified to 10.0.0.1
Resolved :20889 to 169.254.123.195, next is 00296600
[New Thread 2012.0xee4]
Resolved :20888 to 169.254.123.195, next is 00298910
[New Thread 2012.0x9f8]
it binds to the tunnel addapters local ip4 address that it uses for
local communication (conform specs)
And no transfersare offcourse possible. NATT seems to work fine with
both interfaces running.
If more info needed i can provide the 2 netstat and ipconfig results
with and without the 2the addapter :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/882961/+subscriptions
References