I have spent the time since last posting reinstalling, and retesting, the build.

6in4 works. As ever, the firewall configuration as reimported from backup 
blocks ipv6 function, even though the rules appear correct.  I worked around 
this by only reimporting the configuration files needed.

I tried the approach advocated by Sebastian, but achieved better results 
leaving the scripts in /usr/lib/aqm unaltered, which implies that the AQM GUI 
functions as intended.

Left with an uplink delay of 650 to 750 milliseconds, on a known poor ADSL 
line, which is better than previous builds, but still means that undertaking 
concurrent internet activities is problematic.



On 26 Jul 2013, at 16:51, Sebastian Moeller <[email protected]> wrote:

> Hi Fred,
> 
> 
> On Jul 26, 2013, at 16:31 , Fred Stratton <[email protected]> wrote:
> 
>> Thank you,  Sebastian and David.
>> 
>> Sebastian
>> 
>> I was unaware of the problem with functions.sh
>> 
>> I use polipo.
>> 
>> I shall try your stab approach again. I have a bridged connection, rather 
>> than using PPPoE, but can adapt.
> 
>       There is a number of different encapsulations for bridged setups, just 
> pick the one relevant for your link:
>               Connection: Bridged, VC/Mux RFC-1483/2684
>               Protocol (bytes): Ethernet Header (14), ATM pad (2), ATM AAL5 
> SAR (8) : Total 24
> 
>               Connection: Bridged, VC/Mux+FCS RFC-1483/2684
>               Protocol (bytes): Ethernet Header (14), Ethernet PAD [8] (0), 
> Ethernet Checksum (4), ATM pad (2), ATM AAL5 SAR (8) : Total 28
> 
>               Connection: Bridged, LLC/SNAP RFC-1483/2684
>               Protocol (bytes): Ethernet Header (14), ATM LLC (3), ATM SNAP 
> (5), ATM pad (2), ATM AAL5 SAR (8) : Total 32
> 
>               Connection: Bridged, LLC/SNAP+FCS RFC-1483/2684
>               Protocol (bytes): Ethernet Header (14), Ethernet PAD [8] (0), 
> Ethernet Checksum (4), ATM LLC (3), ATM SNAP (5), ATM pad (2), ATM AAL5 SAR 
> (8) : Total 36
> To my knowledge, the worst case overhead for ADSL connections is 44bytes.
> 
>       If you do not have sufficient information about your encapsulation at 
> hand contact me and I am happy to figure it our empirically...
> 
> 
>> I suspect all European telcos use ADSL2+ over ATM.
> 
>       At least in Germany you can also find ADSL1 over ATM, but that has no 
> bearing on the overhead or on the general ATM quantization issue. As fas as I 
> know all ADSLs use an ATM carrier, while VDSL systems (hopefully) should use 
> PTM (without the weird quantization issues).
> 
> Hope that helps
> 
>       Sebastian
> 
> 
>> 
>> David
>> 
>> I am encouraged that it works for you. Shall review settings via uci.
>> 
>> 
>> 
>> 
>> On 26 Jul 2013, at 11:51, David Personette <[email protected]> wrote:
>> 
>>> HEnet has been working consistently for me.
>>> 
>>> In /etc/config/network make sure that se00, sw00, sw10, gw00, gw10, gw01, 
>>> and gw11 all have the  following line:
>>>        option ip6assign        64
>>> 
>>> And add the following using your information to replace the '###' fields, 
>>> also remove any earlier configuration for it:
>>> 
>>> config interface henet
>>>        option proto            6in4
>>>        option peeraddr         ###
>>>        option ip6addr          ###
>>>        option tunnelid         ###
>>>        option username         ###
>>>        option password         ###
>>>        option ip6prefix        ###
>>>        option mtu              1480
>>>        option ttl              64
>>> 
>>> Finally add henet to the wan zone in /etc/config/firewall
>>> 
>>> The way to setup custom DNS is also in /etc/config/network, add the 
>>> following to you ge00 config:
>>>        option peerdns          0
>>>        option dns              '208.67.222.222 208.67.220.220'
>>> 
>>> I ran into issues updating to the 3.10.1 build, something got borked with 
>>> my configuration. Once I restored a backup, everything was fine (NOTE: this 
>>> is an assumption, it could have just been the additional reboot that fixed 
>>> the flakeyness). The upgrade to 3.10.2 went quite smoothly for me. If I hit 
>>> a problem with the upgrade to 3.10.3 I'll send a followup email.
>>> 
>>> 
>>> 
>>> On Fri, Jul 26, 2013 at 2:21 AM, Fred Stratton <[email protected]> wrote:
>>> I can certainly confirm this, having spent several fruitless hours with the 
>>> build.
>>> 
>>> 6in4 remains broken for henet.
>>> 
>>> dnsmasq appears not to recognise additional domain name servers. The ISP I 
>>> use has a very slow domain name service, to which the system now defaults. 
>>> The consequence of this is that opkg times out, and no packages can be 
>>> installed.
>>> 
>>> It is still not possible to watch a video stream and download files 
>>> simultaneously on an ADSL line.
>>> 
>>> 
>>> On 26 Jul 2013, at 06:20, Dave Taht <[email protected]> wrote:
>>> 
>>>> sysupgrade -n doesn't work with this release. Stay away. I have a new
>>>> build of 3.10.3-1 and am trying to fix it...
>>>> 
>>>> I did find the problem on the ubnt builds - I'd switched to the new
>>>> babeld from quagga, but failed to install it by default.
>>>> 
>>>> in openwrt trunk, elliptic curve has been enabled in openssl. It's
>>>> long past time we enable https for configuration by default, and might
>>>> as well figure out how to turn perfect forward secrecy on as well in
>>>> the post-snowden era.
>>>> 
>>>> owamp seemingly works well, with a couple glitches here and there. I
>>>> got to where the lab was synced to about 1ms resolution... and 5 more
>>>> gpses arrived today....
>>>> _______________________________________________
>>>> Cerowrt-devel mailing list
>>>> [email protected]
>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>> 
>>> _______________________________________________
>>> Cerowrt-devel mailing list
>>> [email protected]
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>> 
>> 
>> _______________________________________________
>> Cerowrt-devel mailing list
>> [email protected]
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 

_______________________________________________
Cerowrt-devel mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/cerowrt-devel

Reply via email to