Static IP and Pacman [SOLVED]

slightlystoopid · 2010-01-22 12:49:32

Pacman runs fine as long as my network is configured to use dhcp. Also, it appears to function with a static ip as long as I uncomment "XferCommand = /usr/bin/curl %u > %o". Running it normally though, I get "No address record" errors, or with the wget XferCommand uncommented, I get "Name or service not known" errors. What am I doing wrong?

EDIT: I would provide more info, but I'm not sure what's relevant. All other network services, including bittorrent, are working.

Last edited by slightlystoopid (2010-01-22 16:39:10)

eldragon · 2010-01-22 13:14:53

how did you setup your static ip?

the outputs of ifconfig and route should be useful

so are the contents of /etc/resolv.conf

Last edited by eldragon (2010-01-22 13:15:13)

slightlystoopid · 2010-01-22 13:23:53

I set it through rc.conf, hosts, and resolv.conf.

EDIT: Also, I have restarted. Whenever I switch from dhcp to static, or vice versa, I have to restart. A simple "sudo /etc/rc.d/network restart" doesn't work (although, it doesn't say fail, I just can't ping my router without a restart (and now that I think about it, I wonder if a quick unplug from the router would work)).

ifconfig and route

[~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:09:12:80:18  
          inet addr:192.168.1.200  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:33988 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27695 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:37009847 (35.2 Mb)  TX bytes:5221893 (4.9 Mb)
          Interrupt:20 Base address:0x4000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:125 errors:0 dropped:0 overruns:0 frame:0
          TX packets:125 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:17202 (16.7 Kb)  TX bytes:17202 (16.7 Kb)

[~]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

resolv.conf

# /etc/resolv.conf.head can replace this line
nameserver 192.168.1.1
nameserver 192.168.2.1
nameserver 76.5.159.133
nameserver 63.162.197.99
# /etc/resolv.conf.tail can replace this line

rc.conf - Networking

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="ubermensch"

# 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="dhcp"
eth0="eth0 192.168.1.200 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(eth0)

# 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.1.1"
#ROUTES=(!gateway)
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)

hosts

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1    localhost.localdomain    localhost    ubermensch
192.168.1.200    ubermensch

# End of file

Last edited by slightlystoopid (2010-01-22 13:32:56)

eldragon · 2010-01-22 14:17:36

everything looks ok, how about pacman.conf?

slightlystoopid · 2010-01-22 14:42:33

pacman.conf

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
HoldPkg     = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst   = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl %u > %o
#CleanMethod = KeepInstalled

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg   = pulseaudio
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options (all disabled by default)
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[xyne-any]
# The home of Powerpill and Xyne's other contributions.
# More info including a package list can be found at http://xyne.archlinux.ca/repositories
Server = http://xyne.archlinux.ca/repos/any/

#[testing]
## Add your preferred servers here, they will be used first
#Include = /etc/pacman.d/mirrorlist

[core]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist

[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist

#[community-testing]
## Add your preferred servers here, they will be used first
#Include = /etc/pacman.d/mirrorlist

[community]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs

mirrorlist

# 2010-01-22 09:01 
# generated by reflector
# ranked by rankmirrors
Server = ftp://archlinux.puzzle.ch/$repo/os/x86_64
Server = ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/archlinux/$repo/os/x86_64
Server = ftp://mirror.archlinux.fi/archlinux/$repo/os/x86_64
Server = ftp://cesium.di.uminho.pt/pub/archlinux/$repo/os/x86_64
Server = ftp://archlinux.nautile.nc/archlinux/$repo/os/x86_64

eldragon · 2010-01-22 14:44:09

im out of ideas...anyone?

slightlystoopid · 2010-01-22 15:12:28

I just found that abs returns this:

[~]$ sudo abs
==> Starting ABS sync...
rsync: getaddrinfo: rsync.archlinux.org 873: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.7]

slightlystoopid · 2010-01-22 16:38:31

fuuuu, nameservers were out of order in resolv.conf.

this work:

nameserver 76.5.159.133
nameserver 63.162.197.99
nameserver 192.168.2.1
nameserver 192.168.1.1

I guess a general rule for resolv.conf is something like "farthest nameserver first" in the router line.

I'm still not really sure why only pacman and abs seemed affected while everything else, all messenger protocols, bittorrent, etc. still worked.

Last edited by slightlystoopid (2010-01-22 16:41:45)

Arch Linux

#1 2010-01-22 12:49:32

Static IP and Pacman [SOLVED]

#2 2010-01-22 13:14:53

Re: Static IP and Pacman [SOLVED]

#3 2010-01-22 13:23:53

Re: Static IP and Pacman [SOLVED]

#4 2010-01-22 14:17:36

Re: Static IP and Pacman [SOLVED]

#5 2010-01-22 14:42:33

Re: Static IP and Pacman [SOLVED]

#6 2010-01-22 14:44:09

Re: Static IP and Pacman [SOLVED]

#7 2010-01-22 15:12:28

Re: Static IP and Pacman [SOLVED]

#8 2010-01-22 16:38:31

Re: Static IP and Pacman [SOLVED]

Board footer