Re: [OpenWrt-Devel] multiwan -- allocation of a port (i.e. vlan) for wan2

2011-10-20 Thread Daniel A. Nagy 
On 10/20/2011 09:08 PM, Brian J. Murrell wrote:
> Taking notice of https://dev.openwrt.org/changeset/20925 that looks like
> the bits needs to manage the balancing and failover for multiple WAN
> ports, which is great.
> 
> Is there any corresponding Luci component to manage the allocating of a
> new WAN port (i.e. creating of a new VLAN for a the new WAN port)?
> Currently I manually carve one of the "LAN" ports off into it's own VLAN
> to use as the second WAN port but having a Luci app for this would be great.
> 
> Cheers,
> b.

Hi Brian,

No, unfortunately there isn't one yet. But we need it too, so if nobody
implements it before us, we will contribute one before the end of the year.

-- 
Daniel A. Nagy



signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] multiwan -- allocation of a port (i.e. vlan) for wan2

2011-10-20 Thread Brian J. Murrell 
Taking notice of https://dev.openwrt.org/changeset/20925 that looks like
the bits needs to manage the balancing and failover for multiple WAN
ports, which is great.

Is there any corresponding Luci component to manage the allocating of a
new WAN port (i.e. creating of a new VLAN for a the new WAN port)?
Currently I manually carve one of the "LAN" ports off into it's own VLAN
to use as the second WAN port but having a Luci app for this would be great.

Cheers,
b.



signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Multiwan & qos (big qos-script modification)

2011-10-20 Thread Etienne Champetier 
Hello everyone

I've seen that there is qos related code in the multiwan script, so i've a 
question:

-How does we configure the qos with multiwan (i've seen anything in the 
documentation or ...)

I'm also using wifidog (captive portal) on another router, and wifidog use 
iptables MARK target (as qos-scripts and multiwan) and is thus incompatible 
with qos-scripts . I was wondering if it will help if qos-scripts was only 
using CLASSIFY target (and why it doesn't use it but i think it's related to it 
non existance in 2.4 kernel)

Thanks in advance
Etienne Champetier






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

Re: [OpenWrt-Devel] [PATCH] openl2tp - finally enable config file option

2011-10-20 Thread Philip Prindeville 
You need to turn off "flowed=true" when posting patches.


