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

2006-01-03 Thread Christer Folkesson
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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
  options=1aTXCSUM,VLAN_MTU,VLAN_HWTAGGING
  inet6 fe80::214:22ff:fee1:41be%bge0 prefixlen 64 scopeid 0x1
  inet 192.168.0.228 netmask 0xff80 broadcast 192.168.0.255
  ether 00:14:22:e1:41:be
  media: Ethernet autoselect (100baseTX full-duplex )
  status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
  inet 127.0.0.1 netmask 0xff00
alcoy# netstat -nr
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use  Netif Expire
default192.168.0.199  UGS 0   52   bge0
127.0.0.1  127.0.0.1  UH  0   52lo0
192.168.0.128/25   link#1 UC  00   bge0
192.168.0.199  00:09:5b:10:de:14  UHLW2  190   bge0   1182
192.168.0.210  00:05:5d:0c:f8:23  UHLW1   29   bge0

Internet6:
Destination   Gateway   
Flags  Netif Expire
::1   ::1   
UH  lo0
fe80::%bge0/64link#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/32link#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#








Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
  The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Thu Nov  3 09:36:13 UTC 2005
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: DELL   CPi R  
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) M processor 2.00GHz (1995.15-MHz 686-class CPU)
Origin = GenuineIntel  Id = 0x6d8  Stepping = 8

Features=0xafe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE 


Features2=0x180EST,TM2
AMD Features=0x10NX
real memory  = 1610448896 (1535 MB)
avail memory = 1569087488 (1496 MB)
ioapic0: Changing APIC ID to 1
ioapic0 Version 2.0 irqs 0-23 on motherboard
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: DELL CPi R   on motherboard
pci_link0: ACPI PCI Link LNKA irq 11 on acpi0
pci_link1: ACPI PCI Link LNKB irq 10 on acpi0
pci_link2: ACPI PCI Link LNKC irq 9 on acpi0
pci_link3: ACPI PCI Link LNKD irq 7 on acpi0
pci_link4: ACPI PCI Link LNKE on acpi0
pci_link5: ACPI PCI Link LNKF on acpi0
pci_link6: ACPI PCI Link LNKH on acpi0
Timecounter ACPI-fast frequency 3579545 Hz quality 1000

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

2006-01-03 Thread Danial Thom


--- Christer Folkesson [EMAIL PROTECTED]
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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST
 mtu 1500
   
 options=1aTXCSUM,VLAN_MTU,VLAN_HWTAGGING
inet6 fe80::214:22ff:fee1:41be%bge0
 prefixlen 64 scopeid 0x1
inet 192.168.0.228 netmask 0xff80
 broadcast 192.168.0.255
ether 00:14:22:e1:41:be
media: Ethernet autoselect (100baseTX
 full-duplex )
status: active
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST
 mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid
 0x2
inet 127.0.0.1 netmask 0xff00
 alcoy# netstat -nr
 Routing tables
 
 Internet:
 DestinationGatewayFlags   
 Refs  Use  Netif Expire
 default192.168.0.199  UGS  
   0   52   bge0
 127.0.0.1  127.0.0.1  UH   
   0   52lo0
 192.168.0.128/25   link#1 UC   
   00   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/64link#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/32link#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/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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

2006-01-03 Thread Greg Barniskis

Christer Folkesson 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.

[snip]

I may have snipped some clue to what's actually wrong, but don't let 
that discourage you from trying to file complete problem reports. 
I'm a snipper. What I found to be most relevant follows.



Internet:
DestinationGatewayFlagsRefs  Use  Netif Expire
default192.168.0.199  UGS 0   52   bge0

[snip]

This shows generally that the router IP is being properly used by 
FreeBSD as a gateway (Use = 52). Suggests that your assumption that 
FreeBSD isn't using the gateway properly is not correct.




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


[snip]

This shows the gateway IP is being properly used by FreeBSD as the 
appropriate route to ping.sunet.se. Indicates that the problem 
really is not FreeBSD's default route configuration or 
functionality. The route is clearly being used.




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

[snip]

This shows you communicating with the gateway directly (confirms the 
assertion that local LAN operations are doing just fine).



Since your packets are being routed and NATed by the gateway 
correctly when the box is in Windows mode, packets should be getting 
routed and NATed correctly for FreeBSD as well. That is, if the box 
in Windows mode is using the same IP number and mask as the FreeBSD 
settings (you should double check that it is).


If the gateway is running fine (seems to be) and FreeBSD is properly 
using the gateway (seems to be), then the most likely suspect seems 
to be firewall configuration -- after your connection is properly 
routed, reply packets from the Internet could be getting dropped on 
the floor by your gateway or by FreeBSD.


Have you configured any kind of packet filter (ipf, ipfw, other) for 
FreeBSD? Try disabling that and see if your results change. If so, 
tune your filtering rules accordingly.


Use of tcpdump -i bge0 may also be informative (see man tcpdump).


--
Greg Barniskis, Computer Systems Integrator
South Central Library System (SCLS)
Library Interchange Network (LINK)
gregb at scls.lib.wi.us, (608) 266-6348
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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

2006-01-03 Thread Glenn Dawson

At 07:18 AM 1/3/2006, Christer Folkesson 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.


I don't see anything obviously wrong with the configuration info you 
sent below.  The problem you are having is more likely in the router 
you are using, but without that configuration info, it's impossible to tell.


Are you using dhcp to assign IP addresses?  If so, is the router 
doing that job or something else?


Since you mentioned that it works when you boot into windows, are the 
network settings the same? (IP, netmask, default route ,etc) or is 
windows configured to use something different?


How is NAT configured in the router?  Does it's configuration cover 
the 192.168.0.228 address?


-Glenn





alcoy# ifconfig
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
  options=1aTXCSUM,VLAN_MTU,VLAN_HWTAGGING
  inet6 fe80::214:22ff:fee1:41be%bge0 prefixlen 64 scopeid 0x1
  inet 192.168.0.228 netmask 0xff80 broadcast 192.168.0.255
  ether 00:14:22:e1:41:be
  media: Ethernet autoselect (100baseTX full-duplex )
  status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
  inet 127.0.0.1 netmask 0xff00
alcoy# netstat -nr
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use  Netif Expire
default192.168.0.199  UGS 0   52   bge0
127.0.0.1  127.0.0.1  UH  0   52lo0
192.168.0.128/25   link#1 UC  00   bge0
192.168.0.199  00:09:5b:10:de:14  UHLW2  190   bge0   1182
192.168.0.210  00:05:5d:0c:f8:23  UHLW1   29   bge0

Internet6:
Destination   Gateway
Flags  Netif Expire
::1   ::1
UH  lo0
fe80::%bge0/64link#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/32link#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#








Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
  The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Thu Nov  3 09:36:13 UTC 2005
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: DELL   CPi R  
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) M processor 2.00GHz (1995.15-MHz 686-class CPU)
Origin = GenuineIntel  Id = 0x6d8  Stepping = 8
Features=0xafe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE 


Features2=0x180EST,TM2
AMD Features=0x10NX
real memory  = 1610448896 (1535 MB)
avail memory = 1569087488 (1496 MB)
ioapic0: Changing APIC ID to 1
ioapic0 Version 2.0 irqs 0-23 on motherboard
npx0: [FAST]
npx0: