The problem from beta network has not yet been solved. You can check it
by doing a traceroute to your EID. You will see that there is a loop.
Regards
Albert
On 05/07/2013 10:39 AM, Teto wrote:
Will i spoke too quickly based on LispmobWRT but after capturing the
traffic it seems like outgoing traffic doesn't get encapsulated so
taht's why it worked. Getting back to the method I am most used to, I
ran lispmob on my host and still have these messages (82.121.X.X =
RLOC IP):
DEBUG-2: The entry 82.121.100.X is not found in the data base
DEBUG-2: The entry 82.121.100.X is not found in the data base
DEBUG-2: The entry 82.121.100.X is not found in the data base
so still don't know if it's my fault, lispmob's, or the network xD
sorry for the noise.
On Tue, May 7, 2013 at 10:08 AM, Teto <[email protected]> wrote:
thanks. It works again ! Is there any mailing-list/RSS feed where this
problem was announced ? It would have saved me some time ^^
Matt
On Mon, May 6, 2013 at 4:06 PM, Lori Jakab <[email protected]> wrote:
On 05/06/2013 04:01 PM, Teto wrote:
Hi,
I've received a call from coworkers. It looks like the lisp testbed is
down though they couldn't tell me the reason (so lispmob or my config
would not be at fault). Do you have more information ?
For instance http://www.lisp4.net/ is unreachable
There seems to be a routing loop somewhere in the PxTR infrastructure,
and the Beta Network operators have been notified. Hopefully the issue
will be fixed soon.
-Lori
Matt
On Mon, May 6, 2013 at 1:16 PM, Albert López <[email protected]> wrote:
Hi Matthieu,
Thanks for your message we will check what is happening and come back to
you.
Regards
Albert
On 05/06/2013 12:41 AM, Teto wrote:
Hi,
I've an annoying problem and I don't know why it happens. Lispmob used
to work but not anymore. It registers correctly, I use and
google DNS, I've no firewalls setup either on my laptop or in the
modem. I can see with wireshark DNS requests coming out of ppp0
(running pppoe) but no answer come back. I've joined an output of the
lispmob trunk version but I have the same problem (and same error
message) with the current official version of lispmob.org 0.3.1. (btw,
lispd -v returns a wrong version 3.0.0 number in every case, whereas
the log displays a correct version).
This is a message that comes back often.
"DEBUG-2: The entry 82.121.106.94 is not found in the data base" <-
this IP being my dynamic public IP= RLOC (it may not be the same RLOC
in the log), I found weird that lispmob does not know it.
Here is my routing table :
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0
lispTun0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0
ppp0
128.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0
lispTun0
193.253.160.3 0.0.0.0 255.255.255.255 UH 0 0 0
ppp0
teto@tatooine:~$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 48:5b:39:3d:1a:9c brd ff:ff:ff:ff:ff:ff
inet6 fe80::4a5b:39ff:fe3d:1a9c/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 1c:4b:d6:8b:c7:f6 brd ff:ff:ff:ff:ff:ff
5: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc
pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 82.121.108.252 peer 193.253.160.3/32 scope global ppp0
9: lispTun0: <POINTOPOINT,UP,LOWER_UP> mtu 1440 qdisc pfifo_fast state
UNKNOWN qlen 500
link/none
inet 153.16.49.112/32 scope global lispTun0
I am at yoru disposal for further tests
Best regards
MAtthieu