On 10/17/11 10:34 AM, Bogdan Roman wrote:
> Until now the openl2tpg package only allowed configuration through RPC 
> by using the l2tpconfig command, making many some tasks difficult. 
> Discussion exists at https://dev.openwrt.org/ticket/10164 . Enabling the 
> config file option requires working around the flex library ( (libfl) 
> and a few compile fixes. The following 2 patches enable the config file 
> option in addition to the RPC option. Tested against trunk r28428. Note 
> that the openwrt openl2tp package is still not fully finished, e.g. a 
> proper init.d script and sample conf files should be included, see 
> build_dir/*/openl2tp-1.8/{etc,ipsec}/*. I may sort that out as well later.
> 
> Signed-off-by: Bogdan Roman 
> 
> 
> File: 020-makefile-conf-file.patch
> 
> --- a/Makefile
> +++ b/Makefile
> @@ -8,7 +8,7 @@ L2TP_FEATURE_LAIC_SUPPORT=  y
>   L2TP_FEATURE_LAOC_SUPPORT= y
>   L2TP_FEATURE_LNIC_SUPPORT= y
>   L2TP_FEATURE_LNOC_SUPPORT= y
> -#L2TP_FEATURE_LOCAL_CONF_FILE= y
> +L2TP_FEATURE_LOCAL_CONF_FILE=  y
>   #L2TP_FEATURE_LOCAL_STAT_FILE= y
> 
>   # Define USE_DMALLOC to enable dmalloc memory debugging
> @@ -204,7 +204,7 @@ ifeq ($(L2TP_FEATURE_LOCAL_CONF_FILE),y)
>   # Config file parser
>   LEX=   flex
>   YACC=  bison
> -LDFLAGS.l2tpd+=-lfl
> +#LDFLAGS.l2tpd+=   -lfl
>   %.c:   %.l
>  $(LEX) -o$@ $<
> 
> @@ -212,10 +212,10 @@ LDFLAGS.l2tpd+=   -lfl
>  $(YACC) -d -o l2tp_config_parse.c $<
> 
>   l2tp_config_token.o:   l2tp_config_token.c
> -   $(CC) -I. -MMD -w $(CFLAGS.optimize) -c -DYY_NO_UNPUT $<
> +   $(CC) -I. -MMD -w $(CFLAGS.optimize) -c $(CPPFLAGS) 
> -DYY_NO_UNPUT $<
> 
>   l2tp_config_parse.o:   l2tp_config_parse.c l2tp_config_parse.h
> -   $(CC) -I. -MMD -w $(CFLAGS.optimize) -c -DYY_NO_UNPUT $<
> +   $(CC) -I. -MMD -w $(CFLAGS.optimize) -c $(CPPFLAGS) 
> -DYY_NO_UNPUT $<
>   endif
> 
>   # Compile without -Wall because rpcgen-generated code is full of warnings.
> 
> 
> File: 020-conf-no-libfl.patch
> 
> --- a/l2tp_config_token.l
> +++ b/l2tp_config_token.l
> @@ -23,6 +23,8 @@ static int resolveip(const char *val, st
>   int lineno;
>   int command;
> .
> +int yywrap(void) { return 1; }
> +
>   %}
> .
>   /* common section */
> 
> 

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

[OpenWrt-Devel] Can I somehow help to integrate the port mirroring patch?

2011-10-20 Thread Colin Leitner 
Hello,

is there something I can do to help getting this patch [1] integrated?

The ticket with the LuCI enhancement can be found in Trac [2], but I'm
not even sure how OpenWRT and LuCI devs interact with each other and if
the OpenWRT Trac is the right place for such enhancements.

Thanks to all of you for the great work that led to this great little
distro!

Bye,
Colin

[1]: http://patchwork.openwrt.org/patch/1466/
[2]: https://dev.openwrt.org/ticket/10202


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

Re: [OpenWrt-Devel] ПОКАНА Re: [PATCH] WR740N V3 support

2011-10-20 Thread Emmanuel Deloget 

Le 20/10/2011 11:28, NetworkPro a écrit :

Здравей, моля присъедини се към нашите усилия да популяризираме
тестваме и развиваме *WRT

http://www.mikrotik-bg.net/topic/2622-tl-wr741nd-%D1%81-openwrt/page__pid__31768__st__50#entry31768

Поздрави.


Ouch. Is this the signal for the return of WhiteRussian?

Joke aside, Google translate says this is a bulgarian post, and translate it to:

--8<
Hello, please join our efforts to promote
test and develop * WRT

http://www.mikrotik-bg.net/topic/2622-tl-wr741nd-%D1%81-openwrt/page__pid__31768__st__50#entry31768

Greetings.
-->8

Best regards,

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

Re: [OpenWrt-Devel] usb_modeswitch coldplug issues

2011-10-20 Thread D.S. Ljungmark 
On Wed, 2011-10-19 at 17:22 +0200, Daniel Golle wrote:
> I got a weird problem with usb_modeswitch and coldplugging. Though I somehow
> understand what could be the cause, I have a hard time figuring out a good
> solution
> So: libusb needs usbfs on /proc/bus/usb, so usb_modeswitch can work only after
> usbfs was mounted at the time of the hotplug(/coldplug) event (or even at the
> time when hotplug2 was started during init?!).
> a device needing modeswitch being already attached during boot results in a 
> loop of

> delaying the execution of usb_modeswitch by adding 'sleep 30' to
> /etc/hotplug.d/usb/20-usb_modeswitch just before calling usb_modeswitch 
> doesn't
> do the trick, as apparently usb_modeswitch and therefore libusb can see only 
> the
> mounts which were already there at the time of coldplugging...
> 
> possible solutions could be:
> a) load usb-core and mount usbfs before starting hotplug and/or coldplugging 
> any
> devices
> b) check for usb-devices in need of modeswitch independently of hotplug when
> everything else is completed
> c) maybe fix the hotplug2 worker_fork?
> 
> just in case anyone got a good idea, i'd appreciate it :)
> 


I had similar issues and solved it with a post-boot parse of the
USB-tree for the devices I'm interested in. It's ugly, but works if you
are only after coldplug for certain /(known)/ hardware.  

