Ubuntu 11.04 not responding to PING from uboot 1.3.2

embeduser · 08-01-2011, 05:28 AM

Hi

I am facing a very strange problem. I have ubuntu 11.04 installed on my Laptop which acts as my host. To my Host I connect Mini2440 SBC which has uboot 1.3.2 on it.
The eth0 on my Host has 10.0.0.4 as ipaddress, and the mini2440 has 10.0.0.111 as its IP address.
When I try to Ping from mini2440 to my host, I see ARP requests being received on my host (monitoring eth0), but I dont see any ARP replies being sent.
When I try to do a TFTP from mini2440 to my host, I see ARP requests being received and ARP replies being sent back from host, but mini2440 doesnt receive them.
My host and mini2440 are connected directly to each other through a cross cable.
I have disabled UFW, SeLinux and avahi-daemon on my Ubuntu Host.

Now When I try to ping from mini2440 to some other system like a windows machine or a crunchbang system, then the connecttion between them is established.
Also, similarly, my Ubuntu Host is able to ping and talk to other windows or crunchbang system.

I think it is a configuration issue on my Ubuntu host. Please help.

Thanks

camorri · 08-01-2011, 06:16 AM

Have you set a default route for each system to the other?

embeduser · 08-02-2011, 09:24 AM

Hi Camorri

Yes following is the output of route command. and then the output for arp on my Ubuntu host.

Code:

$sudo route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0


$sudo arp -a
? (192.168.1.1) at 00:08:5c:7b:a4:a0 [ether] on wlan0
? (10.0.0.111) at 08:08:11:18:12:27 [ether] on eth0

Following are the settings on Uboot on mini2440

Code:

MINI2440 # printenv
bootargs=root=/dev/mtdblock3 rootfstype=jffs2 console=ttySAC0,115200
bootcmd=
bootdelay=3
baudrate=115200
ethaddr=08:08:11:18:12:27
ipaddr=10.0.0.111
serverip=10.0.0.4
netmask=255.255.255.0
usbtty=cdc_acm
mtdparts=mtdparts=mini2440-nand:256k@0(u-boot),128k(env),5m(kernel),-(root)
mini2440=mini2440=0tb
bootargs_base=console=ttySAC0,115200 noinitrd
bootargs_init=init=/sbin/init
root_nand=root=/dev/mtdblock3 rootfstype=jffs2
root_mmc=root=/dev/mmcblk0p2 rootdelay=2
root_nfs=/mnt/nfs
set_root_nfs=setenv root_nfs root=/dev/nfs rw nfsroot=${serverip}:${root_nfs}
ifconfig_static=run setenv ifconfig ip=${ipaddr}:${serverip}::${netmask}:mini2440:eth0
ifconfig_dhcp=run setenv ifconfig ip=dhcp
ifconfig=ip=dhcp
set_bootargs_mmc=setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_mmc}
set_bootargs_nand=setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_nand}
set_bootargs_nfs=run set_root_nfs; setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_nfs} ${ifconfig}
mtdids=nand0=mini2440-nand
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
gateway=10.0.0.4

Thanks

camorri · 08-02-2011, 10:25 AM

The only gateway showing on the Ubuntu system is 192.168.1.1. The gateway here needs to point to the mini, 10.0.0.111.

You may have to create different configs, and use the config for your use at any given time. I'm guessing 192.168.1.1 is your wireless router.

Are you using the Network Manager applet that comes on Ubuntu? I have had a lot of problems with it. I removed it, and installed wicd. Its in the repos. I have found it to be much easier to manage, change settings etc.

You can create different configs for eth0 and wlan0, and then select which one you want active.

embeduser · 08-03-2011, 10:34 PM

Hi Camorri

Yes 192.168.1.1 is my wireless router gateway.
I tried to remove network manager and thrn tried to install wicd.

Code:

sudo apt-get remove network-manager
sudo apt-get install wicd.

But After this I was not able to connect to Internet as my wlan0 interface was failing. I tried to kill wpa_supplicant but that
also didnt help much.

Also I configured my eth0 statically through wicd tool, but still it failed to come up.
I have now installed crunchbang on one of my partitions, but it also comes with network manager tool. So could you tell me the right way to do install wicd.
Also I tried the following command to add a new route

Code:

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0

$ route add host 10.0.0.111 netmask 255.255.255.0 gw 10.0.0.4 dev eth0
host: unknown host

Thanks

camorri · 08-04-2011, 06:39 AM

When I removed network-manager and installed wicd, I used Synaptic package manager, not command line. I suspect there is some package that is still there. I had a look at my Ubuntu system. I marked network-manager for install, it want to install three packages. They are 1. network-manager-gnome 2. network-manager-pptp 3. network-manager-pptp-gnome. Have a look with Synaptic package manager to see if any of these are still installed.

Quote:

Also I configured my eth0 statically through wicd tool, but still it failed to come up.

How did you try to bring it up? 'sudo ifconfig eth0 up' is the command. If the interface doesn't come up with that command, we need to look into the driver you have ( or do not have ) loaded. It may be on of the above packages is still there causing problems also.

embeduser · 08-04-2011, 02:13 PM

Hi Cliff,

