Hi Martin,
We have never found this problem. We will try to reproduce it and fix
it. Thanks for your fed back.
Regards
Albert L.
On 03/19/2014 10:17 PM, Martin Grabner wrote:
Hi,
I’ve a problem with LISPmob on OpenWRT, that occurs when the 3G Stick
is reconnecting. After reconnect LISPmob uses 10.64.64.64 (actually
the default Gateway of this connection) as new RLOC and also pushes
that information to the Map Servers of the beta network. I used the
default web interface of OpenWRT 12.09 to configuring the 3G
connection. A restart of LISPmob is the only way to fix it. Here are
some informations and a log snippet:
ifconfig (before reconnect):
3g-drei Link encap:Point-to-Point Protocol
inet addr:178.113.1.33 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
ifconfig (after reconnect):
3g-drei Link encap:Point-to-Point Protocol
inet addr:178.113.103.101 P-t-P:10.64.64.64
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
default 10.64.64.64 0.0.0.0 UG 10 0 0
3g-drei
10.64.64.64 * 255.255.255.255 UH 0 0 0
3g-drei
snippet from Debug-2 log after forcing reconnect via OpenWRT web
interface:
DEBUG-2: =>process_netlink_msg: Received link message
DEBUG-2: process_nl_new_link: The new index of the interface 3g-drei
is: 72. Updating tables
DEBUG: del_rule: Removed rule in ip rule table for source routing of
src prefix: 178.113.1.33/32
DEBUG: add_rule: Added rule in ip rule table for source routing of src
prefix: 178.113.1.33/32
DEBUG-2: open_device_binded_raw_socket: open socket 6 in interface
3g-drei with afi: 2
WARNING: bind_socket_src_address: Cannot assign requested address
DEBUG: process_nl_new_link: Interface 3g-drei changes its status to DOWN
DEBUG-2: process_link_status_change: The detected change of status
doesn't affect
DEBUG-2: =>process_netlink_msg: Received link message
DEBUG: process_nl_new_link: Interface 3g-drei changes its status to DOWN
DEBUG-2: process_link_status_change: The detected change of status
doesn't affect
DEBUG-2: Finish pocessing netlink message
DEBUG-2: =>process_netlink_msg: Received new address message
DEBUG: del_rule: Removed rule in ip rule table for source routing of
src prefix: 178.113.1.33/32
DEBUG: add_rule: Added rule in ip rule table for source routing of src
prefix: 178.113.103.101/32 <— The real new IP/RLOC
DEBUG: precess_address_change: New address detected for interface
3g-drei -> 178.113.103.101 <— The real new IP/RLOC
DEBUG-2: =>process_netlink_msg: Received new route message
DEBUG-2: =>process_netlink_msg: Received del address message <— Why?
DEBUG-2: deleted address: 178.113.103.101 <— The real new IP/RLOC
DEBUG-2: =>process_netlink_msg: Received new address message
DEBUG: del_rule: Removed rule in ip rule table for source routing of
src prefix: 178.113.103.101/32
DEBUG: add_rule: Added rule in ip rule table for source routing of src
prefix: 10.64.64.64/32 <— Problem
WARNING: bind_socket_src_address: Cannot assign requested address
DEBUG: precess_address_change: New address detected for interface
3g-drei -> 10.64.64.64 <— Problem
DEBUG-2: =>process_netlink_msg: Received new route message
DEBUG-2: =>process_netlink_msg: Received link message
DEBUG: process_nl_new_link: Interface 3g-drei changes its status to UP
DEBUG-2: Default control interface down. Recalculate new control interface
DEBUG-2: Default IPv4 control iface 3g-drei: 10.64.64.64 <— Problem
What can I do that LISPmob doesn’t use the wrong IP as RLOC?
Regards
Martin