I couldn't find a generic solution that would be acceptable for OpenWRT,
though it'd be preferrable.

//Spider

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

Re: [OpenWrt-Devel] Cross compiling problems with libpcap

2011-10-20 Thread Jo-Philipp Wich 
Your gcc commandline lacks -lpcap, also never compile against host
headers when cross compiling, use the pcap headers in staging_dir.

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

[OpenWrt-Devel] Cross compiling problems with libpcap

2011-10-20 Thread 马进 
Hi, I am trying to cross compile a program for openwrt to capture the beacon
frames.
The program(beaconCap.c) is as follows.
*
#include
#include
#include
#include
#include
#include
#include
#include
#include

typedef struct mac_header
{
unsigned char fc[2];
unsigned char id[2];
unsigned char add1[6];
unsigned char add2[6];
unsigned char add3[6];
unsigned char sc[2];
}mac_header;

typedef struct frame_control
{
unsigned protocol:2;
unsigned type:2;
unsigned subtype:4;
unsigned to_ds:1;
unsigned from_ds:1;
unsigned more_frag:1;
unsigned retry:1;
unsigned pwr_mgt:1;
unsigned more_data:1;
unsigned wep:1;
unsigned order:1;
}frame_control;

typedef struct beacon_header
{
unsigned char timestamp[8];
unsigned char beacon_interval[2];
unsigned char cap_info[2];
}beacon_header;


void packet_decoder(u_char * useless, const struct pcap_pkthdr *pkthdr,
const u_char * packet)
{
printf("Got Packet");
char ssid[32], *temp;
struct mac_header *p = (struct mac_header *) packet;
struct frame_control *control = (struct frame_control *)p->fc;
temp = (char *)(packet + sizeof(struct mac_header)+sizeof(struct
beacon_header));

memset (ssid, '\0', 32);
// check if frame is beacon frame
if ((control->protocol==0)&&(control->type==0)&&(control->subtype==8))
{
//temp[1] contains the size of the ssid field and temp[2] the beginning
ofthe ssid string .
memcpy (ssid, &temp[2], temp[1]);
printf ("\n\nFound SSID : \n");
printf ("Destination Add : %s\n", ether_ntoa (p->add1));
printf ("Source Add : %s\n", ether_ntoa (p->add2));
printf ("BSSID : %s\n", ether_ntoa (p->add3));
printf ("ssid = %s\n", ssid);
}
}

int main(int argc, char **argv)
{
char *dev = argv[1];
char errbuf[PCAP_ERRBUF_SIZE];
pcap_t *handle;
if(argc<2)
{
printf ("usage : %s capture_device \n", argv[0]);
exit (1);
}

printf ("Initialising capture interface..\n");
//pcap initialisation

handle = pcap_open_live (dev, BUFSIZ, 1, -1, errbuf);

if (handle == NULL)
{
printf ("pcap_open_live : %s\n", errbuf);
exit (1);
}

printf ("\nStarting Capture ...\n");
// tell pcap to pass on captures frames to our packet_decoder fn
pcap_loop(handle, -1, packet_decoder, NULL);
return (0);
}
*

I have cross compiled libpcap 1.1 with openwrt mips tool chain in my ubuntu
10.04 64bit.
libpcap in installed in  /usr/local/lib
scorpio@scorpio-desktop:/usr/local/lib$ ls libpcap.
libpcap.a libpcap.solibpcap.so.1  libpcap.so.1.1.1

