You are not logged in.
Hi,
After installing Arch, I was able to upgrade all packages with pacman fine, as well as get Xorg and Xfce working fine. When I logged in and fired up firefox, i got an "Address not found" problem. I installed epiphany, and it doesn't work there either, though links does, for some reason. I don't know what configuration files or infromation you need to know (sorry ), but I can give you whatever you need to help solve this problem.
All help on this is greatly appreciated
-jhl
Calm down, it is only ones and zeroes.
-flyingfsck ( on /. )
Offline
sysctl net.ipv4.tcp_window_scaling=0
issue that command as root and recheck if firefox can access the web.
Cheers
They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.
Offline
I don't know what configuration files or infromation you need to know
What is the output of the following commands:
ifconfig
route -n
cat /etc/resolv.conf
Last edited by fukawi2 (2009-06-03 22:38:00)
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Hi guys,
I recently came back to a box with Arch installed. It worked fine until I ran
pacman -Syu
After I reboot I could still access pacman and use links to get webpages, but any other browser turns up a "can't connect" error like the OP's post.
I reinstalled Arch with the latest x86_64 isolinux iso, and the problem persisted. I also tried the first suggestion, it changed it to 0 but again the problem persisted.
So here's the input that you requested:
[sharpie@machinelinux ~]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 204 0 0 eth2
0.0.0.0 192.168.0.1 0.0.0.0 UG 204 0 0 eth2
[sharpie@machinelinux ~]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:14:C1:xx:xx:xx
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0x8000
eth1 Link encap:Ethernet HWaddr 00:14:C1:xx:xx:xx
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0x8000
eth2 Link encap:Ethernet HWaddr 00:1B:B9:xx:xx:xx
inet addr:192.168.0.65 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::21b:b9ff:fef9:7d2e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:134441 errors:0 dropped:0 overruns:0 frame:0
TX packets:87953 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192205005 (183.3 Mb) TX bytes:6527205 (6.2 Mb)
Interrupt:27 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
[sharpie@machine ~]$ cat /etc/resolv.conf
# Generated by dhcpcd from eth2
# /etc/resolv.conf.head can replace this line
nameserver 192.168.0.1
# /etc/resolv.conf.tail can replace this line
Also, my rc.conf file:
[sharpie@machine ~]$ cat /etc/rc.conf
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="America/Phoenix"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="machine"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth2="dhcp"
INTERFACES=(eth2)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond alsa hal fam gdm)
Thanks for all input on this guys. I'm currently reading man route to see if the answer's there.
Last edited by sharpie (2009-06-18 20:01:00)
Offline
Sharpie, if you open your browser and in the url bar put
66.102.9.104
does google.com apear?
It looks like you have no DNS lookup ( unless 192.168.0.1 is a DNS )
If entering the I.P. 66.102.9.104 works, maybe you should have a look at getting opendns setup.
Hope it helps, I'm just a newb to arch as well.
This Is My Truth, Tell Me Yours
Offline
I forgot to mention that. I can access any webpage by IP address. I'm going to read about openDNS.
It doesn't explain why I can use Links and still can implement pacman.
Last edited by sharpie (2009-06-12 22:35:19)
Offline
sharpie,
for a quick fix, insert a line in /etc/resolv.conf:
nameserver 208.67.222.222
nameserver 192.168.0.1
208.67.222.222 is one of the openDNS domain name servers.
Having said that, I suppose your 192.168.0.1 is your local router. If thats the case, most routers are able to act like DNS relays.
Check its configuration.
Or use a DNS server from your ISP. Their help pages should mention it.
EDIT: the links and pacman mistery remains. Perhaps there is more to it...
Mektub
Last edited by Mektub (2009-06-12 23:11:16)
Follow me on twitter: https://twitter.com/johnbina
Offline
DNS is setup 'correctly' on your end (ie, 192.168.0.1) is valid syntax, but it appears your modem/router isn't acting as a DNS server correctly. Perhaps it is configured to use DNs server that don't exist or deny you access?
FTR, everything else looks valid.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Hey guys,
Added this to /etc/resolv.conf:
nameserver 208.67.222.222
It works! I'm writing from the Arch install! But I'd still like to know what causes this. Can any of you point me in the direction of some good resources regarding the process involved with configuring the network connection and assigning nameservers?
It's particularly odd because the computer when running WinXp, works just fine.
Also, I am not OP so I can't mark as SOLVED.
Last edited by sharpie (2009-06-13 00:39:58)
Offline
But I'd still like to know what causes this.
For whatever reason, your modem/router refused to act as a DNS server for you, but it's happy to pass it through to the OpenDNS when you use them directly.
It's particularly odd because the computer when running WinXp, works just fine.
Boot WinXP and Start -> Run -> cmd then examine the output of 'ipconfig /all' for the "DNS Servers" directive. Is that set to 192.168.0.1? If it is and it works, then I'm buggered if I know why your router will serve DNS to Windows but not Linux. What Make/Model is it? Try installing 'dnsutils' and running `dig google.com @192.168.0.1` and post the output.
Also, I am not OP so I can't mark as SOLVED.
Technically, we still don't know if the OP's post is solved
Last edited by fukawi2 (2009-06-13 01:49:47)
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
[sharpie@machine ~]$ dig google.com@192.168.0.1
; <<>> DiG 9.6.0-P1 <<>> google.com@192.168.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9383
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com\@192.168.0.1. IN A
;; Query time: 35 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Jun 18 05:55:24 2009
;; MSG SIZE rcvd: 40
Every time that I reboot the machine, I have to re-add the nameserver. This worked just fine about 2 months ago, could it have anything to do with my having 3 ethernet cards?
eth0 Link encap:Ethernet HWaddr 00:14:C1:xx:xx:xx
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xa000
eth1 Link encap:Ethernet HWaddr 00:14:C1:xx:xx:xx
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0x8000
eth2 Link encap:Ethernet HWaddr 00:1B:B9:xx:xx:xx
inet addr:192.168.0.65 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::21b:b9ff:fef9:7d2e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:648 errors:0 dropped:0 overruns:0 frame:0
TX packets:423 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:230504 (225.1 Kb) TX bytes:73958 (72.2 Kb)
Interrupt:27 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
Is it normal to get 0.0.0.0 addresses in the routing table?
[sharpie@machine ~]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 204 0 0 eth2
0.0.0.0 192.168.0.1 0.0.0.0 UG 204 0 0 eth2
Offline
Every time that I reboot the machine, I have to re-add the nameserver. This worked just fine about 2 months ago, could it have anything to do with my having 3 ethernet cards?
Are you using DHCP? The DHCP lease will be over-writing your changes each time it gets a new lease. You can over-ride this behaviour in the DHCP client config. You'll have to search the forum/wiki/google for how to do it, I can't remember off the top of my head.
Is it normal to get 0.0.0.0 addresses in the routing table?
Yes. What you posted is perfectly valid.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Works just fine in WindowsXP. If I delete the /etc/resolv.conf file, the same problem happens. What else is effected by how I access nameservers?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\sharpie>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : machine
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : U.S. Robotics 10/100/1000 PCI NIC
Physical Address. . . . . . . . . : 00-14-C1-xx-xx-xx
Ethernet adapter Local Area Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : U.S. Robotics 10/100/1000 PCI NIC #2
Physical Address. . . . . . . . . : 00-14-C1-xx-xx-xx
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168/8111 PCI-E Gigabit E
thernet NIC
Physical Address. . . . . . . . . : 00-1B-B9-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, June 18, 2009 6:32:08 PM
Lease Expires . . . . . . . . . . : Friday, June 19, 2009 6:32:08 PM
C:\Documents and Settings\sharpie>
And yes, I use dhcpcd to configure my DHCP.
Last edited by sharpie (2009-06-19 02:31:13)
Offline
Works just fine in WindowsXP. If I delete the /etc/resolv.conf file, the same problem happens. What else is effected by how I access nameservers?
If you delete /etc/resolv.conf, your computer has no way of looking up IP addresses; don't do that.
One solution would be to change your /etc/conf.d/dhcpcd to this:
DHCPCD_ARGS="-q -C resolv.conf"
This stops dhcpcd to change your resolve.conf on each boot.
About the original problem: I have a suspicion that your modem/inbuilt DNS can't handle IPv6 requests (I know mine doesn't). Maybe that's causing it to just drop your requests. Try this:
sudo sysctl net.ipv6.conf.all.disable_ipv6=1
Offline