FreeBSD 6.0: Problem with network, doesn't use default gateway

[Danial Thom]

--- Christer Folkesson <christer at aqualize.tk>
wrote:

> Hi, this is my first message to the
> mailing-list. I hope that I have 
> included
> enough information about the problem.
> 
> The problem is that my FreeBSD 6.0 (release)
> won't use the default route
> (gateway). So I can't access anything on the
> internet.
> 
> Hardware and network equipment:
> Dell latitude D810 (Pentium M 2.0 GHz, 1.5 GB
> of primary memory, broadcom
> gigabit/fast/"normal" ethernet controller).
> The broadcom chip uses the bge driver. I have
> looked in the man page for 
> that
> and no troubles or something like that is
> mentioned.
> IPv4 address: 192.168.0.228 /25
> 
> The gateway is a netgear RP614 broadband
> router. IPv4: 192.168.0.199 /25
> 
> Also a windows 2003 server is acting as
> DNS-server for my network.
> 
> FreeBSD shares the computer with windows XP pro
> SP2 using dual boot.
> In windows it works fine so this convince me
> that it's a software 
> problem in
> FreeBSD.
> 
> As said, it works perfectly fine inside the
> LAN, but not outside.
> 
> 
> I include a dmesg output (at the bottom) if
> that is of any importance 
> and also
> output from ifconfig, netstat -nr, ping and
> traceroute.
> I was logged in as root while testing this.
> Notice that because I'm using an internal
> DNS-server I can do lookups.
> Obviously that wouldn't have been possible with
> the DNS-server provided 
> by my
> ISP.
> 
> 
> 
> alcoy# ifconfig
> bge0:
>
flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> mtu 1500
>       
> options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
>        inet6 fe80::214:22ff:fee1:41be%bge0
> prefixlen 64 scopeid 0x1
>        inet 192.168.0.228 netmask 0xffffff80
> broadcast 192.168.0.255
>        ether 00:14:22:e1:41:be
>        media: Ethernet autoselect (100baseTX
> <full-duplex> )
>        status: active
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST>
> mtu 16384
>        inet6 ::1 prefixlen 128
>        inet6 fe80::1%lo0 prefixlen 64 scopeid
> 0x2
>        inet 127.0.0.1 netmask 0xff000000
> alcoy# netstat -nr
> Routing tables
> 
> Internet:
> Destination        Gateway            Flags   
> Refs      Use  Netif Expire
> default            192.168.0.199      UGS      
>   0       52   bge0
> 127.0.0.1          127.0.0.1          UH       
>   0       52    lo0
> 192.168.0.128/25   link#1             UC       
>   0        0   bge0
> 192.168.0.199      00:09:5b:10:de:14  UHLW     
>   2      190   bge0   1182
> 192.168.0.210      00:05:5d:0c:f8:23  UHLW     
>   1       29   bge0
> 
> Internet6:
> Destination                       Gateway      
>                 
> Flags      Netif Expire
> ::1                               ::1          
>                 
> UH          lo0
> fe80::%bge0/64                    link#1       
>                 
> UC         bge0
> fe80::214:22ff:fee1:41be%bge0    
> 00:14:22:e1:41:be             
> UHL         lo0
> fe80::%lo0/64                     fe80::1%lo0  
>                 
> U           lo0
> fe80::1%lo0                       link#2       
>                 
> UHL         lo0
> ff01::/32                         ::1          
>                 
> U           lo0
> ff02::%bge0/32                    link#1       
>                 
> UC         bge0
> ff02::%lo0/32                     ::1          
>                 
> UC          lo0
> alcoy# traceroute ping.sunet.se
> traceroute to ping.sunet.se (130.242.80.31), 64
> hops max, 40 byte packets
> 1  sentinel (192.168.0.199)  0.524 ms  0.518 ms
>  0.515 ms
> 2  * * *
> ^C
> alcoy# ping sentinel
> PING router.aqualize.tk (192.168.0.199): 56
> data bytes
> 64 bytes from 192.168.0.199: icmp_seq=0 ttl=250
> time=0.669 ms
> 64 bytes from 192.168.0.199: icmp_seq=1 ttl=250
> time=0.679 ms
> 64 bytes from 192.168.0.199: icmp_seq=2 ttl=250
> time=0.673 ms
> 64 bytes from 192.168.0.199: icmp_seq=3 ttl=250
> time=0.673 ms
> ^C
> --- router.aqualize.tk ping statistics ---
> 4 packets transmitted, 4 packets received, 0%
> packet loss
> round-trip min/avg/max/stddev =
> 0.669/0.673/0.679/0.004 ms
> alcoy#

It seems obvious from the traceroute that its
going to the gateway. Since the address of the
system is not a legal internet address, its
likely a NAT problem. I'd look closely at the
windows setup to see what might be different.

DT


	
		
__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/