Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!usna!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards,net.lan
Subject: Re: IP-Ethernet Routing Problem (4.2)
Message-ID: <1748@umcp-cs.UUCP>
Date: Thu, 3-Oct-85 16:10:56 EDT
Article-I.D.: umcp-cs.1748
Posted: Thu Oct  3 16:10:56 1985
Date-Received: Sat, 5-Oct-85 07:23:02 EDT
References: <6@uscvax.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 20
Xref: watmath net.unix-wizards:15085 net.lan:1056

I cannot say for certain that this is your problem, but I recall a bug
in the distributed 4.2 code.  In netinet/ip_output.c, inside ip_output(),
if you have a bit of code that reads

	if (ro->ro_rt == 0 || (ifp = ro->ro_rt->rt_ifp) == 0) {
		error = ENETUNREACH;
		goto bad;
	}
	ro->ro_rt->rt_use++;
	if (ro->ro_rt->rt_flags & RTF_GATEWAY)
		dst = &ro->ro_rt->rt_gateway;

change the last two lines to

	if (ro->ro_rt->rt_flags & (RTF_GATEWAY|RTF_HOST))
		dst = &ro->ro_rt->rt_gateway;
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu