![]() |
|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
![]() |
|
Thread Tools | Display Modes |
|
||||
![]()
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. |
|
||||
![]()
I'm using DHCP.
Code:
puffin:ken {27} cat /etc/resolv.conf search domain.actdsltmp nameserver 192.168.0.1 nameserver 205.171.3.26 lookup file bind Code:
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 Code:
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 |
|
||||
![]()
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.
__________________
Network Firefighter |
|
||||
![]()
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: Code:
search domain.actdsltmp nameserver 205.171.3.26 nameserver 192.168.1.1 lookup file bind Code:
nameserver 192.168.1.1 lookup file bind |
![]() |
Tags |
internet, networking |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Openbsd 4.5 network connection timeout | andrewm | OpenBSD General | 4 | 11th September 2009 02:32 AM |
hard disk: avail 0 capacity 100% is it fine to use it like this? | gosha | General Hardware | 13 | 17th June 2009 03:53 PM |
.wav file playing very fast on unix, fine on win | gosha | General software and network | 16 | 2nd June 2009 02:37 PM |
Wireless Network Loses Connection | JMJ_coder | NetBSD General | 5 | 17th February 2009 09:14 PM |
Numeric keypad don't works on X | aleunix | OpenBSD Installation and Upgrading | 3 | 15th June 2008 11:59 AM |