Closed max-b closed 8 years ago
From notdhcpserver/client, treeherder's extender node brought up interface eth0.2 with the mesh IP address. The extender node is set up only to have babeld running on the eth0.1 interface: https://github.com/sudomesh/sudowrt-firmware/blob/master/files_extender-node/etc/config/babeld
eth0.2
eth0.1
I'm pretty sure this is something that needs to get fixed at the home node level, but I don't have time just this second to figure it out and wanted to flag for future.
024e2b1ef92397c58443df0609a6fe2d7b71d204 and e05265215ce741dbaf8ba3dc7aa0ca1fbee17dc8 fix this.
From notdhcpserver/client, treeherder's extender node brought up interface
eth0.2
with the mesh IP address. The extender node is set up only to have babeld running on theeth0.1
interface: https://github.com/sudomesh/sudowrt-firmware/blob/master/files_extender-node/etc/config/babeldI'm pretty sure this is something that needs to get fixed at the home node level, but I don't have time just this second to figure it out and wanted to flag for future.