Date: Sun, 17 Feb 2002 13:04:47 +1100 (EST) From: Edwin Groothuis <edwin@mavetju.org> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/35017: /sbin/route: weird behaviour with using the -interface flag Message-ID: <20020217020447.5E05F42B@k7.mavetju.org>
next in thread | raw e-mail | index | archive | help
>Number: 35017 >Category: bin >Synopsis: /sbin/route: weird behaviour with using the -interface flag >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 16 18:10:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Edwin Groothuis >Release: FreeBSD 4.5-RELEASE i386 >Organization: - >Environment: System: FreeBSD k7.mavetju.org 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Fri Feb 1 09:51:30 EST 2002 edwin@k7.mavetju.org:/usr/src/sys/compile/k7 i386 Running the net/freenet6-port, revision 0.9.5 FreeBSD 4.5 specific, FreeBSD 4.4. didn't have this problem. >Description: See also http://docs.freebsd.org/cgi/getmsg.cgi?fetch=167189+0+current/freebsd-net During the setup of an IPv6 over IPv4 tunnel, the freenet port uses the statement: "route add -inet6 default -interface gif0" When sending TCP traffic over this tunnel, the first few packets get send without problems until my host starts sending out CMP6 neighbor solicitation requests. From that moment on, my host doesn't send any packet anymore for this TCP session. New TCP sessions can be start without problems (but experience the same problems), ICMP6 packets of other sessions keep flowing without interruption. It's only this TCP session which is hanging. I've posted a message about this in -hackers and -net and got two groups of answers: yes I have the same problem and no I don't have this problem anymore since I've changed to a different IPv6 provider. When comparing what was going different with different providers, I saw they were issueing the "route add -inet6 default ipaddress" statement instead of the "route add -inet6 default -interface ..." statement. When using this statement in the scripts of freenet6 my tunnels stayed up without problems. I have informed the people from freenet6.net about this, I have submitted a patch for the net/freenet6 port. But the real problem lies somewhere in the way FreeBSD 4.5 is looking through its routing-table. >How-To-Repeat: Install net/freenet6 version 0.9.5 and setup a tcp-session towards an IPv6 enabled host. >Fix: Unfortunatly I'm not skilled enough to fix what is going wrong here... >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020217020447.5E05F42B>