search

ypy705 / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

Unable to create IPv4 routing Rules #654

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Setting up routing rules using the "ip rule add from xxx.xxx.xxx.xxx to 
xxx.xxx.xxx.xxx table xx" to direct traffic a certain way
2.
3.

What is the expected output? What do you see instead?
I expect that the rules get added but instead I get this output 

"/opt/home/admin # ip rule add from 192.168.1.224 to 192.168.0.10 table main 
RTNETLINK answers: Address family not supported by protocol" 

I also  notice that there are no IPv4 tables. When I type in the command "ip 
rule list" I get nothing for the output. I noticed though that for IPv6 there 
are tables. This is the output.

/opt/home/admin # ip -f inet6 rule list
0:      from all lookup local
32766:  from all lookup main

What version of the product are you using? On what operating system?

RT-N56U_3.0.3.1v-027

Please describe the problem as detailed as it's possible.
I am trying to direct traffic from certain clients to go over a vpn that i am 
using. I do not want all traffic to go over the vpn. It seems as though ipv4 ip 
rules are not there. Is there something that I am missing? Is there another way 
to do this? I can set up rules on the Asus stock firmware but there are many 
features not available on the stock firmware. If anyone can help, I would very 
much appreciate it. Thank you.

Original issue reported on code.google.com by matthew....@gmail.com on 25 Dec 2012 at 4:50

GoogleCodeExporter commented 8 years ago 
BTW this is a great firmware

Original comment by matthew....@gmail.com on 27 Dec 2012 at 4:27

GoogleCodeExporter commented 8 years ago 
I have had the same issue. Solution is to compile it with additional kernel 
options:
CONFIG_IP_ADVANCED_ROUTER=y 
CONFIG_IP_MULTIPLE_TABLES=y

Original comment by anton.me...@gmail.com on 29 Jan 2013 at 12:53

GoogleCodeExporter commented 8 years ago 
anton,

That worked perfectly. I had to get Ubuntu up and running to compile the 
firmware. I noticed though that these options were already configured when I 
pulled the source yesterday. I think that pas already made the change. Once 
again thanks.

This problem is fixed from my end.

Original comment by matthew....@gmail.com on 31 Jan 2013 at 8:31

GoogleCodeExporter commented 8 years ago

Original comment by andy.pad...@gmail.com on 14 Mar 2013 at 3:31