Ubuntu
miredo package

lucid alpha 1: miredo doesn't autostart after boot

Bug #497943 reported by Sander Jonkers on 2009-12-17

This bug report is a duplicate of: Bug #485377: Miredo dies unexpectedly on reload signals.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	miredo (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: miredo

lucid alpha 1:

miredo is installed, and works after a manual "sudo /etc/init.d/miredo start", but it doesn't autostart after a boot

Everything worked OK on earlier versions of Ubuntu

So, IMHO this is a bug. The problem could be in miredo, or in the boot process.

ubuntu@ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:42:13:41:73
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:16

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)

wlan0 Link encap:Ethernet HWaddr 00:18:de:10:c5:06
          inet addr:192.168.1.37 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::218:deff:fe10:c506/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:3057 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2930 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2769580 (2.7 MB) TX bytes:620681 (620.6 KB)

ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ sudo /etc/init.d/miredo start
* Starting Teredo IPv6 tunneling daemon miredo [ OK ]

teredo Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: 2001:0:53aa:64c:1c40:b059:ad55:e84b/32 Scope:Global
          inet6 addr: fe80::ffff:ffff:ffff/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B) TX bytes:96 (96.0 B)

wlan0 Link encap:Ethernet HWaddr 00:18:de:10:c5:06
          inet addr:192.168.1.37 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::218:deff:fe10:c506/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:5596 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4524413 (4.5 MB) TX bytes:1120738 (1.1 MB)

ubuntu@ubuntu:~$

ProblemType: Bug
Architecture: i386
Date: Thu Dec 17 20:07:05 2009
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: miredo 1.2.1-1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-7.10-generic
SourcePackage: miredo
Tags: lucid
Uname: Linux 2.6.32-7-generic i686

Tags:

Revision history for this message

Sander Jonkers (jonkers) wrote on 2009-12-17:

Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Inox (inox) wrote on 2010-05-11:

I'm not sure, if it is a duplicate of #485377.
I suppose your wlan0 is down during boot-up and eth0 link is down.
Try ps -A in terminal to check, if miredo was started or not.

However it should reconnect later (even if there was no network access during boot-up) and that's what was fixed in miredo 1.2.2.