(Solved)--Static Address problem

b0uncyfr0 · 2010-03-09 05:08:00

I set my static address according to the wiki an deverything bu it still refuses to work. I have to use dhcpcd eth0 everytime i boo to make my connection work. Here are a few files:

rc.conf
eth0="eth0 192.168.1.10 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)

/etc/hosts
<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost tux
192.168.1.10 tux.domain.org tux

Anything wrong from this?

Last edited by b0uncyfr0 (2010-03-10 07:52:51)

CountDuckula · 2010-03-09 05:31:16

Can you ping your default gateway at 192.168.1.1 ?

If so, you have probably forgot to add your DNS server entries in /etc/resolv.conf in order to resolve your domain lookups.

Last edited by CountDuckula (2010-03-09 05:41:08)

chakra-user · 2010-03-09 05:47:43

do u load network or networkmanager in daemons? I too was facing same problem when I installed Alpha 4. Try running

ifconfig eth0 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255
ifconfig eth0 up

and reboot. it should be up next time onwards. I got it working after this drill.

b0uncyfr0 · 2010-03-09 07:24:23

My daemon order is :

(hal network kdm alsa netfs samba syslog-ng crond g15daemon)

And i dont remember ever putting anything in /etc/resolv.conf. Was i supposed to?

tomk · 2010-03-09 07:29:32

chakra-user, ifconfig commands are not persistent across a reboot. That's what config files are for.

b0uncyfr0, "refuses to work" is vague. What doesn't work exactly? Paste your ifconfig and route output, and the contents of /etc/resolv.conf.

CountDuckula · 2010-03-09 07:38:28

b0uncyfr0 wrote:

My daemon order is :
(hal network kdm alsa netfs samba syslog-ng crond g15daemon)
And i dont remember ever putting anything in /etc/resolv.conf. Was i supposed to?

Yeah you need to put your ISP's (assuming you have no internal DNS server) DNS servers in that file. The wiki states,

Edit your /etc/resolv.conf like this, substituting your nameservers' IPs and your domain name:

nameserver 61.23.173.5
nameserver 61.95.849.8
search example.com

Without knowing who to contact for DNS resolution your machine will not find anything out on the net.

chakra-user · 2010-03-09 10:34:43

tomk wrote:

chakra-user, ifconfig commands are not persistent across a reboot. That's what config files are for.
b0uncyfr0, "refuses to work" is vague. What doesn't work exactly? Paste your ifconfig and route output, and the contents of /etc/resolv.conf.

Ahh well what I meant is that in addition to entries in /etc/rc.conf reg. static IP address and network in DAEMON Array, I did this ifconfig commands and had my eth0 up and running. I know it does not persist across reboots but somehow inspite of having the rc.conf stuff in, it did not wrk but when I ran the rc.conf + ifconfig it worked. Magic Mantra

inaddition, I saw two lines of eth0="dhcp" in default rc.conf, I had done that also just incase it helps one or all of it together made my eth0 come up. I have now removed duplicate eth0="xxx" entries, removed NetworkManager and kept network and everything works. It is sad that these things must be working in stock install of Arch/Chakra but users have to struggle for such simple things.

perbh · 2010-03-09 13:32:32

Just to add my 2c worth ...
When you use dhcp, the router will pick the appropriate dns from your isp, if you use static ip-addresses you are on your own (more or less)
What you can do is:
1) use one or more public dns (eg. google has one on 8.8.8.8 - search the web for public dns if you want more)
2) I presume that you can access the router (192.168.1.1) from a browser - if you look around you will probably find the dns of your isp there

b0uncyfr0 · 2010-03-10 07:52:31

Thanks a lot guys. I used the dns of my router. (192.168.1.1). Would i see a performance difference if i used the dns of my isp? I remember a year ago when i was constantly installing ARCH with static addresses, i never had to edit the reslv.conf file. Something must have changed.

Thnx again guys...long live Arch..

CountDuckula · 2010-03-10 08:05:58

b0uncyfr0 wrote:

Thanks a lot guys. I used the dns of my router. (192.168.1.1). Would i see a performance difference if i used the dns of my isp?

There would be no real difference to be honest, as your router is looking at your ISP's DNS servers i would imagine. Anyway glad its working for you now

perbh · 2010-03-10 16:11:18

eeek! silly me!
Of course you can use your router as a nameserver - it makes everything a bit simpler than having to dig around for your isp's nameserver.
Then - as CountDuckula says - if you use your router, it in turn will use the nameserver of your isp.

I believe that if you use dhcp, then /etc/resolv.conf gets overwritten and your router is used automagically.
If you want to make sure your router is _always_ one of your nameservers, put it in /etc/resolv.conf.header.
I guess these are the changes since you last used arch ...

Arch Linux

#1 2010-03-09 05:08:00

(Solved)--Static Address problem

#2 2010-03-09 05:31:16

Re: (Solved)--Static Address problem

#3 2010-03-09 05:47:43

Re: (Solved)--Static Address problem

#4 2010-03-09 07:24:23

Re: (Solved)--Static Address problem

#5 2010-03-09 07:29:32

Re: (Solved)--Static Address problem

#6 2010-03-09 07:38:28

Re: (Solved)--Static Address problem

#7 2010-03-09 10:34:43

Re: (Solved)--Static Address problem

#8 2010-03-09 13:32:32

Re: (Solved)--Static Address problem

#9 2010-03-10 07:52:31

Re: (Solved)--Static Address problem

#10 2010-03-10 08:05:58

Re: (Solved)--Static Address problem

#11 2010-03-10 16:11:18

Re: (Solved)--Static Address problem

Board footer