Re: [OpenWrt-Devel] [OpenWrt] [LEDE-DEV] TR-069 for OpenWrt

[sniperpr]

qi_w...@people2000.net
tie_y...@people2000.net
Dirk Feytons 于2016年6月1日 周三04:49写道：

> On 30 May 2016 at 11:58, Delbar Jos  wrote:
>
>> Felix Fietkau  wrote:
>> > > We are conscious of the fact that together with the proposals made by
>> > > Felix, Luka and Wojtek we are now looking at many "competing"
>> proposals.
>> > > As a next step, we recommend to organize a workshop, at a practical
>> > > location and time, where we put everything on the table and define the
>> > > most appropriate path forward to the benefit of OpenWrt as a whole.
>> > I think such a workshop would be a great idea. It would be nice to have
>> the
>> > code available for review some time before that workshop, so we can all
>> take
>> > a detailed look at the various proposals before we sit down and decide
>> how
>> > to move forward with this.
>>
>> I agree that would be helpful. In our case it will take us some weeks
>> before we can formally release sources. We will be able to share
>> documentation on architecture, API, features, etc. up front to get the
>> discussions going.
>>
>
> At the Lua Workshop last year I presented how we're using Lua in our
> gateways. One of the items is how we implement the TR-069 datamodels in
> OpenWrt. The talk was recorded and is available at
> https://www.youtube.com/watch?v=zVzEmewJG8I
>
>
> Dirk F.
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Time Division Multiple Access (TDMA)

[sniperpr]

i have  interesting.

2012/8/22 Adrian Chadd adr...@freebsd.org

 On 13 July 2012 06:24, Jonathan Bither jonbit...@gmail.com wrote:
  Nico,
  I too have been interested in experimenting with TDMA. When I
 looked
  a while ago the most helpful information that I saw was that TDMA
 support is
  apparently included in freebsd. You may want to take a look at how it is
  implemented over there.
 
  http://fxr.watson.org/fxr/source/net80211/ieee80211_tdma.c
 

 I'm about to start working out the kinks. It broke some time after
 FreeBSD-7.x. Luckily I have all of the pre-11n atheros hardware here
 so I can setup a working environment and then figure out which
 commits/changes broke things.

 I'll post updates to FreeBSD-wireless once I figure it out.

 Thanks,


 Adrian
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel




-- 
DDNAS系列！ http://ddnas.openmobilefree.net/

adam.huang
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Invitation to connect on LinkedIn

[Sniperpr(Linux_Pro Linuxsir)]

OpenWrt,

I'd like to add you to my professional network on LinkedIn.

- Sniperpr(Linux_Pro

Sniperpr(Linux_Pro Linuxsir)
Embedded engineer at aisai
China

Confirm that you know Sniperpr(Linux_Pro Linuxsir):
https://www.linkedin.com/e/-mk98gm-gs179gc4-2p/isd/4050430013/0DHknQLg/?hs=falsetok=1wk5djoREFoAU1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-mk98gm-gs179gc4-2p/ktZPbWxB25EZT1bCQhnisxPEyrgU5E5CHHZjsWlByC8zSIB/goo/openwrt-devel%40lists%2Eopenwrt%2Eorg/20061/I1395658114_1/?hs=falsetok=1L6OoxT_YFoAU1

(c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #7670: about ath9k performance. STA(WDS) and AP (WDS) bridge mode.

[sniperpr]

Next week,i will test it.

nbd,Thank you for your efforts.

2010/8/4 OpenWrt openwrt-devel@lists.openwrt.org

 #7670: about ath9k  performance. STA(WDS) and AP (WDS) bridge mode.

 ---+
  Reporter:  sniperpr@… |   Owner:  developers
 Type:  task   |  Status:  new
  Priority:  low|   Milestone:  Backfire 10.03.1
 Component:  kernel | Version:  Backfire 10.03
  Keywords:  ath9k bridge slow  |

 ---+

 Comment(by nbd):

  I have no idea what the description is supposed to mean. Could you please
  rephrase and give some details on your setup?
  It might be helpful to copypaste the network and wireless configs from
  both ends.

 --
 Ticket URL: https://dev.openwrt.org/ticket/7670#comment:3
 OpenWrt http://openwrt.org
 Opensource Wireless Router Technology
 ___
 openwrt-tickets mailing list
 openwrt-tick...@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] MPC8241 based WW721 BSP Backfire-10.03 Support

[sniperpr]

thanks.

2011/1/6 HP Teoh hpt...@ceedtec.com

 Attached is Backfire-10.03 Linux BSP patch to support MPC8241 based WW721
 3G Wireless board.  For more information about the board, please visit
 http://www.ceedtec.com/router-embedded-platform-on-board-mini-pcie-slot-for-wimax-hsdpa-hsupa-wireless-module.html
 .

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] WRT610n v2 support

[sniperpr]

good job!

