[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(usagi-users 03903) Re: Binding Update Failure

Hi Romain,

The setup I was running for the previous test which I had sent the
logs from was all in one room.  I checked the radvd.conf and the time
intervals were both set very low.  So, I increased them each by a few

I tried a new setup today with the routers separated down the fall
from each other so that the wireless networks overlap just a bit.
Both wireless networks are on a separate ESSID (homenet and visitnet).
I had both of the networks on the same channel though.  Is it
necessary or preferred to have the routers on different channels?  How
does the MN receive router advertisements from the AR if it is
listening for its own router on a different channel?  In addition, the
routers are set to master (ap) mode and the HA and MN are in managed
mode.   Would it be better to put everything in ad-hoc?

When I gave this setup a try, it partially succeeded.  The MN did
successfully bind into the foreign network a couple times, but failed
considerably more.  The issue was that router advertisements from both
the HA and AR were being received in both wireless networks.  The MN
is receiving both of these from either the HA or the AR (depending on
which network it resides in at the time), and the MN is out of range
of which ever network it is not in.  Hence, the router advertisements
are being forwarded between the networks.  IPv6 forwarding
(/proc/sys/net/ipv6/conf/forwarding) is set to 1, but Accept RAs
(/proc/sys/net/ipv6/conf/accept_ra) is set to 0 on the HR, HA, and AR.
This is very confusing because I did not believe routers were suppose
to forward router advertisements.  I suppose it is possible just
because I am using normal nodes with a bridge as access points, as
opposed to true routers.  Is there another way to prevent router
advertisements from being forwarded?

Thanks for all the great help.  I really appreciate it.


On 7/19/07, Romain KUNTZ <kuntz@xxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Ryan,

On 2007/07/19, at 5:53, Ryan Measel wrote:
> I am still having issues with the mobile node not being able to bind
> to the home agent.  It knows that it moves into a foreign network, but
> it then throws an error that "blackhole is already set."  And, no

Do not pay attention to this message, this is juste a debug message
that ii IMHO not the cause of your problem.

> binding update will be sent.  I have posted the debug from the mobile
> node and the config file for the mobile node below.

Ok, see my comment inline below.

> Also, how does everyone else setup their testbed, i.e., what type of
> hardware do use for routers and the home agent?

Personnally, I use some usual desktop PCs for the HA, MR, Access

> Mobile Node Debug Output
> =====================
> Wed Jul 18 23:32:38 mn_move: 1578
> Wed Jul 18 23:32:38 mn_move: in foreign net
> Wed Jul 18 23:32:39 mn_move: 1578
> Wed Jul 18 23:32:39 mn_move: in home net
> Wed Jul 18 23:32:44 mn_move: 1578
> Wed Jul 18 23:32:44 mn_move: in foreign net
> Wed Jul 18 23:32:45 mn_move: 1578
> Wed Jul 18 23:32:45 mn_move: in home net

Looks like your MN moves to the Home Network right after (1 sec.)
finding a foreign network. I think it does not send any BU because it
does not have the time to send one :-)

How do you performs handovers? Are your APs configuration OK
(different channel and ESSID, etc.)?