networking hosed after upgrading to 10.04

[scar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

scar @ 05/31/2011 05:29 PM:
> so all that's left is figuring out why i need to restart the networking
> init.d script upon boot in order to get a functioning connection...

now this is interesting... i was looking through my Tor log to be sure
it started up fine with the sketchy network connection, and it appears
to me that my network connection initially works fine but then drops out
shortly afterwards and remains that way until i restart networking.  you
can see that the service gets about 80% started and then throws some
routing errors.  between that time and the time it gets to 100% is when
i restarted the networking.

May 31 17:22:06.947 [notice] Interrupt: will shut down in 30 seconds.
Interrupt again to exit now.
May 31 17:22:36.082 [notice] Clean shutdown finished. Exiting.
May 31 17:24:01.027 [notice] Tor 0.2.1.30 opening log file.
May 31 17:24:01.028 [notice] Parsing GEOIP file.
May 31 17:24:01.156 [notice] OpenSSL OpenSSL 0.9.8k 25 Mar 2009 [9080bf]
looks like it's older than 0.9.8l, but some vendors have backported
0.9.8l's renegotiation code to earlier versions, and some have
backported the code from 0.9.8m or 0.9.8n.  I'll set both SSL3_FLAGS and
SSL_OP just to be safe.
May 31 17:24:02.886 [notice] We now have enough directory information to
build circuits.
May 31 17:24:02.886 [notice] Bootstrapped 80%: Connecting to the Tor
network.
May 31 17:25:33.056 [warn] Problem bootstrapping. Stuck at 80%:
Connecting to the Tor network. (No route to host; NOROUTE; count 10;
recommendation warn)
May 31 17:25:36.062 [warn] Problem bootstrapping. Stuck at 80%:
Connecting to the Tor network. (No route to host; NOROUTE; count 11;
recommendation warn)
May 31 17:25:56.319 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
May 31 17:25:56.319 [warn] router_orport_found_reachable(): Bug: ORPort
found reachable, but I have no routerinfo yet. Failing to inform
controller of success.
May 31 17:25:57.482 [warn] Problem bootstrapping. Stuck at 80%:
Connecting to the Tor network. (Invalid argument; RESOURCELIMIT; count
12; recommendation warn)
May 31 17:25:57.832 [notice] Guessed our IP address as 65.103.211.127
(source: 174.140.163.93).
May 31 17:25:58.924 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
May 31 17:26:06.843 [notice] Bootstrapped 85%: Finishing handshake with
first hop.
May 31 17:26:07.837 [notice] Bootstrapped 90%: Establishing a Tor circuit.
May 31 17:26:08.995 [notice] Tor has successfully opened a circuit.
Looks like client functionality is working.
May 31 17:26:08.995 [notice] Bootstrapped 100%: Done.
May 31 17:27:07.136 [notice] Self-testing indicates your DirPort is
reachable from the outside. Excellent.
May 31 17:27:22.961 [notice] Performing bandwidth self-test...done.


-----BEGIN PGP SIGNATURE-----

iEYEAREIAAYFAk3lif8ACgkQXhfCJNu98qCIHwCfZXV1sYMMERbq1Tan3Axt6EZu
V2oAn0HlcWC3j3+aiTpdMiJ6oID5MLki
=4itS
-----END PGP SIGNATURE-----