routing: fix bug introduced during switch to pubkeys in routing table

This commit fixes a bug which was introduced when the routing table was
switched over to store full pub keys rather then public key hashes. The
switch was change was required in order to properly support onion
routing within the daemon. During the change the source node vertex
when receiving a message wasn’t converted to use public keys instead of
pubkeyhashes. As a result, nodes would be blind to any topology related
updates sent by its neighbors.

This commit fixes the bug by setting the source node of the received
message to the serialized public key rather than the pubkeyhash.

peer.go

@@ -3,6 +3,7 @@ package main
 import (
 	"bytes"
 	"container/list"
+	"encoding/hex"
 	"fmt"
 	"net"
 	"sync"
@@ -400,8 +401,10 @@ out:
 			*lnwire.NeighborUpdMessage,
 			*lnwire.RoutingTableRequestMessage,
 			*lnwire.RoutingTableTransferMessage:
+
 			// Convert to base routing message and set sender and receiver
-			p.server.routingMgr.ReceiveRoutingMessage(msg, graph.NewID(([32]byte)(p.lightningID)))
+			vertex := hex.EncodeToString(p.identityPub.SerializeCompressed())
+			p.server.routingMgr.ReceiveRoutingMessage(msg, graph.NewID(vertex))
 		}
 
 		if isChanUpdate {