Hi David, On Thu, Aug 23, 2012 at 2:26 PM, David Romero <[email protected]> wrote: > I don't know if my problem has relationship with last Johhanes's path: > > whith this configuration > mesh1 ----- meshGate ---- eth router adsl----- internet > > I sniffed with kismet and meshGate is transmiting root and RANN signals, but > mesh1 in a path dump only shows a mac to meshgate as other normal mesh > nodes: ¿normal? it could be good to have a default path but I'm not sure > about this point.
This patch won't affect the mpaths at all. That said, the current mpath addressing implementation could use some careful testing and review. > Another point is that I have to add a line like this in any mesh node to > work: > "route add default mesh_interface", it works but I think is not correct > because you use level 3 (is there another way to do it?), I get ping from > node 1 to eth port of the router (good) but if I try to ping from node 1 to > internet (8.8.8.8) I get no answer, and wireshark shows in eth port of > router that node1 is arp-broadcast asking who has 8.8.8.8., ther router > don't send the packets to internet. Is all right or mesh gate had to resend > the packet to router as DA right. > > If instead of "add route default mesh_interface", I use "route add default > gw 10.0.0.1(router adress)" all works perfect but in full level 3.. shit. Just bridging meshGate and the ethernet interface should work fine. Thomas _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
