ngnodemap must be set for rj45 type nodes as well, otherwise

deployCfg would break when attempting to connect an rj45 node to
whatever is on the other side of the link.

With this change plus a kernel-level fix to be submitted to p4
shortly communication to external world via "rj45" nodes should
work properly.

Bug found by:
Submitted by:
Reviewed by:
Approved by:
Obtained from:

diff --git a/rj45.tcl b/rj45.tcl
index 7de56a5fac9358e1761f95c5b194d076bd71716d..48a3744d8b8b3edeecafcdef5b0904fa5519b0ba 100755 (executable)
--- a/rj45.tcl
+++ b/rj45.tcl
@@ -1,4 +1,4 @@
-# $Id: rj45.tcl,v 1.9 2007/05/07 08:43:20 ana Exp $ 
+# $Id: rj45.tcl,v 1.10 2007/08/30 18:54:35 marko Exp $ 
 #
 # Copyright 2005 University of Zagreb, Croatia.  All rights reserved.
 #
@@ -77,7 +77,10 @@ proc $MODULE.layer {} {
 #****
 
 proc $MODULE.instantiate { eid node } {
+    global ngnodemap
+
     set ifname [getNodeName $node]
+    set ngnodemap($ifname) $ifname
     nexec ifconfig $ifname up promisc
 }