Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Mar 2000 14:32:38 -0500
From:      "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com>
To:        Mike Caudill <mcaudill@cisco.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: default routes problem
Message-ID:  <20000318143238.B72361@cc942873-a.ewndsr1.nj.home.com>
In-Reply-To: <20000318111931.B3578@cisco.com>; from mcaudill@cisco.com on Sat, Mar 18, 2000 at 11:19:31AM -0500
References:  <20000318111931.B3578@cisco.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 18, 2000 at 11:19:31AM -0500, Mike Caudill wrote:
> I think this might be a bug, and searching has produced no results on it 
> being reported yet.
> 
> Here is the situation
> 
>                   (net 1)
> FreeBSD pc ---------------------- rtr 1 
>                                     |
>                                     |
>                                     | (net 2)
>                                     |
>                                     |
>                                   rtr 2 -------------------- Windoze PC1
>                                             |  (net 3)
>                                             |
>                                             |
>                                             |--------------- Windoze PC2
> 
> 
> net 1 - 1.1.1.X     rtr 1 is 1.1.1.1, FreeBSD pc is 1.1.1.2
> net 2 - 2.2.2.X, but doesnt really matter
> net 3 - 3.3.3.X     rtr 2 is 3.3.3.1 WinPC1 is 3.3.3.3, winpc2 is 3.3.3.4
> 
> FreeBSDpc has default gateway set to 1.1.1.1
> Both Windows pcs have their default gateways set to 3.3.3.1
> 
> FreeBSDpc can talk to WinPC1, but not WINpc 2.  Both rtr1 and rtr2 can
> talk to winpc1 and winpc2.  There are no access lists,  firewalls, or NAT
> going on. 
> 
> Winpc2 can talk to other hosts on net1 just fine.
> 
> So, on FreeBSD pc, I add a static route for the network.
> 
> route add 3.3.3.0 1.1.1.1
> 
> still cant talk to winpc2.
> 
> route add 3.3.3.4 1.1.1.1
> 
> now the two can finally talk to each other.  This is not an arp issue, as
> all hosts and routers have the correct arp entries (otherwise the rtrs 
> themselves could not have had conversations with the winpcs).
> 
> It seems like there might be a bug in the routing table lookups.  I have seen
> this problem before on another machine, but dismissed it as a possible fluke
> which seemed to go away after a reboot.  Now I am seeing it again on 
> another machine.

When trying to ping WinPC2 from FreeBSDpc, what does tcpdump(8) give?

  # tcpdump -en host WinPC2

What does your routing table look like, netstat -rn?
-- 
Crist J. Clark                           cjclark@home.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000318143238.B72361>