2010/12/20 George Kashperko geo...@academy.zt.ua

 Hi All,

 Might be posting not in a proper thread but one regarding ASUS RT-N16 looks
 like dead one atm. Anyway afaik Linksys WRT610n v2 is built around BCM4718
 soc,
 the same as N16 one is based on. So may be I could be of some use for those
 who wanna get Openwrt running on their boxes.

 I've spent some time with RT-N16 GPL code from ASUS (you can get one from
 ftp://ftp.asus.com/pub/ASUS/wireless/RT-N16/GPL_RT_N16_1019.zip). Cleaned
 it up a
 bit as it was based on some intermediate git of 2.6.22 and got a patch
 (about 250Kb) against linux-2.6.22. Unfortunately this code is built around
 Broadcom's SDK one (release 5.10.147.0 if I got it right). Everything about
 soc hw (ssb, pci, etc.) in kernel itself is left intact, instead bunch of
 Broadcom's code doing all the stuff about detecting, initializing and
 managing BCM471x hardware. Also to get this kernel built one need at least
 two
 proprietary Broadcom's .o object files (one for wireless driver, and
 another one for ctf driver code) both provided with original ASUS GPL
 package (ftp
 link to .zip from ASUS is above) and two more .o's to get wl supplicant and
 configuration tool running (from
 http://mirror2.openwrt.org/sources/broadcom-wl-
 5.10.56.27.0.tar.bz2). Also you can get just these .o's alone at
 http://www.znau.edu.ua/temp/asus-rt-n16/asus-rt-n16.2.6.22.mips2.files.tar.bz2

 Attached is the patch against current (last tried it with 24667) Openwrt
 trunk to get it run on RT-N16 with 2.6.22.19 kernel. Also you can dl it from

 http://www.znau.edu.ua/temp/asus-rt-n16/asus-rt-n16.2.6.22.mips2.files.tar.bz2

 I know pre2.6.34 kernel support is wiped out from Openwrt trunk, and this
 one is based on 2.6.22. Just hope this could be of some use as the
 alternative to
 original/dd-wrt/tomato/wl500g/etc. firmware till we get mainline kernel
 working with 4716/18, and maybe of some use for porting ssb/pcie code from
 Broadcom's SDK.

 Atm I've got 3 RT-N16 boxes running with this stuff and it seems they work
 smooth enough (except for bunch of annoying messages protocol  is
 buggy,
 dev eth1 in dmesg).

 For those who will decide to try it out keep in mind that:
 1. 2.6.22'based code is moved out into different target (brcm4716 instead
 of the brcm47xx as used in trunk and earlier Openwrt releases) in order not
 to
 break current 47xx functionality.
 2. Packages base-files, broadcom-diag, nvram and switch where
 patched to get them working with this new target, but those changes should
 not affect
 original brcm47xx target's functionality.
 3. To get broadcom-hnd package compiled (mainly its for ethernet and
 wireless drivers with wl supplicant and cfg tool) one need four precompiled
 .o files
 (nas_exe.o, wl_exe.o, ctf.o and either wl_ap.o or wl_apsta.o or wl.sta.o
 depending on planned wl mode) - get them from
 http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.0.tar.bz2 and
 ftp://ftp.asus.com/pub/ASUS/wireless/RT-N16/GPL_RT_N16_1019.zip or dl

 http://www.znau.edu.ua/temp/asus-rt-n16/asus-rt-n16.2.6.22.mips2.files.tar.bz2for
  just these files alone.
 4. After patching the trunk chmod +x following scripts:
