You are not logged in.
I setup a linksys router, and it doesn't work properly with arch. I can connect to it, but there's no internet.
Other computers on the router can get internet, and windows vista on the same computer as arch can.
There is another router upstream from this one.
The new router uses a static IP, and arch uses DHCP.
Last edited by Raccoon1400 (2009-04-13 22:07:31)
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline
Hello.
Please post your rc.conf and resolv.conf or any other involved config file.
Can you ping your router? Can you ping any URL, e.g. www.google.com ? Can you ping the IP adress of this URL? If you can ping the IP but not the URL then you may have a DNS problem. To find the IP of a URL you can use http://www.dnswatch.info/de.
Last edited by hauntergeist (2009-04-11 11:44:18)
Offline
I can't ping any of the IP addresses for Google.
I can ping the router.
I can' ping a URL.
duncan@duncan-arch ~]$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="localtime"
USEDIRECTISA="yes"
TIMEZONE="Canada/Eastern"
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=(bcm43xx b43 ssb) #deprecated
MODULES=(mii ndiswrapper b44 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel acpi-cpufreq cpufreq_ondemand cpufreq_powersave soundcore vboxdrv usblp fuse iwl3945)
# 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="duncan-arch"
# 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
#
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(eth0 wlan0)
# 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 dbus @cpufreq @hal alsa @dhcdbd @networkmanager @crond @cups)
duncan@duncan-arch ~]$
duncan@duncan-arch ~]$cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 67.69.235.1
nameserver 207.164.234.193
duncan@duncan-arch ~]$
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline
The new router uses a static IP, and arch uses DHCP.
Offline
Raccoon1400 wrote:The new router uses a static IP, and arch uses DHCP.
why does arch need a static IP?
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline
try to check your route tables if default gw is set properly
Offline
try to check your route tables if default gw is set properly
How?
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline
type route command and paste output
Offline
duncan@duncan-arch ~]$route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 1 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
duncan@duncan-arch ~]$
Last edited by Raccoon1400 (2009-04-11 15:59:31)
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline
192.168.1.1 is ip of router that is directly connected to internet or it is that second one?
Offline
@Raccoon1400
It looks like 192.168.1.1 is the first router, i.e. the one which is not directly connected to the internet?
Once I had a similiar problem: WLAN: can ping gateway but can't ping any website
My solution was: changed the router and everything went fine. So for me it was a hardware problem. Maybe you can try to swap the role of the routers and look if it works ...
But what makes me wondering about your config is that your dns server is not the router. I'd try to turn NetworkManager off and to set the internet connection up by hand, i.e.
- NetworkManager off
- turn every existing connection to your router down
- overwrite your resolv.conf with "nameserver 192.168.1.1"
- make "dhcpcd eth0"
Offline
If you can ping your router but not get out to the net, check your /etc/hosts file.
It should probably look similar to below.
#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost duncan-arch
# End of file
Offline
And I don't see how it could be a harware issue, since other computers can get internet through it, and other operating sytems on the same computer can.
And there's no way mom's letting me touch the other router.
duncan@duncan-arch ~]$cat /etc/hosts
#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 duncan-arch.localdomain duncan-arch
# End of file
duncan@duncan-arch ~]$
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline
Can you resolve external names at all via nslookup or dig ?
nslookup www.google.com
dig www.yahoo.com
What happens if you run a traceroute from the Arch box to the upstream router ? Or to something beyond that ?
traceroute IP.OF.UPSTREAM.ROUTER
traceroute www.google.com
Offline
I realized the IP address of both routers was the same, so I changed the subnet mask and IP on the new router, and it seems to be working, at least for now.
Fustrated Windows users have two options.
1. Resort to the throwing of computers out of windows.
2. Resort to the throwing of windows out of computers.
Offline