Re: [OpenWrt-Devel] OVS on OpenWRT
Hello Yilun, I think that you can use OVS pretty much as you could use on any other Linux distro. We don't have any specific tutorials for OVS on OpenWRT. There are a few blogs that reference something like that: http://voices.canonical.com/zhengpeng.hou/11/ http://vishalshahane.blogspot.ro/2014/04/configuring-tp-link-wr1043nd-v21-as.html What is important regarding OVS on OpenWRT is to read about the /etc/config/network format. That's on the OpenWRT here: http://wiki.openwrt.org/doc/uci/network Looks like you need to configure OVS to setup bridges/flows via ovs-vsctl + ovs-ofctl commands and then in /etc/config/network you need to setup your IP addresses and other stuff. FYI: OVS is officially supported in the latest OpenWRT trunk. It's here in the package feeds: https://github.com/openwrt/packages/tree/master/net/openvswitch Thanks On Mon, Nov 17, 2014 at 2:14 AM, Yilun Zhou wrote: > > Hi, > I am experimenting with OpenVSwitch on OpenWRT. My goal is to use > Floodlight controller to do routing on OVS with Openflow 1.0 protocol. My > router is NETGEAR WNDR3800. I have installed OpenWRT Attitude and OVS on it > so that I can see a list of utilities such as: > ovs-appctl > ovs-dpctl > ovs-tcpundump > ovsdb-server > ovs-benchmark > ovs-ofctl > ovs-vlan-test > ovsdb-tool > ovs-brcompatd > ovs-parse-leaks > ovs-vsctl > ovs-bugtool > ovs-pcap > ovs-vswitchd > ovs-controller > ovs-pki > ovsdb-client > > I looked at this tutorial ( > http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=INSTALL;hb=HEAD) > but it uses a PC Linux distribution, which has different filesystem, etc. > that makes me not able to proceed as directed. Could anyone tell me how to > specifically use OVS on OpenWRT or point me to a resource about it? > Here is my post on Floodlight group that may provide more information ( > https://groups.google.com/a/openflowhub.org/d/msg/floodlight-dev/C6RAY-TYXdI/tHE8vt9tz9wJ > ). > > Thanks, > Yilun > > > > > > > ___ > 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
[OpenWrt-Devel] OVS on OpenWRT
Hi, I am experimenting with OpenVSwitch on OpenWRT. My goal is to use Floodlight controller to do routing on OVS with Openflow 1.0 protocol. My router is NETGEAR WNDR3800. I have installed OpenWRT Attitude and OVS on it so that I can see a list of utilities such as: ovs-appctl ovs-dpctl ovs-tcpundump ovsdb-server ovs-benchmark ovs-ofctl ovs-vlan-test ovsdb-tool ovs-brcompatd ovs-parse-leaks ovs-vsctl ovs-bugtool ovs-pcap ovs-vswitchd ovs-controller ovs-pki ovsdb-client I looked at this tutorial (http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=INSTALL;hb=HEAD) but it uses a PC Linux distribution, which has different filesystem, etc. that makes me not able to proceed as directed. Could anyone tell me how to specifically use OVS on OpenWRT or point me to a resource about it? Here is my post on Floodlight group that may provide more information (https://groups.google.com/a/openflowhub.org/d/msg/floodlight-dev/C6RAY-TYXdI/tHE8vt9tz9wJ?). Thanks, Yilun? ? ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] comgt: add ncm proto support
Matti, would you like to have the Huawei e3276 for debugging this after I get it back? Yours to keep if you want to :) Mine skills is kinda not there with this, but need for working NCM is more than needed for me :) Sami Olmari On Sat, Nov 15, 2014 at 6:31 AM, John Crispin wrote: > no and i will resend your device back to you next week > > On 14/11/2014 20:26, Sami Olmari wrote: >> I'm sorry to bother, but any luck with this? :) I have tried some >> stuff what Matti has suspected above the quirk is located at, but no >> good with mine coding skills :/ >> >> Sami Olmari >> >> On Sun, Nov 9, 2014 at 11:49 AM, Matti Laakso wrote: >>> Hi Jamie, >>> On Thu, Oct 30, 2014 at 12:58:40PM +0200, Matti Laakso wrote: > Hi Sami, > >> Using John's version: >> >> config interface 'wan' >> option proto 'wwan' >> option apn 'opengate' >> # option device '/dev/cdc-wdm0' (with or without commenting this) >> >> Does absolutely nothing, nothing in logread... >> >> However now when using >> >> config interface 'wan' >> option proto 'ncm' >> option apn 'opengate' >> option device '/dev/ttyUSB1' > > I believe that device should be /dev/cdc-wdm0 also here, at least > when using huawei_cdc_ncm. The /dev/ttyUSBx terminals created by the > option driver do not necessarily support all necessary AT-commands. > Also, (at least when using proto ncm) you need to specify in > addition > > option ifname wwan0 That wasn't enough to get it to find the device for me for some reason. The following change to proto_ncm_setup does make it work: echo "ncm[$$]" "Connected, starting DHCP" - proto_init_update "*" 1 + proto_init_update "wwan0" 1 proto_send_update "$interface" For bringing the interface down the control device can't be found. The following change in proto_ncm_teardown makes that work: json_get_vars device + + device="/dev/ttyUSB0" echo "ncm[$$]" "Stopping network" With the above two changes in place this all works fine. I don't know enough about how this is all meant to work to know why this is needed or why those configuration values are not making it to where they need to be. >>> >>> I suspect that the call to >>> >>> json_load "$(cat /etc/gcom/ncm.json)" >>> >>> in ncm.sh causes the interface information to get lost, so that subsequent >>> json_* calls no longer work correctly. We should somehow "unload" ncm.json >>> after the necessary AT-commands are read, and then restore normal >>> interface information. Or can we read ncm.json into a separate namespace or >>> something? Maybe Felix or Steven could give some advice? >>> >>> Matti >>> ___ >>> 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] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)
Depending on the CO/stinger equipment it might just be your chipset is incompatible. I had issues in the past with Bell sympatico stingers (made by Ikanos). They had firmware bugs verified by both Bell and Ikanos with anything that didn't run a broadcom DSP. There was nothing I could do except find a decent bridge modem based on a broadcom chipset. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] packages that won't build when building for tp-link archer c7 v2
for what it's worth, i enabled the "oldpackages" feed and selected to build all packages and i'm just making a list of all packages that (for one reason or another) don't build for my current platform: http://www.crashcourse.ca/wiki/index.php/OpenWrt_TP-Link_AC1750#Build_errors i make no claims that this is deep or profound information, or that it isn't trivially fixable -- i'm just trying to do a full build of all packages and, for each one that fails to build, i'm just doing a quick copy and paste to keep track, that's it. if anyone wants to do anything about any of them, have at it, i'm just trying to get to the end of my build sometime today. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq usb - isochronous transfers
Hi all, I'm trying to play around with isochronous USB mode an a fritz box router using freetz (a firmware mod of the original AVM firmware) and found this discussion during my research. As far as figured out, openwrt AA uses the dwc usb module (originally written by DesignWare) for the most lantiq SoC's except those used by AVM devices. Those are using the ifx-hcd module (v1.0) instead, that originally was written by lantiq and was published by AVM's code tarballs. While dwc-usb obviously supports isochronous transfer ifx-hcd doesn't (code does not compile if you activate this feature). Openwrt BB instead uses a more up-to-date version of ifx-hcd (3.2) for all lantiq SoC's that includes isochronous transfer that compiles but does not work. Obviously those two modules targeting the same usb-controller and are exchangeable, am I right? So in my special case using the dwc-usb module of openwrt AA with the original AVM kernel/freetz seems a promising approach to make isochronous transfer work? I also tried to port the ifx-hcd's code of openwrt BB to AVM/freetz, but by now I only get crashes. As this module obviously does not even work with a nativ openwrt build I don't need to invest more work here unless anybody find's a more up-to-date version of the code. Does anybody know where the currently used v3.2 code is from? I think it is not from AVM as all those comments and hacks of v1.0 etc. are missing. Thanks a lot, Tobias Herzog Am Montag, den 10.11.2014, 09:37 +0100 schrieb Ben Mulvihill: > Thanks! > > Any recommendations for good reasonably up-to-date GPL tarballs? > > On Mon, 2014-11-10 at 09:21 +0100, John Crispin wrote: > > there is now a upstream driver for dwc2 usb. i already started using it > > on ralink. we should really try to use that one. i am happy to take any > > patches though that imporve the current state. > > > > maybe we could also try to port a ifxhcd froma recent GPL tarball. > > > > > > > > > > On 10/11/2014 09:03, Ben Mulvihill wrote: > > > May I ask what the status of isochronous transfer support is > > > in the lantiq hcd driver? It was working in Attitude Adjustment > > > (at least my usb sound card worked anyway). > > > But a lot of changes were made to the driver between AA and BB, > > > including new code related to isosynchronous transfers, which are > > > now disabled by default (CONFIG_USB_HOST_IFX_WITH_ISO=n). > > > Someone else has filed a bug about this: > > > > > > https://dev.openwrt.org/ticket/15364 > > > > > > I tried building a BB image with isochronous transfers enabled, > > > but ifxhcd_intr.c failed to compile. The errors look like the > > > sorts of careless syntax errors which most people make when > > > writing a first version of a new piece of code, and my guess is > > > that this bit of code has have never in fact been compiled, let > > > alone tested. I have managed to get it to compile by making > > > various plausible corrections, but I don't yet have any sound. > > > Before I investigate further can you tell me whether it is > > > supposed to be working? > > > > > > (Below, for reference, are the corrections I have made. But this > > > is just an initial attempt, certainly not a patch to be merged.) > > > > > > Many thanks, > > > > > > Ben Mulvihill > > > > > > --- a/package/kernel/lantiq/ltq-hcd/src/ifxhcd_intr.c 2014-11-10 > > > 00:31:52.744641266 +0100 > > > +++ b/package/kernel/lantiq/ltq-hcd/src/ifxhcd_intr.c 2014-11-10 > > > 00:25:03.321242453 +0100 > > > @@ -103,6 +103,10 @@ > > > ifxusb_mreg(&((_hc_regs_)->hcintmsk),0, hcintmsk.d32); \ > > > } while (0) > > > > > > + > > > +static > > > +void init_hc(ifxhcd_epqh_t *_epqh); > > > + > > > /* > > > * Save the starting data toggle for the next transfer. The data toggle > > > is > > > * saved in the QH for non-control transfers and it's saved in the QTD > > > for > > > @@ -4089,13 +4093,13 @@ void init_hc(ifxhcd_epqh_t *_epqh) > > > ifxhc->isoc_xact_pos = > > > IFXUSB_HCSPLIT_XACTPOS_ALL; > > > #endif > > > > > > - _epqh->isoc_frame_index=0; > > > + urbd->isoc_frame_index=0; > > > _epqh->isoc_now=0; > > > _epqh->isoc_start_frame=0; > > > - if(_urb->transfer_flags && URB_ISO_ASAP) > > > + if(urb->transfer_flags && URB_ISO_ASAP) > > > _epqh->isoc_now=1; > > > else > > > - _epqh->isoc_start_frame=_urb->start_frame; > > > + _epqh->isoc_start_frame=urb->start_frame; > > > #ifdef __EN_ISOC_SPLIT__ > > > _epqh->isoc_split_pos =0; > > > _epqh->isoc_split_offset=0; > > > @@ -4296,8 +4300,8 @@ void select_eps_sub(ifxhcd_hcd_t *_ifxhc > > > > > > list_add_tail(&epqh->ql, &_ifxhcd->epqh_list_isoc); >
Re: [OpenWrt-Devel] libdlna won't build, allegedly due to missing dependencies
On 16.11.2014 09:45, Robert P. J. Day wrote: i checked trac and it seems that there is (still?) an ongoing issue with building libdlna, as i was trying to do for a tp-link archer c7 v2: cc1: note: someone does not honour COPTS correctly, passed 2 times src/libdlna.so: undefined reference to `av_find_stream_info' src/libdlna.so: undefined reference to `av_close_input_file' collect2: error: ld returned 1 exit status Makefile:36: recipe for target 'test-libdlna' failed make[4]: *** [test-libdlna] Error 1 that seems to match what i see here: https://dev.openwrt.org/ticket/11666 is there a suggested fix for this? or i can just deselect it for now. rday Since both libdlna and ushare are discontinued by the developer and no longer maintained, I would suggest you use minidlna instead. If that is not satisfactory, then someone needs to volunteer to move these packages to the active Github repo, take ownership of the maintenance and bring them up-to-date. I also recommend these packages be moved to the packages-abandoned repo. /ted ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/4] ubinize-image: Change the rootfs to a static volume
On Sun, Nov 16, 2014 at 10:54:18AM +0100, Daniel Golle wrote: > Hi Maxime, > > first of all sorry for the late reply. > > On Mon, Oct 27, 2014 at 11:16:13AM +0100, Maxime Ripard wrote: > > Hi Daniel, > > > This will break things if rootfs is a read-write UBIFS volume which should > > > by dynamic. > > > > Indeed, but is this something that is usually done in OpenWRT? > > Yes. Similar to having the option of using either JFFS2 (rw) or SquashFS (ro) > as rootfs on NOR-based devices, allowing users to use UBIFS (rw) rootfs can > make sense depending on the requirements further down the road. Ok. Who makes this decision? The user? The target? Someone else? > > > I also saw weird things happening when trying to access static > > > volumes in U-Boot and thus avoided them for now. > > > Please also consider that ubootenv* and kernel could be static volumes as > > > well, however, that needs to be tested with a more recent U-Boot (I hope > > > it'll work). > > > > Indeed, the kernel and bootloader might be static too. > > > > The only other solution I could think of was to force the size of the > > ubifs rootfs image to something like 10MB in our case. Which looks a > > bit counter-productive. > > I don't understand why that would be needed. > From what I saw, support for static volumes is hardly being used anywhere > and thus in exactly in the best shape. > I never encountered any problems writing fixed-size read-only images into > a dynamic UBI volume and just not using random-access write and dynamic > resize features. The cost of using dynamic volumes vs. static volumes also > seems neglectible (anyone?) You're missing the point. The point is UBI for a dynamic volume requires a bit less that 20 LEBs (I remember it being around 17, but I'm not sure anymore, and don't have the board here to test). 20 LEBs on a NAND with a PEB-size of 512k represents around 10MB. So far, OpenWRT generates UBI volumes for the rootfs that are of the size of the rootfs image you put in it, aligned on a PEB. Which makes sense. But for it to even just be mounted, this rootfs volume needs to be more 10MB. Which never happens. So there's two solutions here: - Don't make the rootfs volume dynamic - Align the rootfs volume on 20 PEBs, instead of a single one. The second solution is just dumb, especially when you try to make such aggressive changes to reduce the size of other components, while you waste ~7MB on the other side. I do believe it is the right solution. It might not be enforced at the right place (but where then? target? board level? we then fall back to another question I had that was unanswered on this same patch set...) Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com signature.asc Description: Digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)
On 15 November 2014 20:46, Michael Richardson wrote: > How do you know it's not the DSLAM being unstable? Erm... I don't? I'm not sure what that means. Is there some way that I can find out "from just my end" (the consumer end) of the connection? I've called my ISP regarding the disconnections, and their response is "Put our (supported) router back on, and we'll monitor the situation" - I do that, and obviously the problem then disappears. I put my Openwrt'd BTHOMEHUBV2B, and the problem starts again. Rinse, repeat... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] 4addr mode hangs on rekey on a WPA2+CCMP 802.1x network with ar71xx hardware
Hi everyone, I'm having the problem described in this bug I filed: https://dev.openwrt.org/ticket/18343 In the bug you can see I've tested various options and I've come to the conclusion that the problem is with 4addr mode being enabled (option wds '1'). The problem is made worse if I enable 802.11w Management Frame Protection along with 4addr mode. There is no problem at all with 4addr mode disabled. Is this a known problem? Could somebody help me debug this further? Thank you very much. Best regards, Vittorio G ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [packages] libdlna: fix build with ffmpeg 2.4.2
On 16.11.2014 09:45, Robert P. J. Day wrote:
>
> i checked trac and it seems that there is (still?) an ongoing issue
> with building libdlna, as i was trying to do for a tp-link archer c7
> v2:
>
> cc1: note: someone does not honour COPTS correctly, passed 2 times
> src/libdlna.so: undefined reference to `av_find_stream_info'
> src/libdlna.so: undefined reference to `av_close_input_file'
> collect2: error: ld returned 1 exit status
> Makefile:36: recipe for target 'test-libdlna' failed
> make[4]: *** [test-libdlna] Error 1
>
> that seems to match what i see here:
>
> https://dev.openwrt.org/ticket/11666
>
> is there a suggested fix for this? or i can just deselect it for now.
>
> rday
>
only compile tested
fixes error:
src/libdlna.so: undefined reference to `av_find_stream_info'
src/libdlna.so: undefined reference to `av_close_input_file'
collect2: error: ld returned 1 exit status
ffmpeg API changes:
av_find_stream_info -> avformat_find_stream_info
av_close_input_file -> avformat_close_input
patch libdlna instead of ffmpeg since recently
av_close_input_file got removed in upstream git
avformat: remove obsolete FF_API_CLOSE_INPUT_FILE cruft
Signed-off-by: Dirk Neukirchen
---
libs/libdlna/patches/200-parallel-build.patch | 4 ++--
libs/libdlna/patches/300-ffmpeg_compat.patch | 18 ++
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/libs/libdlna/patches/200-parallel-build.patch
b/libs/libdlna/patches/200-parallel-build.patch
index 7f9934b..0e1b942 100644
--- a/libs/libdlna/patches/200-parallel-build.patch
+++ b/libs/libdlna/patches/200-parallel-build.patch
@@ -2,8 +2,8 @@
Makefile |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
libdlna-0.2.3.orig/Makefile
-+++ libdlna-0.2.3/Makefile
+--- a/Makefile
b/Makefile
@@ -32,8 +32,8 @@ lib:
test: $(LIBTEST)
diff --git a/libs/libdlna/patches/300-ffmpeg_compat.patch
b/libs/libdlna/patches/300-ffmpeg_compat.patch
index 8fb9b39..7ab69d1 100644
--- a/libs/libdlna/patches/300-ffmpeg_compat.patch
+++ b/libs/libdlna/patches/300-ffmpeg_compat.patch
@@ -16,6 +16,24 @@
{
video_stream = i;
continue;
+@@ -287,7 +287,7 @@ dlna_guess_media_profile (dlna_t *dlna,
+ return NULL;
+ }
+
+- if (av_find_stream_info (ctx) < 0)
++ if (avformat_find_stream_info (ctx, NULL) < 0)
+ {
+ if (dlna->verbosity)
+ fprintf (stderr, "can't find stream info\n");
+@@ -334,7 +334,7 @@ dlna_guess_media_profile (dlna_t *dlna,
+ p = p->next;
+ }
+
+- av_close_input_file (ctx);
++ avformat_close_input (&ctx);
+ free (codecs);
+ return profile;
+ }
--- a/src/profiles.h
+++ b/src/profiles.h
@@ -25,6 +25,14 @@
--
2.1.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] libdlna won't build, allegedly due to missing dependencies
i checked trac and it seems that there is (still?) an ongoing issue with building libdlna, as i was trying to do for a tp-link archer c7 v2: cc1: note: someone does not honour COPTS correctly, passed 2 times src/libdlna.so: undefined reference to `av_find_stream_info' src/libdlna.so: undefined reference to `av_close_input_file' collect2: error: ld returned 1 exit status Makefile:36: recipe for target 'test-libdlna' failed make[4]: *** [test-libdlna] Error 1 that seems to match what i see here: https://dev.openwrt.org/ticket/11666 is there a suggested fix for this? or i can just deselect it for now. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
