Network connection works fine, and then...

[snes-addict]

...suddenly, as of yesterday, I cannot access most websites. The other computers on the network seem to work, and when booting into a live GNU/Linux on my OpenBSD box, everything also works. I'm pretty darn sure that this is config related, but I'm not sure where I went wrong.

What's bizzare about this is that some sites, such as daemonforums.org, netbsd.org, openbsd.org, and linux.org work fine, even though I cannot even get simple requests from most websites.

Here is a very rough visual of the network. Nothing special.

 _______________________
(                       )
(       Internet        )
(_______________________)
           | |
           | |
        ___| |___
       |         |
       |  Modem  |
       |_________|              _________
            ||                 |         |
         ___||___            __| Printer |
        |        |          |  |_________|
        | router |          |
        |________|          |        _________________
          | | | |___________|       |                 |
          | | |_____________________| OpenBSD Machine | -Partial Internet >:(
          | |___________________    |_________________|
     _____|_____________        |___________________
    |                   |       |                   |
    | Windows Machine 1 |       | Windows Machine 2 |
    |___________________|       |___________________|

My /etc/hosts file:

#       $OpenBSD: hosts,v 1.11 2002/09/26 23:35:51 krw Exp $
#
# Host Database
#
# RFC 1918 specifies that these networks are "internal".
# 10.0.0.0      10.255.255.255
# 172.16.0.0    172.31.255.255
# 192.168.0.0   192.168.255.255
#
::1 localhost.domain.actdsltmp localhost
127.0.0.1 localhost.domain.actdsltmp localhost
::1 puffin.domain.actdsltmp puffin
127.0.0.1 puffin.domain.actdsltmp puffin

192.168.0.3   router.domain.actdsltmp router
192.168.0.4   router.domain.actdsltmp router
192.168.1.100 puffin.domain.actdsltmp puffin

And here's some more:

puffin:ken {22} route -n show -inet
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use    Mtu  Interface
default            192.168.1.1        UGS         0      527      -   vr0
127/8              127.0.0.1          UGRS        0        0  33208   lo0
127.0.0.1          127.0.0.1          UH          2        4  33208   lo0
192.168.1/24       link#1             UC          2        0      -   vr0
192.168.1.1        MAC addr           UHLc        1        0      -   vr0
192.168.1.100      127.0.0.1          UGHS        0        0  33208   lo0
192.168.1.101      MAC addr           UHLc        0        0      -   vr0
224/4              127.0.0.1          URS         0        0  33208   lo0

I hope that I've provided enough correct information.

Any suggestions on this?

[phoenix]

Static IP or DHCP?

Sounds like a DNS issue.

Anything in /etc/resolv.conf?

What happens if you run ping www.google.com in a terminal? Or ping 208.67.217.231?

If the first fails and the second succeeds, then your system is having problems querying DNS servers.

[snes-addict]

I'm using DHCP.

puffin:ken {27} cat /etc/resolv.conf
search domain.actdsltmp
nameserver 192.168.0.1
nameserver 205.171.3.26
lookup file bind

puffin:ken {23} ping -c5 google.com
PING google.com (72.14.207.99): 56 data bytes
64 bytes from 72.14.207.99: icmp_seq=0 ttl=245 time=77.586 ms
64 bytes from 72.14.207.99: icmp_seq=1 ttl=245 time=77.115 ms
64 bytes from 72.14.207.99: icmp_seq=2 ttl=245 time=74.625 ms
64 bytes from 72.14.207.99: icmp_seq=3 ttl=245 time=75.068 ms
64 bytes from 72.14.207.99: icmp_seq=4 ttl=245 time=76.961 ms
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 74.625/76.271/77.586/1.189 ms

puffin:ken {24} ping -c5 208.67.217.231
PING 208.67.217.231 (208.67.217.231): 56 data bytes
64 bytes from 208.67.217.231: icmp_seq=0 ttl=55 time=65.500 ms
64 bytes from 208.67.217.231: icmp_seq=1 ttl=55 time=64.874 ms
64 bytes from 208.67.217.231: icmp_seq=2 ttl=55 time=64.551 ms
64 bytes from 208.67.217.231: icmp_seq=3 ttl=55 time=64.721 ms
64 bytes from 208.67.217.231: icmp_seq=4 ttl=55 time=65.130 ms
--- 208.67.217.231 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 64.551/64.955/65.500/0.369 ms

[ai-danno]

You appear to have references to two different private networks... 192.168.1.0/24 and 192.168.0.0/24. This screws up your DNS as the first DNS server listed is not your actual DNS server-

192.168.0.1 is listed as your first nameserver, but your default gateway in the routing table is listed as 192.168.1.1.

So you can probably ping the heck outta IP addresses, but more than half the time you will not be able to resolve DNS (the backup nameserver appears to be a real address.)

Now, of course, I'm wrong about this if, in fact, you really have a 192.168.0.1, but even then, your machine has to route to the router to get to that nameserver, and that particular host isn't represented in the information you provided anywhere.

Also, if my hunch is correct, you will also want to correct in any entries in your hosts file that make reference to 192.168.0.x to 192.168.1.x.

[snes-addict]

@ ai-danno: yes, I do have a 192.168.0.1, that would be my modem.

I think I might understand what you are saying. Would this mean that I have to add 192.168.0.1 into /etc/hosts, or do I need the router's IP address?

[phoenix]

Two options: either remove the first nameserver line in /etc/resolv.conf, or edit that line to read 192.168.1.1.

You'll also want to remove the two lines with 192.168.0.x entries from /etc/hosts. They aren't correct, or needed.

[snes-addict]

I got it working again! Cool, thank you very much, phoenix and ai-danno!

I think it was all in /etc/resolv.conf. The file now reads:

search domain.actdsltmp
nameserver 205.171.3.26
nameserver 192.168.1.1
lookup file bind

And /etc/resolv.conf.tail is:

nameserver 192.168.1.1
lookup file bind

Now I only have to figure out how to make my edit to /etc/resolv.conf permanent. I know that, according to the OpenBSD FAQ, /etc/dhclient.conf has something to do with this, but how would I ensure that the old line "nameserver 192.168.0.1" is not re-added on bootup?

[phoenix]

Fix the DHCP server. Most likely it's your router. Just go through the configs on there and put in the correct DNS server entries.

[snes-addict]

Originally Posted by phoenix

Fix the DHCP server. Most likely it's your router. Just go through the configs on there and put in the correct DNS server entries.

Got it.
dhclient vr0 updates /etc/resolv.conf with correct info now. Thanks!