target/linux/brcm4716/base-files/etc/init.d/netconfig
target/linux/brcm4716/base-files/etc/init.d/wmacfixup
target/linux/brcm4716/base-files/sbin/hotplug.failsafe
 5. You will need to get things compiled with binutils 2.20.1 and gcc 4.2.4.
 Newer gcc refuses to compile that stuff. Other binutils might work but never
 tried it itself so better stick to 2.20.1 one. The same stands to uClibc -
 tested it with 0.9.30.1, others might work or might not. Issue make
 menuconfig
 and set proper gcc/binutils/uClibc vers in Advanced configuration options
 (for developers)/Toolchain Options or just cp 2.6.22.19.config .config to
 use
 mine template config provided with patch.
 6. Keep in mind that after reflash during first boot your box will start
 formatting mtdblock3 for linux-data jffs2 partition and it could take some
 time
 (about 3-5 mins for mine N16 with 32Mb flash). If you reset the box before
 it finish with format and after then run mtd fixtrx your box will enter
 emergency repair mode (at least N16 does so) or potentially could get
 bricked - so better let it finish with format or even better get yourself
 uart-rs232
 to watch how's it going online. This one thingy could get been fixed with
 proper drivers/mtd/maps/bcm947xx-flash.c code ofcourse, but I just dont
 think it
 worth time spent.
 7. See files network and wireless in /etc/config.tmp/ after you get box
 flashed and running for network/wireless uci config templates.

 For those who are interested in cleaned up Broadcom's kernel patch code
 look for it in
 target/linux/brcm4716/patches-2.6.22/000-linux-2.6.22.19.asus-
 gpl.rc8.patch (there were bits more things in netfilter code managing h/w
 acceleration - keep in mind I've wiped that code out).

 Also, I would be pleased to help with 

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #7759: ome pci device can't allocate I/O resource on ar71xx

[sniperpr]

no fix.

2010/12/10 OpenWrt openwrt-devel@lists.openwrt.org

 #7759: ome pci device can't allocate I/O resource on ar71xx

 ---+
  Reporter:  anonymous  |   Owner:  developers
 Type:  defect |  Status:  new
  Priority:  normal |   Milestone:  Kamikaze
 Component:  packages   | Version:  Trunk
  Keywords: |

 ---+

 Comment(by cantona):

  Hi, is there any update regarding this issue?

 --
 Ticket URL: https://dev.openwrt.org/ticket/7759#comment:5
 OpenWrt http://openwrt.org
 Opensource Wireless Router Technology
 ___
 openwrt-tickets mailing list
 openwrt-tick...@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #8181: iptables ttl option not working

[sniperpr]

trunk's iptalbe not has TTL.
backfire is has.

please use

 $(eval $(call nf_add,IPT_IPOPT,CONFIG_NETFILTER_XT_MATCH_HL,
$(P_XT)xt_hl))
136d134
 $(eval $(call nf_add,IPT_IPOPT,CONFIG_NETFILTER_XT_TARGET_HL,
$(P_XT)xt_HL))
148d145
 # XXX: ttl/TTL extensions have been merged in ttl/TTL in linux 2.6.30, but
not yet in iptables
150,151c147,148
   $(eval $(if $(NF_KMOD),,$(call nf_add,IPT_IPOPT,CONFIG_IP_NF_MATCH_TTL,
$(P_V4)ipt_ttl)))
   $(eval $(if $(NF_KMOD),,$(call nf_add,IPT_IPOPT,CONFIG_IP_NF_TARGET_TTL,
$(P_V4)ipt_TTL)))
---
   $(eval $(call nf_add,IPT_IPOPT,CONFIG_NETFILTER_XT_MATCH_HL,
$(P_XT)xt_hl))
   $(eval $(call nf_add,IPT_IPOPT,CONFIG_NETFILTER_XT_TARGET_HL,
$(P_XT)xt_HL))

2010/11/20 OpenWrt openwrt-devel@lists.openwrt.org

 #8181: iptables ttl option not working

 +---
  Reporter:  cheza...@…  |   Owner:  jow
 Type:  defect  |  Status:  accepted
  Priority:  normal  |   Milestone:  Kamikaze
 Component:  packages| Version:  Trunk
  Keywords:  |

 +---

 Comment(by markus_kub...@…):

  Using KAMIKAZE (bleeding edge, r23991), there also are no TOS and LENGTH
  libraries. WTF?  On Backfire 10.03.01-RC3 this worked. (But there were
  more packages installed.)

  on vanilla do:[[BR]]
  # opkg install kmod-ipt-ipopt

  # sh shaping-script[[BR]]
  iptables v1.4.9.1: Couldn't load match `length':File not found[[BR]]
  iptables v1.4.9.1: Couldn't load match `tos':File not found[[BR]]


  # opkg info kmod-ipt-ipopt[[BR]]
  Package: kmod-ipt-ipopt[[BR]]
  Version: 2.6.32.25-1[[BR]]
  Depends: kernel (= 2.6.32.25-1), kmod-ipt-core[[BR]]
  Provides:[[BR]]
  Status: install hold,user installed[[BR]]
  Section: kernel[[BR]]
  Architecture: ar71xx[[BR]]
  Maintainer: OpenWrt Developers Team openwrt-de...@openwrt.org[[BR]]
  MD5Sum: 9af035f5516eeb867a78b45f5ea5b160[[BR]]
  Size: 11919[[BR]]
  Filename: kmod-ipt-ipopt_2.6.32.25-1_ar71xx.ipk[[BR]]
  Source: package/kernel[[BR]]
  Description: Netfilter (IPv4) modules for matching/changing IP packet
  options[[BR]]
  Includes:
  - CLASSIFY
  - dscp/DSCP
  - ecn/ECN
  - hl/HL (2.6.30 and later)
  - length
  - mark/MARK
  - statistic (2.6)
  - tcpmss
  - time
  - tos/TOS (prior to 2.6.25)
  - ttl/TTL (prior to 2.6.30)
  - unclean
  Installed-Time: 1290209572

  # ls /usr/lib/iptables[[BR]]
  libipt_DNAT.solibipt_MASQUERADE.so  libipt_SNAT.so
  [[BR]]libxt_NOTRACK.so  libxt_comment.so  libxt_mac.so
  libxt_standard.so libxt_tcp.so[[BR]]
  libipt_LOG.so libipt_REJECT.so  libipt_icmp.so
  [[BR]]libxt_TCPMSS.so   libxt_limit.solibxt_multiport.so
  libxt_state.solibxt_udp.so[[BR]]

  I see the ticket is 2 Weeks old, when will there be a fix?

 --
 Ticket URL: https://dev.openwrt.org/ticket/8181#comment:3
 OpenWrt http://openwrt.org
 Opensource Wireless Router Technology
 ___
 openwrt-tickets mailing list
 openwrt-tick...@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-tickets




--
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel