[Cerowrt-devel] upnpd problem semi-solved

[Cerowrt-devel] upnpd problem semi-solved

[Dave Taht]

The version I was carrying in ceropackages was obsolete and didn't integrate
into fw3. Dropped that release, built from openwrt head, I can open ports now
from the transmission bittorrent client and from dns-sd (on macos) now.

the author tells me the latest version (not what I built, it's only a
few days old) does PCP also.

1) It's not clear to me why minissdpd was needed?

2) Are there any other test cases I could try?

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

Re: [Cerowrt-devel] upnpd problem semi-solved

[Paul Handly]

SSDP registration (server) and subsequent discovery (client) across
subnets was what I needed minissdpd for, but the devices I was trying to
drive (Sonos) are kind of pricey as a test case.

Having an IPv6 address on the listen interface/s broke the old build of
minissdpd, so I had to choose between IPv6 and Sonos.

-- 
Paul Handly <paul@hand.ly>

On Wed, Jan 29, 2014, at 11:55, Dave Taht wrote:
> The version I was carrying in ceropackages was obsolete and didn't
> integrate
> into fw3. Dropped that release, built from openwrt head, I can open ports
> now
> from the transmission bittorrent client and from dns-sd (on macos) now.
> 
> the author tells me the latest version (not what I built, it's only a
> few days old) does PCP also.
> 
> 1) It's not clear to me why minissdpd was needed?
> 
> 2) Are there any other test cases I could try?
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

Re: [Cerowrt-devel] upnpd problem semi-solved

[Dave Taht]

Well, I see ipv6 support in the current codebase, don't know if it's
in the codebase I'm trying now...

my understanding of the separate minissdp server was that it acted as
an arbitrator between
multiple possible users of the functionality (like dlna)

On Wed, Jan 29, 2014 at 9:25 AM, Paul Handly <paul@hand.ly> wrote:
> SSDP registration (server) and subsequent discovery (client) across
> subnets was what I needed minissdpd for, but the devices I was trying to
> drive (Sonos) are kind of pricey as a test case.
>
> Having an IPv6 address on the listen interface/s broke the old build of
> minissdpd, so I had to choose between IPv6 and Sonos.
>
> --
> Paul Handly <paul@hand.ly>
>
> On Wed, Jan 29, 2014, at 11:55, Dave Taht wrote:
>> The version I was carrying in ceropackages was obsolete and didn't
>> integrate
>> into fw3. Dropped that release, built from openwrt head, I can open ports
>> now
>> from the transmission bittorrent client and from dns-sd (on macos) now.
>>
>> the author tells me the latest version (not what I built, it's only a
>> few days old) does PCP also.
>>
>> 1) It's not clear to me why minissdpd was needed?
>>
>> 2) Are there any other test cases I could try?
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt:
>> http://www.teklibre.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

Re: [Cerowrt-devel] upnpd problem semi-solved

[Maciej Soltysiak]

DLNA discovery is using SSDP. SSDP are multicasts which don't easily
traverse between interfaces.
minissdp is supposed to proxy between interfaces. I think it also
keeps track of the devices so it can respond on behalf of other
devices.

I'm running 3.10.18-1. If there's a build you would suggest I try, I'm
happy to do it.


On Wed, Jan 29, 2014 at 7:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Well, I see ipv6 support in the current codebase, don't know if it's
> in the codebase I'm trying now...
>
> my understanding of the separate minissdp server was that it acted as
> an arbitrator between
> multiple possible users of the functionality (like dlna)
>
> On Wed, Jan 29, 2014 at 9:25 AM, Paul Handly <paul@hand.ly> wrote:
>> SSDP registration (server) and subsequent discovery (client) across
>> subnets was what I needed minissdpd for, but the devices I was trying to
>> drive (Sonos) are kind of pricey as a test case.
>>
>> Having an IPv6 address on the listen interface/s broke the old build of
>> minissdpd, so I had to choose between IPv6 and Sonos.
>>
>> --
>> Paul Handly <paul@hand.ly>
>>
>> On Wed, Jan 29, 2014, at 11:55, Dave Taht wrote:
>>> The version I was carrying in ceropackages was obsolete and didn't
>>> integrate
>>> into fw3. Dropped that release, built from openwrt head, I can open ports
>>> now
>>> from the transmission bittorrent client and from dns-sd (on macos) now.
>>>
>>> the author tells me the latest version (not what I built, it's only a
>>> few days old) does PCP also.
>>>
>>> 1) It's not clear to me why minissdpd was needed?
>>>
>>> 2) Are there any other test cases I could try?
>>>
>>> --
>>> Dave Täht
>>>
>>> Fixing bufferbloat with cerowrt:
>>> http://www.teklibre.com/cerowrt/subscribe.html
>>> _______________________________________________
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

