On 2/13/07, Kyle Mott <[EMAIL PROTECTED]> wrote:
Ok, I think I found a way around it. All I have to do is specify
"-iface" to the route command line arguments. I can then (from
172.1.1.2) ping 10.10.100.x:
route add 172.1.1/24 10.20.100.1 -iface
Is there any way we can add the various flags to the webgui static route
page? Even if we have to do something like:
http://mypfsensefw.com/system_routes.php?advanced=1
-cloning RTF_CLONING - generates a new route on use
-xresolve RTF_XRESOLVE - emit mesg on use (for external lookup)
-iface ~RTF_GATEWAY - destination is directly reachable
-static RTF_STATIC - manually added route
-nostatic ~RTF_STATIC - pretend route added by kernel or daemon
-reject RTF_REJECT - emit an ICMP unreachable when matched
-blackhole RTF_BLACKHOLE - silently discard pkts (during updates)
-proto1 RTF_PROTO1 - set protocol specific routing flag #1
-proto2 RTF_PROTO2 - set protocol specific routing flag #2
-llinfo RTF_LLINFO - validly translates proto addr to link addr
I would think the best option here is to install the route with a shellcmd.
http://faq.pfsense.com/index.php?action=artikel&cat=10&id=38&artlang=en&highlight=hidden%20options
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
