All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pankaj Agarwal" <pankaj@toughguy.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help - Getting an error when trying to add prio to tables....
Date: Sat, 05 Feb 2005 17:29:55 +0000	[thread overview]
Message-ID: <00a101c50ba6$a6fde160$8d00150a@dreammac> (raw)
In-Reply-To: <003c01c50b97$62f77940$8d00150a@dreammac>

tried these but not working... i edited the file /usr/src/linux/.config

CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_LARGE_TABLES=y

looking for you help


----- Original Message ----- 
From: "Endre SZABO" <snitt@urbnet.hu>
To: "Pankaj Agarwal" <pankaj@toughguy.net>
Cc: <lartc@mailman.ds9a.nl>
Sent: Saturday, February 05, 2005 10:39 PM
Subject: Re: [LARTC] Help - Getting an error when trying to add prio to 
tables....


> compile a kernel with the required options checked first, like:
>
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ADVANCED_ROUTER=y
>
> but i'm not sure if these are the required ones.
>
> 73, Snitt
>
> .-- Valaszul Pankaj Agarwal levelere:
>
> |Hi,
> |
> |I am getting the errors given below, when I am trying to add the prio to 
> any
> |table. What can be the problem and how can i resolve it.... Kindly help
> |
> |[root /root]# ip rule
> |RTNETLINK answers: Invalid argument
> |Dump terminated
> |
> |[root /root]# ip rule list
> |RTNETLINK answers: Invalid argument
> |Dump terminated
> |
> |[root /root]# ip rule list table main
> |"ip rule show" need not eny arguments.
> |
> |[root /root]# ip rule show
> |RTNETLINK answers: Invalid argument
> |Dump terminated
> |
> |[root /root]# ip rule add prio 50 table main
> |RTNETLINK answers: Invalid argument
> |
> |[root /root]# ip route
> |192.168.2.5 dev eth1  scope link
> |61.11.104.63 dev eth0  scope link
> |220.227.153.48/28 dev eth2  proto kernel  scope link  src 220.227.153.61
> |192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.5
> |61.11.104.0/24 dev eth0  proto kernel  scope link  src 61.11.104.63
> |127.0.0.0/8 dev lo  scope link
> |default via 61.11.104.1 dev eth0
> |
> |[root /root]# ip
> |Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
> |where  OBJECT := { link | addr | route | rule | neigh | tunnel |
> |           maddr | mroute | monitor }
> |OPTIONS := { -V[ersion] | -s[tatistics] | -r[esolve] |
> |-f[amily] { inet | inet6 | ipx | dnet | link }
> || -o[neline] }
> |
> |Thanks and Regards,
> |
> |Pankaj Agarwal
> |_______________________________________________
> |LARTC mailing list / LARTC@mailman.ds9a.nl
> |http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> |
> |
> | 

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2005-02-05 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05 15:40 [LARTC] Help - Getting an error when trying to add prio to tables Pankaj Agarwal
2005-02-05 17:09 ` [LARTC] Help - Getting an error when trying to add prio to Endre SZABO
2005-02-05 17:29 ` Endre SZABO
2005-02-05 17:29 ` Pankaj Agarwal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00a101c50ba6$a6fde160$8d00150a@dreammac' \
    --to=pankaj@toughguy.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.