[This question is more appropriate for -net IMHO]
-On [20010322 03:00], David E. Cross ([EMAIL PROTECTED]) wrote:
>I recently tried (for the first time) to get gif running under FreeBSD
>4.3-BETA (cvsup-ed yesterday). I noticed the following:
>
>gifconfig gif0 inet 10.1.1.1 10.1.2.1
>ifconfig gif0 192.168.1.1 192.168.1.2 netmask 0xffffff00
>
>and then I 'ping 192.168.1.1' it will try to route the packet instead of
>reply directly. I need to 'route add 192.168.1.1 127.0.0.1' to have it
>reply to the packet directly. I don't need to do this for other types
>of interfaces... did I mess something up, is this how it is supposed to
>be (doesn't seem to be documented as such).
I think that's how it is supposed to be given that gif's main function
is to tunnel things and it works on a point-to-point basis.
I might be wrong, in which case I am sure UMEMOTO-san or ITOJUN-san will
correct me.
--
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best
D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867
What is to be, will be. And what isn't to be sometimes happens...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