Re: [Cerowrt-devel] upnpd problem semi-solved

[Dave Taht]

I have been gradually realizing that solving all the problems highly
dynamically assigned native
ipv6 brings us is not going to get solved this week, or this year.

anyway, I am still working on stablizing comcast specific stuff here:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/comcast/3.10.28-4/

but since tunnels don't go boom it's more suitable for general use...

improvements since the last time I talked about anything:

+ rngd, polipo, ahcpd, pimd, both web servers, - moved to procd
+ upnpd updated and at least partially fixed
+ babeld logs to /dev/null

hopefully this should stop running out of memory and flash.

+ tunnelling headaches sorta solved
  we no longer spin out of control when establishing an he tunnel
  while a native ipv6 session is active

- tunneling headaches
  but a ton of things don't work either, like dns
  advise: tunnel or run native, not both
             turn off sourcerouting for tunnels (as yet)
- ipv6 dynamic headaches
  poor integration with ahcp, dhcp-pd, etc
  (and I only get a /60 from comcast)
  (and a reboot of the router led to getting new addresses
   assigned and caused chaos through my ahcpd'd
   and dhcp-pd'd testbed)

- a source of unaligned instruction traps found but not fixed

https://dev.openwrt.org/ticket/14868

The trap occurs during the call to SyS_prlimit64.
Didn't see anything obvious that said "I'm
possibly unaligned, fixme"

- package signing broke a few releases back
  disabled here. ENOTIME.

- babeld not moved to procd
- babeld fails to detect a channel on AP wireless interfaces.
- haven't necessarily got all the ucitrack dependencies right overall
- still no mosh on the router...

in other news, ipv6 support has landed for mosh, upstream
dropbear is adding support for TOS setting, and
I actually saw dnsmasq doing dnssec validation without crashing (on x86).

I am overjoyed to finally have ipv6 support for mosh upstream. Now I
can finally go e2e with it and leave a ton of connections nailed up.

https://github.com/keithw/mosh

note: ipv6 support requires a newer perl library than the previous generation of
mosh, libio-socket-ip-perl.

On Wed, Jan 29, 2014 at 11:54 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
> DLNA discovery is using SSDP. SSDP are multicasts which don't easily
> traverse between interfaces.
> minissdp is supposed to proxy between interfaces. I think it also
> keeps track of the devices so it can respond on behalf of other
> devices.
>
> I'm running 3.10.18-1. If there's a build you would suggest I try, I'm
> happy to do it.
>
>
> On Wed, Jan 29, 2014 at 7:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> Well, I see ipv6 support in the current codebase, don't know if it's
>> in the codebase I'm trying now...
>>
>> my understanding of the separate minissdp server was that it acted as
>> an arbitrator between
>> multiple possible users of the functionality (like dlna)
>>
>> On Wed, Jan 29, 2014 at 9:25 AM, Paul Handly <paul@hand.ly> wrote:
>>> SSDP registration (server) and subsequent discovery (client) across
>>> subnets was what I needed minissdpd for, but the devices I was trying to
>>> drive (Sonos) are kind of pricey as a test case.
>>>
>>> Having an IPv6 address on the listen interface/s broke the old build of
>>> minissdpd, so I had to choose between IPv6 and Sonos.
>>>
>>> --
>>> Paul Handly <paul@hand.ly>
>>>
>>> On Wed, Jan 29, 2014, at 11:55, Dave Taht wrote:
>>>> The version I was carrying in ceropackages was obsolete and didn't
>>>> integrate
>>>> into fw3. Dropped that release, built from openwrt head, I can open ports
>>>> now
>>>> from the transmission bittorrent client and from dns-sd (on macos) now.
>>>>
>>>> the author tells me the latest version (not what I built, it's only a
>>>> few days old) does PCP also.
>>>>
>>>> 1) It's not clear to me why minissdpd was needed?
>>>>
>>>> 2) Are there any other test cases I could try?
>>>>
>>>> --
>>>> Dave Täht
>>>>
>>>> Fixing bufferbloat with cerowrt:
>>>> http://www.teklibre.com/cerowrt/subscribe.html
>>>> _______________________________________________
>>>> Cerowrt-devel mailing list
>>>> Cerowrt-devel@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>>
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html