Re: Setting IP address not working

[Kent West <westk@acu.edu>]

Alan Chandler wrote:

>On Wednesday 15 June 2005 16:31, Kent West wrote:
>  
>
>>Whoa! So your network is working?
>>    
>>
>Yes but with the wrong ip address
>  
>
>>What's the output of "ifconfig"?
>>    
>>
>eth0      Link encap:Ethernet  HWaddr 00:50:DA:CF:A5:06
>          inet addr:169.254.50.3  Bcast:0.0.0.0  Mask:255.255.0.0
>          inet6 addr: fe80::250:daff:fecf:a506/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:89616 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:58120 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:108856836 (103.8 MiB)  TX bytes:4467081 (4.2 MiB)
>          Interrupt:5 Base address:0xd400
>
>  
>
>>What's the output of "lspci -v"?
>>    
>>
>0000:00:0f.0 Ethernet controller: 3Com Corporation 3cSOHO100-TX Hurricane (rev 
>30)
>  
>
>>What's the output of "/etc/init.d/networking restart"?
>>    
>>
>sit0: unknown hardware address type 776
>sit0: unknown hardware address type 776
>Listening on LPF/eth0/00:50:da:cf:a5:06
>Sending on   LPF/eth0/00:50:da:cf:a5:06
>Sending on   Socket/fallback/fallback-net
>DHCPREQUEST on eth0 to 255.255.255.255 port 67
>DHCPACK from 192.168.0.20
>SIOCSIFADDR: File exists
>bound to 192.168.0.21 -- renewal in 10800 seconds.
>RTNETLINK answers: Cannot assign requested address
>done.
>
>Note the ifconfig output above is relevent also to after this last command - 
>where you can see the dhcpd server is trying to give me 192.168.0.21 (which 
>is what I want it to be).
>  
>
I found this at:
http://www.ussg.iu.edu/hypermail/linux/kernel/9611.1/0330.html

> sit stands for "simple internet transition" and is bassically a device
> capable of encapsulating ipv6 in ipv4 datagrams.


So apparently the sit0 is a "device" for IPv6, which you're probably not
using. Perhaps removing any ipv6-related modules might help eradicate
this error message.

But that might not affect the real issue.

I think the next thing I'd try is:
  /etc/init.d/networking stop

followed by editing the interfaces file to a static IP so it looks like:

# The loopback network interface
>auto lo
>iface lo inet loopback
>
># The primary network interface
>auto eth0
>iface eth0 inet static
>    address 192.168.0.21
>    netmask 255.255.0.0  (or 255.255.255.0, or whatever it's supposed to be on your network)

and then
  /etc/init.d/networking start

and report the output.


-- 
Kent West
Technology Support
/A/bilene /C/hristian /U/niversity