You are not logged in.
Pages: 1
I set up rc.conf under network to give wlan0 static ip as follows:
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="wlan0 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.100.255"
INTERFACES=(wlan0 eth0)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
but ifconfig -a returns an output that shows my wireless card has not the ip i assigned to in rc.conf.
wlan0 Link encap:Ethernet HWaddr 00:22:5F:A8:AA:F8
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::222:5fff:fea8:aaf8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:442027 errors:0 dropped:0 overruns:0 frame:0
TX packets:281916 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:656933941 (626.5 Mb) TX bytes:25026451 (23.8 Mb)
I installed network-manager gnome applet which show wlan0 set to DHCP, maybe it override rc.conf??
Offline
I installed network-manager gnome applet which show wlan0 set to DHCP, maybe it override rc.conf??
Yep... Remove "network" from rc.conf DAEMONS= line and use only network-manager... OR... remove network-manager and write "network" on that line if you only use 1 connection (saves RAM).
Wiki might help you...
Last edited by TigTex (2010-11-01 23:27:23)
.::. TigTex @ Portugal .::.
Offline
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
These lines are the problem.
Offline
Also, make sure that the IP in /etc/resolv.conf is set to your router. It's explained in the wiki, but I managed to overlook that when I first tried to set a static IP for a new Arch install.
Offline
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255" eth0="dhcp"
These lines are the problem.
No they're not. The OP is asking about the wlan0 interface, not eth0.
Offline
I installed network-manager gnome applet which show wlan0 set to DHCP, maybe it override rc.conf??
Indeed. Your gnome-panel-applets are processed long after the rc.conf.
I'd suggest using wicd anyway. This way you have an easy to configure network AND network access without booting into a DE.
Offline
I want a tool that automatizes commands to make wlan0 up at startup. Wicd can do that as gnome applet network-manager does?
Or..to solve my problem..i can just mantain network manager and set it up with the same settings in rc.conf
Last edited by jacopastorius82 (2010-11-02 17:17:51)
Offline
Also, make sure that the IP in /etc/resolv.conf is set to your router. It's explained in the wiki, but I managed to overlook that when I first tried to set a static IP for a new Arch install.
i set /etc/resolv.conf with opendns dns, which are the same i set in my router..this shouldn't be a problem
Offline
I want a tool that automatizes commands to make wlan0 up at startup. Wicd can do that as gnome applet network-manager does?
Or..to solve my problem..i can just mantain network manager and set it up with the same settings in rc.conf
It can do that. In fact, it does a better job. wicd runs as a daemon, so you'll have your wlan0 without booting into gnome. That means you'd be able to ssh into your box even if the X server is down.
Offline
Pages: 1