[wplug-bsd] Dumb question: "no route to host" but why?

[Poyner, Brandon]

Ok, from the output of your ifconfig, you can see why FreeBSD isn't
happy with the route.

>          media: Ethernet autoselect (none)
>          status: no carrier

That should say something more like:

        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

There could potentially be an IRQ conflict with the cards, historically
I've had bad luck trying to run two Intel EEPro cards in the same
server.  I think I've sometimes made it work by moving the cards to
other PCI slots, and always made it work by using a mismatch of brands.
Also check for link light and/or try switching the cable. 

Brandon Poyner
Network Engineer III
CCAC - College Office
412-237-3086
 
 

> -----Original Message-----
> From: wplug-bsd-bounces+bpoyner=ccac.edu at wplug.org 
> [mailto:wplug-bsd-bounces+bpoyner=ccac.edu at wplug.org] On 
> Behalf Of Brandon Kuczenski
> Sent: Thursday, July 07, 2005 12:46 PM
> To: WPLUG BSD user group
> Subject: RE: [wplug-bsd] Dumb question: "no route to host" but why?
> 
> On Thu, 7 Jul 2005, Poyner, Brandon wrote:
> 
> > What is the output from 'ifconfig xl0' and 'route get 192.168.1.1' ?
> >
> 
> $ ifconfig xl0
> xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>          options=9<RXCSUM,VLAN_MTU>
>          inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
>          inet6 fe80::250:4ff:fed3:e73%xl0 prefixlen 64 scopeid 0x1
>          ether 00:50:04:d3:0e:73
>          media: Ethernet autoselect (none)
>          status: no carrier
> $ route get 192.168.1.1
>     route to: dslrouter
> destination: 192.168.1.0
>         mask: 255.255.255.0
>    interface: xl0
>        flags: <UP,DONE,CLONING>
>   recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu 
> expire
>         0         0         0         0         0         0      1500 
> -62945
> $ ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
> ping: sendto: No route to host