pcap.h in located in /usr/local/include
scorpio@scorpio-desktop:/usr/local/include$ ls pcap.h
pcap.h
only  #include 
exists in  /usr/local/include/pcap.h
However in /usr/local/include/pcap, another pcap.h is here and this is the
real pcap.h.
***
My problem is when I cross compiled beaconCap.c with
mips-openwrt-linux-gcc beaconCap.c -o beaconCap -L /usr/local/lib/ -I
/usr/local/include/
I got following errors:
/tmp/ccA7FOzC.o: In function `main':
beaconCap.c:   (.text+0x270): undefined reference to `pcap_open_live'
beaconCap.c:   (.text+0x2d8): undefined reference to `pcap_loop'
collect2: ld returned 1 exit status
***
I do not know how to solve it. Actually pcap_open_live and pcap_loop are
declared in  /usr/local/include/pcap/pcap.h

Could any help me? I really need you help.

Thank you,
Jin
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] correct fair traffic sharing support in qos-scripts

2011-10-20 Thread Dave Taht 
On Thu, Oct 20, 2011 at 11:55 AM, Weedy  wrote:

> On 08/10/11 10:41 AM, Dave Taht wrote:
> > I am getting towards being able to test both this and ipv6 support in
> > the qos-scripts6 packages in the ceropackages repo on github, but
> > various problems elsewhere (kernel.org  being out of
> > service notably) were stopping me. Perhaps next week.
> >
> > On Fri, Oct 7, 2011 at 2:53 PM, Weedy  > > wrote:
> >
> > On 25/09/11 01:21 PM, Dave Taht wrote:
> > > I am pleased to see this basic improvement to qos-scripts. I will
> be
> > > testing this patch soon in the cerowrt-1.0rc7 series if it doesn't
> get
> > > committed to openwrt head soon.
> >
> > Any luck?
>
> Yo
>

It's very near the top of my list. Regrettably at the top of my list are 2
talks and linuxcon. I made a start at fixing qos-scripts for ipv6 but still
lacks the above patch, in the ceropackages repo...

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] correct fair traffic sharing support in qos-scripts

2011-10-20 Thread Weedy 
On 08/10/11 10:41 AM, Dave Taht wrote:
> I am getting towards being able to test both this and ipv6 support in
> the qos-scripts6 packages in the ceropackages repo on github, but
> various problems elsewhere (kernel.org  being out of
> service notably) were stopping me. Perhaps next week.
> 
> On Fri, Oct 7, 2011 at 2:53 PM, Weedy  > wrote:
> 
> On 25/09/11 01:21 PM, Dave Taht wrote:
> > I am pleased to see this basic improvement to qos-scripts. I will be
> > testing this patch soon in the cerowrt-1.0rc7 series if it doesn't get
> > committed to openwrt head soon.
> 
> Any luck?

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

[OpenWrt-Devel] ПОКАНА Re: [PATCH] WR740N V3 support

2011-10-20 Thread NetworkPro 
Здравей, моля присъедини се към нашите усилия да популяризираме
тестваме и развиваме *WRT

http://www.mikrotik-bg.net/topic/2622-tl-wr741nd-%D1%81-openwrt/page__pid__31768__st__50#entry31768

Поздрави.

On 4 July 2011 20:30, Martin Raykov  wrote:
> Just added few lines following WR740N V1 patch and V3 patch from DD-Wrt.
> Tested it. Firmware uploads correctly through stock WebUI. I'm not sure if I
> made diff correctly.
>
> Signed-off-by: Martin Raykov martin.ray...@gmail.com
>
> Index: target/linux/ar71xx/image/Makefile
> ===
> --- target/linux/ar71xx/image/Makefile  (revision 27423)
> +++ target/linux/ar71xx/image/Makefile  (working copy)
> @@ -704,6 +704,11 @@
>     $(call
> Image/Build/Template/$(fs_64k)/$(1),TPLINK,tl-wr740n-v1,$(tlwe740nv1_cmdline),TL-WR740Nv1)
>  endef
>
> +tlwe740nv3_cmdline=board=TL-WR741ND console=ttyS0,115200
> +define Image/Build/Profile/TLWR740NV3
> +   $(call
> Image/Build/Template/$(fs_64k)/$(1),TPLINK,tl-wr740n-v3,$(tlwe740nv3_cmdline),TL-WR740Nv3)
> +endef
> +
>  tlwr841nv15_cmdline=board=TL-WR841N-v1.5 console=ttyS0,115200
>  define Image/Build/Profile/TLWR841NV15
>     $(call
> Image/Build/Template/$(fs_squash)/$(1),TPLINK,tl-wr841n-v1.5,$(tlwr841nv15_cmdline),TL-WR841Nv1.5)
> @@ -823,6 +828,7 @@
>     $(call Image/Build/Profile/TLWA901NDV2,$(1))
>     $(call Image/Build/Profile/TLWR741NDV1,$(1))
>     $(call Image/Build/Profile/TLWR740NV1,$(1))
> +   $(call Image/Build/Profile/TLWR740NV3,$(1))
>     $(call Image/Build/Profile/TLWR841NV15,$(1))
>     $(call Image/Build/Profile/TLWR841NDV3,$(1))
>     $(call Image/Build/Profile/TLWR841NDV5,$(1))
> Index: target/linux/ar71xx/generic/profiles/tp-link.mk
> ===
> --- target/linux/ar71xx/generic/profiles/tp-link.mk (revision 27423)
> +++ target/linux/ar71xx/generic/profiles/tp-link.mk (working copy)
> @@ -71,6 +71,19 @@
>
>  $(eval $(call Profile,TLWR740NV1))
>
> +
> +define Profile/TLWR740NV3
> +   NAME:=TP-LINK TL-WR740N v3
> +   PACKAGES:=kmod-ath9k wpad-mini
> +endef
> +
> +define Profile/TLWR740NV3/Description
> +   Package set optimized for the TP-LINK TL-WR740N v3.
> +endef
> +
> +$(eval $(call Profile,TLWR740NV3))
> +
> +
>  define Profile/TLWR841NV15
>     NAME:=TP-LINK TL-WR841N v1.5
>     PACKAGES:=kmod-ath9k wpad-mini
> Index: tools/firmware-utils/src/mktplinkfw.c
> ===
> --- tools/firmware-utils/src/mktplinkfw.c   (revision 27423)
> +++ tools/firmware-utils/src/mktplinkfw.c   (working copy)
> @@ -39,6 +39,7 @@
>  #define HWID_TL_WA901ND_V2 0x09010002
>  #define HWID_TL_WR741ND_V1 0x07410001
>  #define HWID_TL_WR740N_V1  0x0741
> +#define HWID_TL_WR740N_V3  0x07400300
>  #define HWID_TL_WR841N_V1_5    0x08410002
>  #define HWID_TL_WR841ND_V3 0x08410003
>  #define HWID_TL_WR841ND_V5 0x08410005
> @@ -169,6 +170,14 @@
>     .kernel_ep  = 0x8006,
>     .rootfs_ofs = 0x14,
>     }, {
> +   .id = "TL-WR740Nv3",
> +   .hw_id  = HWID_TL_WR740N_V3,
> +   .hw_rev = 1,
> +   .fw_max_len = 0x3c,
> +   .kernel_la  = 0x8006,
> +   .kernel_ep  = 0x8006,
> +   .rootfs_ofs = 0x14,
> +   }, {
>     .id = "TL-WR841Nv1.5",
>     .hw_id  = HWID_TL_WR841N_V1_5,
>     .hw_rev = 2,
>
>
> ___
> 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] printk() and browser

2011-10-20 Thread Alexey Loukianov 
18.10.2011 14:44, abhinav narain wrote:
> I wrote the following code ... its int he thread above also :
> 
> There are a lot of such errors on dmesg,
> when i compile the following lines of code in at_rx_tasklet() in recv.c
> 
> static int ai=0;
> if (ai==0) {
> printk("abhinav\n"); ai++ ;}
> 

OMFG, that's ridiculous!

How do you expect that someone would be able to help you when you don't specify:
* Your hardware (box vendor, box model, hw revision, e.t.c.).
* Type and version of the firmware you use. Is it at least OpenWRT? If is it
then do you use pre-compiled image downloaded from somewhere/someone? If you're
building it yourself - do you use released version of OpenWRT of stick with SVN
trunk? What build configuration do you use?
* You wrote that you're "modifying the driver for past few days". What is the
driver you're modifying? What are your goals? Why do you wand to modify 
something?
* You wrote that you can't connect to internet. I assume that you're trying to
connect to the internet using the router with the firmware you have built
containing some modifications to some unspecified driver. Is that a case?
* What are the exact symptoms of "can't connect to internet"? Had you tried to
ssh/telnet into the box and diagnose the connection problems from there?
* You wrote that "I am just doing opkg install ath9k_2.6.39.4+..ipk". When are
you "just doing" it? What do you want to achieve by executing this command?

P.S. Considering the overal quality of your "request for help" you had sent to
the list, taking into the account it's consistency and amount of details you
provide I wouldn't recommend you to mess with the kernel patching and editing
drivers source code at all.

-- 
Best regards,
Alexey Loukianov  mailto:mooro...@mail.ru
System Engineer,Mob.:+7(926)218-1320
*nix Specialist




signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel