Date: Thu, 08 Feb 2007 21:19:05 -0800 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-current@freebsd.org Subject: Re: Error adding route on 7-CURRENT Message-ID: <45CC0449.7010107@u.washington.edu> In-Reply-To: <45CC011B.8060805@u.washington.edu> References: <45CC011B.8060805@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote: > For some odd reason my host seems hosed and I can't reach the outside > world (odd enough..). Any thoughts? > > My system running 6.2 RELEASE has almost the same exact options (just > slightly different hardware and a little less kernel options) and it > functions perfectly fine. > > [root@hoover /store]# route add default 192.168.40.1 > route: writing to routing socket: Network is unreachable > add net default: gateway 192.168.40.1: Network is unreachable > [root@hoover /store]# netstat -nr > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > 192.168.10 link#1 UC 0 0 sis0 > 192.168.10.41 00:e0:7d:f7:6e:2e UHLW 1 444 sis0 977 > 192.168.10.255 ff:ff:ff:ff:ff:ff UHLWb 1 71 sis0 > [root@hoover /store]# uname -a > FreeBSD hoover.localdomain 7.0-CURRENT FreeBSD 7.0-CURRENT #20: Sun Jan > 21 12:04:41 PST 2007 > gcooper@hoover.localdomain:/usr/obj/usr/src/sys/HOOVER i386 > > Networking functions perfectly fine within LAN and doesn't access WAN at > all really (part of the reason why this isn't super high priority, but I > do find it annoying). And yes, 192.168.40.1 is the gateway and I did > specify the route create directive properly in /etc/rc.conf. > -Garrett Nevermind. I just accidentally flip flopped some numbers... -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45CC0449.7010107>