Arch Linux

tandycorp

Member

Registered: 2007-07-01

Posts: 65

WIMAX networking doesn't work in arch? [solved]

Hello I have an external wimax modem, this thing is the same size of a cable modem and is positionned in a window (inside) to get a good signal. This is really simple. I only need to connect this in the wall for power. Then, from that modem I have a cat5 cable that directly connects in the pc's network card (mine is integrated), and everything works with DHCP. I don't even need a username or pass, this is just like a local area network. It works in ubuntu, vector linux, gos at first boot.

But I always get this error in arch (at boot or when I type /etc/rc.d/network restart)

err, eth0: timed out
warn, eth0: using IPV4LL address 169.254.110.130

As you see, I got an IP.
Here's another proof I got an IP:

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:1D:7D:9E:CD:AD  
          inet addr:169.254.110.130  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2578 (2.5 Kb)  TX bytes:15204 (14.8 Kb)
          Interrupt:16 Base address:0xc000 

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

So since DHCP seems to work, I thought I had a problem with dns. But I can't ping anything

ping -c 3 206.102.35.42
Network is unreachable.

So I thought it had something with the nic. My motherboard is a gygabyte ga-p35-ds3L and the nic on it is a Realtek RTL8168/8111 PCI-E Gigabit Ethernet. I decided to use the Realtek driver instead of the one that comes with arch. It didn't change anything.

I tried also to put off an option integrated into the nic (from windows). There's a power management thing that could stop the nic for saving purpose, so I chose to be up all the time. Didn't change anything.

Does it have to do with the wimax principle? Not sure. This technology is simple and all managed by the modem. But I know it needs an authorization from the FAI to get good ips and internet access. I realised that: when windows connects on the internet at bootup, it first gets an IP like the one I got in arch, starting from 169.254.... then after few seconds of communication, it suddently changes to a completely different range : 76.67.51.1. And only from that time I can get access to the internet. So, is arch not able to receive the gateway address?

I read somewhere I could send my NIC mac address by doing :

 interface "eth0" {
   send dhcp-client-identifier 00-1D-7D-9E-CD-AD;
 }

But I don't know if it would change anything.

Please help!

Here's my 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="fr_CA.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Canada/Eastern"
KEYMAP="cf"
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=() #deprecated
MODULES=(r8168 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc 
snd-pcm snd-timer snd snd-hda-intel soundcore)

# 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="myhost"

# 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"
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.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 network netfs crond)

Last edited by tandycorp (2008-10-07 22:42:01)

tandycorp

Member

Registered: 2007-07-01

Posts: 65

Re: WIMAX networking doesn't work in arch? [solved]

Does someone see something wrong in my rc.conf?
Is the delay of 30 seconds too short for connection at bootup? Can I make that connection in the background?
Sorry I don't speak english everyday.

and oh, i don't have anything in /etc/hosts except the loopback line. Should I add something, like the host name?

Last edited by tandycorp (2008-09-28 23:44:47)

tandycorp

Member

Registered: 2007-07-01

Posts: 65

Re: WIMAX networking doesn't work in arch? [solved]

Please help. What should I do?

lucke

Member

From: Poland

Registered: 2004-11-30

Posts: 4,018

Re: WIMAX networking doesn't work in arch? [solved]

dhcpcd doesn't really work in your case. As for the cause, beats me. Make sure there's a "eth0: link up" message in dmesg.

tankmcp

Member

From: Tulsa, OK

Registered: 2007-09-17

Posts: 54

Re: WIMAX networking doesn't work in arch? [solved]

Just some speculation here as I'm not a network expert.

I don't think it has anything to do with WIMAX, only with communicating with the dhcp server of your device.
Your 169.254.x.x IP is not an IP given by a successful connection, but only a dummy given when the true connection fails. (someone please explain this more accurately )

Work thru the wiki setup page again. Note the dhcpd setup section and the note on your realtek card.
http://wiki.archlinux.org/index.php/Configuring_network
Try the Arch driver again for your card.

Or, switch to the netcfg2 setup, even though using an ethernet card, it works great for my setup with a realtek card.
It can be found http://wiki.archlinux.org/index.php/Network_Profiles here.

Hope it helps.

tandycorp

Member

Registered: 2007-07-01

Posts: 65

Re: WIMAX networking doesn't work in arch? [solved]

Ok thanks for your answers. Yeah you're right, after some search I realised that most 169.xx are given when nothing works. I'm a begginer in dhcp and network stuff.

Yeah wimax is not the problem here.
I'll try dhclient, an dhcpcd alternative. thanks a lot!

Last edited by tandycorp (2008-10-01 22:58:56)

tandycorp

Member

Registered: 2007-07-01

Posts: 65

Re: WIMAX networking doesn't work in arch? [solved]

Solved. I simply copied dhclient package from arch servers in windows then

killall dhcpcd
dhclient

dhclient seems better than dhcpcd in my case..
now i need to automate the operation

Last edited by tandycorp (2008-10-03 01:30:52)