Hi guys,
Any Idea about this?:
[root@localhost nftables]# make
make all-recursive
make[1]: Entering directory `/root/nftables'
Making all in src
make[2]: Entering directory `/root/nftables/src'
make all-am
make[3]: Entering directory `/root/nftables/src'
CC main.o
In file included from ../include/netlink.h:10,
from main.c:25:
/usr/include/linux/netlink.h:35: error: expected specifier-qualifier-list before ‘sa_family_t’
make[3]: *** [main.o] Error 1
make[3]: Leaving directory `/root/nftables/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/nftables/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/nftables'
make: *** [all] Error 2
Thanks & Best Regards,
Danilo Magat
eZeLink Telecom
www.ezelink.com
Ph: +971 4 457 2218 Ext: 110
Facebook - Twitter - LinkedIn - G+ - Pinterest - Instagram
Bay Square Building 06 - Office No 105 - Business Bay
P.O Box 111581, Dubai, UAE
Note: My Email Id is changed from danny@xxxxxxxx to danny@xxxxxxxxxxx, please update in your record.
-----Original Message-----
From: Arturo Borrero Gonzalez [mailto:arturo.borrero.glez@xxxxxxxxx]
Sent: Thursday, March 12, 2015 3:27 PM
To: danny@xxxxxxxxxxx
Cc: Netfilter Users Mailing list
Subject: Re: ebtables vlan captive portal
On 12 March 2015 at 04:39, <danny@xxxxxxxxxxx> wrote:
> http://s16.postimg.org/e5nu6g1md/bridgevlancaptive.png
>
> The above image link is based on my project about captive portal. As
> you can see on the image i have a diagram on LEFT side which is
> WORKING without a problem on a normal scenario without any vlan.
>
> On RIGHT side however, it is similar to the setup on left side but it
> is with multiple VLAN.
>
> I am having difficulties on finding the solution on this. need your input.
>
> Currently im looking at ebtables form the link
>
If you're planning a new project based on ebtables, would you consider taking a look into nftables?
best regards.
--
Arturo Borrero González
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
