Netcfg static IP -- 'Adding gateway failed'

firecat53 · 2010-01-21 17:23:19

I can't find the "complete" example anymore in netword.d/profiles and I can't find the complete documentation for netcfg profiles, so here's my question:

This profile works great:

CONNECTION="wireless"
DESCRIPTION="Home"
INTERFACE="wlan0"
SECURITY="wpa"
ESSID="firecat4153"
KEY="wirelesskey"
IP="dhcp"

For a static IP with this profile:

CONNECTION="wireless"
DESCRIPTION="Home"
INTERFACE="wlan0"
SECURITY="wpa"
ESSID="firecat4153"
KEY="wirelesskey"
IP="static"
GATEWAY="192.168.0.1"
ADDR="192.168.0.100"
DNS=("208.67.222.222 208.67.220.220")

I get the following error:

:: firecat4153 up                                                                                                                    [BUSY]
 SIOCADDRT: No such process
 - Adding gateway failed.

I've also tried tried changing the DNS entries to:
DNS1="208.67.222.222"
DNS2="208.67.220.220"
but get the same result.

Netcfg v2.2.1 from core.

What am I missing?

Thanks!
Scott

doc.horn · 2010-01-22 13:10:46

same here.
using RaLink RT2561/RT61 rev B 802.11g with serialmonkey's ralink driver rt61pci,
dhcpcd always times out

firecat53 · 2010-01-22 13:27:10

Dhcpcd works fine for me (the first profile w/ ip="dhcp"). It's the static ip setup that fails. I've got a Belkin F5D9050 (rt73usb driver w/ rtx200 firmware).

Scott

noclue · 2010-02-08 09:53:40

I'm having the same problem as firecat. DHCP works fine in my profile, but fails when trying to use a static IP.

wrc1944 · 2010-02-08 11:04:27

I'm no expert, but In all my cases trying to setup static wireless, I had to make sure the "gateway" address I used in whatever network software (wicd, a config file, NetworkManager, etc.) was the same as the wireless router's actual address I was trying to use. Somtimes I had problems with reboots over-writing my /etc/resolv.conf file with the wrong gateway address (when using a 2nd bridged router system), and had to edit in the correct address every time, until I discovered that in the /etc/conf.d/dhcpcd file I had to put in the line

 DHCPCD_ARGS="-q --nohook resolv.conf"

I'm not saying in your case you need to do this, but it's worth looking at if your resolv.conf file is getting overwritten with the wrong address.

Are you absolutely sure that GATEWAY="192.168.0.1" is the correct address of you router? You could check by typing http://192.168.0.1 in a browser whiuch should open your router's setup page if it's really the correct address. Your router's documentation should tell you what the address is, so that you can access the setup page.

What's the output of route in a terminal say when you are successfully connected with dhcp?

Last edited by wrc1944 (2010-02-08 19:21:43)

pepeapepepe · 2010-02-09 01:26:24

maybe the lack of the file is due to changes coming in netcfg 2.5

Last edited by pepeapepepe (2010-02-09 01:30:14)

sdolim · 2010-02-09 03:00:47

I found what may be a helpful tip on this thread:
http://bbs.archlinux.org/viewtopic.php?pid=289404

The problem is that at the time the default gateway is being set up, there's no route for it, so it is considered unreachable. (The error message is obscure, but that is apparently what it means.)

Here's what the solution from the other thread was:

g0="80.48.71.175 eth0"
gateway="default gw 80.48.71.175"
ROUTES=(g0 gateway)

(You need to put in your correct gateway address instead, obviously.)

Arch Linux

#1 2010-01-21 17:23:19

Netcfg static IP -- 'Adding gateway failed'

#2 2010-01-22 13:10:46

Re: Netcfg static IP -- 'Adding gateway failed'

#3 2010-01-22 13:27:10

Re: Netcfg static IP -- 'Adding gateway failed'

#4 2010-02-08 09:53:40

Re: Netcfg static IP -- 'Adding gateway failed'

#5 2010-02-08 11:04:27

Re: Netcfg static IP -- 'Adding gateway failed'

#6 2010-02-09 01:26:24

Re: Netcfg static IP -- 'Adding gateway failed'

#7 2010-02-09 03:00:47

Re: Netcfg static IP -- 'Adding gateway failed'

Board footer