Date: Fri, 24 Jan 1997 17:41:17 -0500 (EST) From: Paul Sandys <myj@nyct.net> To: Julian Elischer <julian@whistle.com> Subject: Re: kern/2569: route -iface breaks inet behaivour Message-ID: <Pine.BSF.3.95.970124172931.15962B-100000@bsd1.nyct.net> Resent-Message-ID: <Pine.BSF.3.95.970124223304.10279A@bsd1.nyct.net> In-Reply-To: <32E896C8.41C67EA6@whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Jan 1997, Julian Elischer wrote:
> Date: Fri, 24 Jan 1997 03:02:32 -0800
> From: Julian Elischer <julian@whistle.com>
> To: myj@nyct.net
> Subject: Re: kern/2569: route -iface breaks inet behaivour
>
> Paul Sandys wrote:
> >
> > >Number: 2569
> > >Category: kern
> > >Synopsis: route -iface breaks inet behaivour
> > >Confidential: no
> > >Severity: serious
> > >Priority: high
> > >Responsible: freebsd-bugs
> > >State: open
> > >Class: sw-bug
> > >Submitter-Id: current-users
> > >Arrival-Date: Thu Jan 23 23:10:01 PST 1997
> > >Last-Modified:
> > >Originator: Paul Sandys
> > >Organization:
> > New York Connect
> > >Release: FreeBSD 2.1.6.1-RELEASE i386
> > >Environment:
> >
> > interface ed0 is on 204.141.86.0/24 and 207.198.184.0/22
> >
> > >Description:
> > This is configuration of ed0 interface:
> >
> > ifconfig ed0 204.141.86.3 netmask 0xffffff00
> > ifconfig ed0 204.141.86.xxx netmask 0xffffffff alias - lot of virtual addr.
> > route add -net 207.198.184.0 -netmask 0xfffffc00 204.141.86.3 -iface
> >
> > After issuing route command, all outgoing connections (telnet rlogin etc.)
> > are originating from random IP address assigned to ed0, not from
> > 204.141.86.3
> >
> > >How-To-Repeat:
> >
> > create simillar environment
>
> WHY ARE YOU DOING THAT!??? -iface requires a following argument..
> like -netmask does..
-iface doesn't require any parameter, it's just a flag.
>From route manpage:
Routes have associated flags which influence operation of the protocols
when sending to destinations matched by the routes. These flags may
be set (or sometimes cleared) by indicating the following corresponding
modifiers:
-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
end snip
>
> for Point to point links you can say:
>
> route add default -iface "ppp0"
That's nonsense
>
> for enet interfaces..
> route add 1.1.1.1 -iface 192.198.1.2 (or some address on one of
> your interfaces.. (though I'm not clear on why one would do that..
This means route add -host 1.1.1.1 -gateway 192.198.1.2 -iface
>
> >Fix:
> >
> > I wish I knew.
> >
> > >Audit-Trail:
> > >Unformatted:
>
P.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970124172931.15962B-100000>