Peter
--
You received this message because you are subscribed to the Google Groups "Village Telco Development Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to village-telco-...@googlegroups.com.
To post to this group, send email to village-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/002601cf87b8%240c23f8d0%24246bea70%24%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Terry
Your understanding is correct. I did see the modifications to SECN to set it to client-only non-mesh mode in the following URL:
http://wiki.villagetelco.org/How_To_Set_up_SECN_2.0_Mesh_Potato_as_a_Wifi_ATA
Would you advise starting with 2.0RC3 or 1.1GA01 for this purpose?
Peter
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/CAD58Ekwxw09zEJ5j_g7KG9MfsJ2hjrJ2xAsCd4gUOEnKBQE46w%40mail.gmail.com.
Peter
In general RC firmware should not be used for production work. The GA would be better to start with I think. At some point in the future you may wish to upgrade to a later GA version, just for supportability.
The instructions on the wiki page are OK for what you want.
I think the main thing now is to set up a couple of MP01s and an AP (on AR71 / ath9k) and test that the madwifi / ath9k interoperability issue is not going to affect the operation of the system.
Regards
Terry
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/002901cf87c8%2406b18560%2414149020%24%40gmail.com.
Terry
Forgot to specify – I followed your advice, and started with SECN 1.1 GA01 rv295.
Peter
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/CAD58Ekzt-G_-zu%2BurWD7skSzwJx%3Dai8kQUboufQ-O%3D4gyrD55w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/001001cf88ba%24593bce60%240bb36b20%24%40gmail.com.
Terry
Thanks for taking the trouble to look at my configs and provide advice.
SECN 2.0RC3d is not available on the download site – I used RC3c instead (are there significant fixes between RC3c and RC3d?).
Your patches worked perfectly, and I was able to connect in psk2 client mode as well as “none”. I had no problem pinging the AP from the MP01 – perhaps you had the 10.130.1.x network on both the lan and wlan0-3 interfaces?
The sip registration worked fine, and I could make calls.
One remaining issue – connectivity from the lan network to the wan network still seems to be broken – I am trying to work out how to nat between the lan and wan. I have enabled dhcp on the lan from the SECN page, and have left the “Use Device IP” check box ticked. From the lan I can access the mp01 with no problem, but packets destined for the wan do not arrive at destination (verified by wireshark).
You mention that you may be able to provide an updated SECN with MP01-fxs improvements? This is quite exciting – what has happened on the fxs front?
Peter
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/CAD58Ekzs_3_hPZ4smbjJD6jgNige7drM2T-g7TD9NknY1P%3DRsA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/000d01cf8925%24131d5b40%24395811c0%24%40gmail.com.