I removed all the packages related to network-namager through synaptic package manager and re-installed wicd.
I am able to see my default wireless connection but I am not able to connect to my wireless connection. I could connect it to earlier using NM. when I do a iwlist scan following output i get

Code:

sudo iwlist scan

lo      Interface doesn't support scanning

eth0    Interface doesn't support scanning

wlan0   Scan Completed:
        Cell 01 - Address : 00:08:5C:7B:A4:A1
        Channel:11
        Frequency:2.46 GHz (Channel 11)
        Quality=29/70 Signal level=-81 dBm
        Encryption key:on

when i do a iwlist scan

Code:

wlan0    IEEE 802.11bgn ESSID:off/any
         Mode:Managed  Frequency:2.462 Ghz Access Point: Not-Associated
         Tx-Power=14 dBm
         Retry Long limit:7 RTS thr:off Fragment thr:off
         Power Management:off

Also When I reconnect the wireless connection I monitor /var/log/syslog messages and see that there is a error for

Code:

avahi-daemon: Registering new address record for 169.254.11.25 on wlan0.IPv4
avahi-autopid(wlan0)[3399]: SIOCSIFFLAGS failed: Permission denied
avahi-autopid(wlan0)[3399]: Callout STOP, address 169.254.11.25 on wlan0
Kernel: [ 1214.310174] ADDRCONF(NETDEV_UP): WLAN: link is not ready

Thanks.

camorri · 08-04-2011, 04:35 PM

There is one network visible

Quote:

Cell 01 - Address : 00:08:5C:7B:A4:A1

Is this your access point?

From the errors in syslog, it looks like you have a permission problem.

Quote:

avahi-autopid(wlan0)[3399]: SIOCSIFFLAGS failed: Permission denied

Did you boot the system after you installed wicd? Have you configured wlan0 in wicd?

You should be able to see any wireless access points on the Network tab on WICD.

Are you using Ndiswrapper and a windoze driver, or are you using a linux driver for wlan0?

embeduser · 08-05-2011, 10:21 AM

Hi Cliff

Quote:

Is this your access point?

Yes this is access point. I did a reboot after installing WICD and have restarted quite a few times. I am not sure of the permissions because i ran wicd client as a root only.
I am not sure which Wireless driver I am using, but the output of lspci gave

Code:

01.00.0 Ethernet Controller: Aheros Communications AR8152 v2.0 Fast Ethernet (rev c1)
07.00.0 Network Controller: Aheros Communications Inc. AR9285 Wireless Network Adapter(PCI-Express)(rev 01)

on doing a

Code:

lsmod | grep ath
ath9k         103633 0
mac80211      257001 ath9k
ath9k_common  13611  ath9k
ath9k_hw      300328 ath9k,athk_common
ath           19141  ath9k,athk_hw
cfg80211      156212 ath9k,mac80211,ath

I could connect to my wireless router before installing wicd through Network Manager. So could it be a problem of driver ?

Thanks.

camorri · 08-05-2011, 12:19 PM

The driver is ath9k, that happens to be the same driver I use on my netbook. Antheros chip sets are good. You should do not need Ndiswarpper.

I'm going to do a little googling to see if I can get some idea why you are getting the permission errors.

camorri · 08-05-2011, 12:31 PM

Well, you learn something new each day. Here is what avahi-autopid is for...

Quote:

Description
avahi-autoipd implements IPv4LL, "Dynamic Configuration of IPv4 Link-Local Addresses" (IETF RFC3927), a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server. It is primarily intended to be used in ad-hoc networks which lack a DHCP server.

Since you are trying to set up an ad-hoc connection, it appears avahi-autopid is trying to assign an IP address; based on this error:

Quote:

avahi-autopid(wlan0)[3399]: SIOCSIFFLAGS failed: Permission denied

What you might try is to assign static IP addresses. That should eliminate the need for this daemon.

Not sure just what file(s) this daemon wants to write to, but I suspect what ever file(s) it is, permission is being denied.

Here is a link that tells up more about avahi...

-->http://avahi.org/wiki/AvahiAutoipd

If you want to test your connection, without the avahi-daemon running, in a konsole you can stop the daemon with the command 'sudo service avahi-daemon stop'. I also have read a lot of threads suggesting if you don't use avahi-daemon, you can simply un-install it with Synaptic package manager. I did that on my netbook and all is well. You can always re-install it, if you need it in the future.

embeduser · 08-12-2011, 10:15 AM

Hi
Yeah static IP worked for me. Was able to get wlan0 up and running. But then you have to give correct IP and DNS settings.
Also my Initial problem of Ubuntu on my laptop not able to Ping mini2440 with uboot got resolved.
I couldnt find the correct reason, but when I connected a L2 switch between my laptop and mini2440 it was able to do so.
The possible reason could be that Uboot initiates the ethernet link only when required, i.e when it sends a ARP message and then downs the link. It seems the current Atheors 8152 Driver for eth0 doesn't reply back if the link is down. So it never relies back to ARP. On connecting a L2 switch, the switch keeps the link layer up and then on receiving an ARP request for itself the Kernel replies.

Hope this makes sense and helps others.

Thanks.

camorri · 08-12-2011, 02:47 PM

Glad you got it working.