hello everyone....did somebody know how to move from one ESSID/network to
another ESSID?network without using command : iwconfig eth0 essid visitnet??
i mean i want my wireless card to detect automatically the network when it has
lose the homenet signal..
please reply
[EMAIL PROTECTED] wrote: Send mipl mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of mipl digest..."
Today's Topics:
1. md expire router message ([EMAIL PROTECTED])
2. Re: mipl Digest, Vol 44, Issue 4 ([EMAIL PROTECTED])
3. Re: md expire router message (shariq haseeb)
4. MIPL/NEPL problems with 3Com NICs (Tobias Hof)
5. How to shut down the DAD probe? (tian tian)
----------------------------------------------------------------------
Message: 1
Date: 11 Dec 2006 12:10:37 +0800
From: [EMAIL PROTECTED]
Subject: [mipl] md expire router message
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
Hi, i'm having a problem with expire router. I had follow all the instruction
the document HOWTO. I successfully ping all my network (Home Agent, MN and AR).
This is my test bed:
AR========R+HA MN
The document test bed said that R and HA is different machine, but i just
combined it, i guess that is nothing wrong with it. The problem with the
pinging is it only can last about 18-19 minutes (i do not change to visitnet).
After that period, all the icmp message will return 'Destination unreachable'.
This is my MN message:
[EMAIL PROTECTED] ~]# mip6d -c /etc/mipv6/mip6d.conf
mip6d[4697]: MIPL Mobile IPv6 for Linux v2.0.2 started (Mobile Node)
main: MIPL Mobile IPv6 for Linux started in debug mode, not detaching from
terminal
conf_show: config_file = /etc/mipv6/mip6d.conf
conf_show: vt_hostname = localhost
conf_show: vt_service = 7777
conf_show: mip6_entity = 1
conf_show: debug_level = 10
conf_show: PolicyModulePath = [internal]
conf_show: DefaultBindingAclPolicy = 0
conf_show: NonVolatileBindingCache = disabled
conf_show: KeyMngMobCapability = disabled
conf_show: UseMnHaIPsec = enabled
conf_show: MnMaxHaBindingLife = 262140
conf_show: MnMaxCnBindingLife = 420
conf_show: MnRouterProbes = 1
conf_show: MnRouterProbeTimeout = 0.000000
conf_show: InitialBindackTimeoutFirstReg = 1.500000
conf_show: InitialBindackTimeoutReReg = 1.000000
conf_show: UseCnBuAck = disabled
conf_show: DoRouteOptimizationMN = enabled
conf_show: MnUseAllInterfaces = disabled
conf_show: MnDiscardHaParamProb = enabled
conf_show: SendMobPfxSols = enabled
conf_show: OptimisticHandoff = disabled
conf_show: SendMobPfxAdvs = enabled
conf_show: SendUnsolMobPfxAdvs = enabled
conf_show: MaxMobPfxAdvInterval = 86400
conf_show: MinMobPfxAdvInterval = 600
conf_show: HaMaxBindingLife = 262140
conf_show: DoRouteOptimizationCN = enabled
xfrm_cn_init: Adding policies and states for CN
xfrm_mn_init: Adding policies and states for MN
conf_home_addr_info: HoA address fec0:106:2700:0:0:0:0:4
conf_home_addr_info: HA address fec0:106:2700:0:0:0:0:2
__tunnel_add: created tunnel ip6tnl1 (6) from fec0:106:2700:0:0:0:0:4 to
fec0:106:2700:0:0:0:0:2 user count 1
conf_home_addr_info: Home address fec0:106:2700:0:0:0:0:4
flag_hoa: set HoA fec0:106:2700:0:0:0:0:4/128 iif 6 flags 10 preferred_time
4294967295 valid_time 4294967295
conf_home_addr_info: Added new home_addr_info successfully
__md_discover_router: discover link on iface eth1 (5)
md_change_default_router: add new router fe80:0:0:0:204:23ff:fe86:848d on
interface eth1 (5)
mn_addr_do_dad: DAD succeeded!
mn_move: 1535
mn_move: in home net
mv_hoa: move HoA fec0:106:2700:0:0:0:0:4/64 from iface 6 to 5
md_expire_router: expiring router fe80:0:0:0:204:23ff:fe86:848d on iface eth1
(5)
__md_discover_router: discover link on iface eth1 (5)
__md_discover_router: discover link on iface eth1 (5)
__md_discover_router: discover link on iface eth1 (5)
__md_discover_router: discover link on iface eth1 (5)
__md_discover_router: discover link on iface eth1 (5)
As the mesage show 'md_expire_router: expiring router fe80...', all the network
become unreachable, but before that it's ok. I just wait and the MN mentioned
'md_discover_router', but the network still unreachable 'pinging not
successful'.
And also at my HA, after the /etc/init.d/mip6d start, it doesnt show
'vt_server_init: VT server listens 127.0.0.1[7777] OK 4'
meaning that it doesn't listen to local host port 7777, is this has anything to
do with that? Your help is much highly appreciated.
--------------------------------------
http://www.um.edu.my
------------------------------
Message: 2
Date: 11 Dec 2006 14:50:42 +0800
From: [EMAIL PROTECTED]
Subject: Re: [mipl] mipl Digest, Vol 44, Issue 4
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
Jaewon, HA, MN and CN must all be patched with 2.6.16 kernel, i guess so, cause
mine work just fine
On 09.12.2006 18:00:02, [EMAIL PROTECTED] wrote:
>Send mipl mailing list submissions to
> [email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
>or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
>You can reach the person managing the list at
> [EMAIL PROTECTED]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of mipl digest..."
>
>
>Today's Topics:
>
> 1. HA didn't answer DAD probe! (Jaewon "Jay" Kang)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 8 Dec 2006 18:02:42 -0500
>From: "Jaewon "Jay" Kang"
>Subject: [mipl] HA didn't answer DAD probe!
>To:
>Message-ID: <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset="us-ascii"
>
>Dear All,
>
>I am testing the handover among Home network and Foreign networks.
>When my Mobile Node moves between foreign networks, it is fine.
>But, whenever, my mobile node goes back to the home network, the mip6d
>complains as follows.
>
>mn_addr_do_dad: HA didn't answer DAD probe!
>
>Does anyone has the similar problem and answers?
>
>The mip6d running on the MN is patched for kernel 2.6.16.
>The mip6d running on the Home Agent and Corresponding node are not
>patched.
>
>Thanks in advance.
>
>- J
>
>Jaewon "Jay" Kang
>Senior Research Scientist
>Applied Research
>Telcordia Technologies
>----------------------------------------
>Voice) 732-699-3956
>Email) [EMAIL PROTECTED]
>
>
>
>
>
>------------------------------
>
>_______________________________________________
>mipl mailing list
>[email protected]
>http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
>
>End of mipl Digest, Vol 44, Issue 4
>***********************************
>
--------------------------------------
http://www.um.edu.my
------------------------------
Message: 3
Date: Sun, 10 Dec 2006 23:02:50 -0800 (PST)
From: shariq haseeb
Subject: Re: [mipl] md expire router message
To: [EMAIL PROTECTED], [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
Dear saaidal,
Firstly:
You dont get this message
'vt_server_init: VT server listens 127.0.0.1[7777]OK
4'
because you havent enabled the vt server while
installing the mipl userspace. to install the vt
server, you have to write in the user space directory.
# CPPFLAGS=-I/usr/src/linux/include ./configure
--enable-vt
# make
# make install
And this has nothing to do with your problem of router
expire.
Secondly (your main problem):
I think you are using link address "fec0....". Try
changing to global "eg: 2001::1/64". support for link
local address has been removed.
It should work.
rgds,
Shariq
--- [EMAIL PROTECTED] wrote:
> Hi, i'm having a problem with expire router. I had
> follow all the instruction the document HOWTO. I
> successfully ping all my network (Home Agent, MN and
> AR). This is my test bed:
>
> AR========R+HA MN
>
> The document test bed said that R and HA is
> different machine, but i just combined it, i guess
> that is nothing wrong with it. The problem with the
> pinging is it only can last about 18-19 minutes (i
> do not change to visitnet). After that period, all
> the icmp message will return 'Destination
> unreachable'. This is my MN message:
>
> [EMAIL PROTECTED] ~]# mip6d -c /etc/mipv6/mip6d.conf
> mip6d[4697]: MIPL Mobile IPv6 for Linux v2.0.2
> started (Mobile Node)
> main: MIPL Mobile IPv6 for Linux started in debug
> mode, not detaching from terminal
> conf_show: config_file = /etc/mipv6/mip6d.conf
> conf_show: vt_hostname = localhost
> conf_show: vt_service = 7777
> conf_show: mip6_entity = 1
> conf_show: debug_level = 10
> conf_show: PolicyModulePath = [internal]
> conf_show: DefaultBindingAclPolicy = 0
> conf_show: NonVolatileBindingCache = disabled
> conf_show: KeyMngMobCapability = disabled
> conf_show: UseMnHaIPsec = enabled
> conf_show: MnMaxHaBindingLife = 262140
> conf_show: MnMaxCnBindingLife = 420
> conf_show: MnRouterProbes = 1
> conf_show: MnRouterProbeTimeout = 0.000000
> conf_show: InitialBindackTimeoutFirstReg = 1.500000
> conf_show: InitialBindackTimeoutReReg = 1.000000
> conf_show: UseCnBuAck = disabled
> conf_show: DoRouteOptimizationMN = enabled
> conf_show: MnUseAllInterfaces = disabled
> conf_show: MnDiscardHaParamProb = enabled
> conf_show: SendMobPfxSols = enabled
> conf_show: OptimisticHandoff = disabled
> conf_show: SendMobPfxAdvs = enabled
> conf_show: SendUnsolMobPfxAdvs = enabled
> conf_show: MaxMobPfxAdvInterval = 86400
> conf_show: MinMobPfxAdvInterval = 600
> conf_show: HaMaxBindingLife = 262140
> conf_show: DoRouteOptimizationCN = enabled
> xfrm_cn_init: Adding policies and states for CN
> xfrm_mn_init: Adding policies and states for MN
> conf_home_addr_info: HoA address
> fec0:106:2700:0:0:0:0:4
> conf_home_addr_info: HA address
> fec0:106:2700:0:0:0:0:2
> __tunnel_add: created tunnel ip6tnl1 (6) from
> fec0:106:2700:0:0:0:0:4 to fec0:106:2700:0:0:0:0:2
> user count 1
> conf_home_addr_info: Home address
> fec0:106:2700:0:0:0:0:4
> flag_hoa: set HoA fec0:106:2700:0:0:0:0:4/128 iif 6
> flags 10 preferred_time 4294967295 valid_time
> 4294967295
> conf_home_addr_info: Added new home_addr_info
> successfully
> __md_discover_router: discover link on iface eth1
> (5)
> md_change_default_router: add new router
> fe80:0:0:0:204:23ff:fe86:848d on interface eth1 (5)
> mn_addr_do_dad: DAD succeeded!
> mn_move: 1535
> mn_move: in home net
> mv_hoa: move HoA fec0:106:2700:0:0:0:0:4/64 from
> iface 6 to 5
> md_expire_router: expiring router
> fe80:0:0:0:204:23ff:fe86:848d on iface eth1 (5)
> __md_discover_router: discover link on iface eth1
> (5)
> __md_discover_router: discover link on iface eth1
> (5)
> __md_discover_router: discover link on iface eth1
> (5)
> __md_discover_router: discover link on iface eth1
> (5)
> __md_discover_router: discover link on iface eth1
> (5)
>
>
> As the mesage show 'md_expire_router: expiring
> router fe80...', all the network become unreachable,
> but before that it's ok. I just wait and the MN
> mentioned 'md_discover_router', but the network
> still unreachable 'pinging not successful'.
>
> And also at my HA, after the /etc/init.d/mip6d
> start, it doesnt show
> 'vt_server_init: VT server listens 127.0.0.1[7777]
> OK 4'
>
> meaning that it doesn't listen to local host port
> 7777, is this has anything to do with that? Your
> help is much highly appreciated.
>
> --------------------------------------
> http://www.um.edu.my
>
> _______________________________________________
> mipl mailing list
> [email protected]
>
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
>
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com
------------------------------
Message: 4
Date: Mon, 11 Dec 2006 09:18:51 +0100
From: "Tobias Hof"
Subject: [mipl] MIPL/NEPL problems with 3Com NICs
To: [email protected]
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
Dear all,
I would like to know if any body of you has already experienced misbehaviour
of 3Com (Ethernet) NICs when experimenting with MIPL, NEPL or simply IPv6...
For the moment, I can tell from three observations:
1/ Some time ago, I had a problem with a simple Nemo implementation based on
MIPL 1.0. The problem was that the CoA expired without being renewed (the
RAs continued to be sent), and thus the BU expired as well and the mobility
support failed.
2/ Last week, I assisted a partner who expirienced problems to setup a NEPL
0.2 platform in this lab with a correct configuration (addresses, radvd,
nemod). The problem as that when nemod was switched on (on a visisted
network), it started quite well but did not at all recognize that it was
conencted to a visited link, totally ignoring the RAs and not configuring a
Stateless Address. Regarding the behaviour and output of nemod, it was as if
the MR was totally isolated, not connected.
However, we are sure that the configuration was correct because after
replacing the 3Com NICs he used, everything worked perfect immediately.
3/ When setting up a NEPL platform with (Nautlilus6) MCoA support, I used a
3Com NIC as second egress interface, besides 2 Intel NICs as first egress
and as ingress interface.
Basic NEPL worked fine, only using the Intel cards. However, when deploying
NEPL+MCoA with the 3Com card, it started well, registered both CoAs with the
HA, but as soon as there was any movement (disconnection from the visited
link, HO to another visisted link) on one of the egress interfaces, nemoed
did not always correctly de-register the old CoA or not correctly register
the new one, letting expire one or both bindings.
Then, each time when trying to stop the deaemon (Ctrl-C in debug level 10),
I realized that it was somehow stuck: It displayed "SIGINT received", but
did not go any further, i.e. did not exit properly. Also, the tunnel(s) set
up by the daemon were not erased, but continued to exist after killing the
(stuck) daemon
We did not have the time to analyse in detail this strange behaviour, but it
might be due to incorrect handling of RAs..
In any case, if somebody has had similar problems or even found a
workaround, I owuld be pleased to hear about that!
Best regards,
Tobias
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.mobile-ipv6.org/pipermail/mipl/attachments/20061211/56d8bf9d/attachment.html
------------------------------
Message: 5
Date: Mon, 11 Dec 2006 08:31:03 +0000
From: "tian tian"
Subject: [mipl] How to shut down the DAD probe?
To: [email protected]
Message-ID:
Content-Type: text/plain; charset=gb2312; format=flowed
Hallo All,
I want to do the handover tests without the DAD process, does anyone know
how to shut down this porbe?Which configration file can be changed in
order to shut down and turn on this DAD probe freely?
Regards
Tian
_________________________________________________________________
?????????????? Live Messenger;
http://get.live.com/messenger/overview
------------------------------
_______________________________________________
mipl mailing list
[email protected]
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
End of mipl Digest, Vol 44, Issue 5
***********************************
---------------------------------
Access over 1 million songs - Yahoo! Music Unlimited.
_______________________________________________
mipl mailing list
[email protected]
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
