SECN 2.0RC6 for MP01?

[Peter Retief]

Terry

I am looking to deploy a Ubuiquiti Bullet M2HP as an access point, and to use MP01's as pure client ATA's in a simple environment where mesh is not required.

1) Can you create a version of SECN2.0RC6 for the MP01? I see the firmware for the MP01 is still at RC3 - are the improvements meaningful for the MP01?
2) If I load generic OpenWRT Attitude Adjustment on the Bullet M2HP (I doubt that I need SECN for this simple AP?), will I still run into the ath5k/madwifi incompatibility issue?

Regards

Peter

[T Gillett]

Hi Peter

I am not sure I quite understand the network arrangement.

Just to clarify, is it that you will have the Bullet as a central AP, and the MP01s running as simple wifi clients (ie in 'sta' mode) in order to get an upstream connection fr the phones?

There will be no AP running on the MP01s?

Assuming this is the case...

1. We are working on bringing the  MP01 up to the same level as the MP02, but there are some issues we are battling with. But the functional changes from RC3 should not be relevant to what you are doing.

The compatibility issue between  ath9k and madwifi is nothing to do with SECN.

It is fundamental in the OpenWrt wifi drivers. 

That said, the issue may not be critical for your application as it results in a limit on the upstream bandwidth from the MP01 (runing madwifi) to the Bullet (running ath9k). 

But the limitation is something approaching 1Mbps, so if you are only using voice on the MP01s then it should not have any effect.

2. You can certainly run the Bullet with the stable AA 12.09 image from OpenWrt Downloads and configure it as an AP with the supplied LuCI interface.

Equally I imagine you could use the standard Ubiquity firmware for the same purpose.

All that remains is to configure the MP01 as a simple wifi client, with the SSID and Passphrase to match the AP. That is quite simple to do but will require a small hack of the RC3c firmware as it is not a mode that is explicitly supported in the SECN configuration interface.

You could also use the SECN 1.1 GA01 stable firmware as your starting point since you are not using any mesh. A similar small hack would apply.

Regards

Terry 

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.

[Peter Retief]

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.

[T Gillett]

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.

[Peter Retief]

Terry

I am struggling to get the MP01 into client mode, following your page http://wiki.villagetelco.org/How_To_Set_up_SECN_2.0_Mesh_Potato_as_a_Wifi_ATA

Here is /etc/config/network:

config 'interface' 'loopback'

        option 'ifname' 'lo'

        option 'proto' 'static'

        option 'ipaddr' '127.0.0.1'

        option 'netmask' '255.0.0.0'

config 'interface' 'lan'

        option 'type' 'bridge'

        option 'ifname' 'eth0 bat0 ath1'

        option 'proto' 'static'

        option 'netmask' '255.255.255.0'

        option 'dns' '8.8.8.8'

        option 'broadcast' '10.130.1.255'

        option 'ipaddr' '10.130.1.20'

        option 'gateway' '10.130.1.1'

        option 'stp' '1'

config 'interface' 'wifi0'

        option 'ifname' 'ath0'

        option 'proto' 'static'

        option 'ipaddr' '10.10.1.20'

        option 'netmask' '255.255.255.0'

        option 'mtu' '1528'

        option 'broadcast' '10.10.1.255'

#  PFR added the next section

config 'interface' 'client_0'   

        option 'proto' 'dhcp'

Here is /etc/wireless:

config 'wifi-device' 'wifi0'

        option 'type' 'atheros'

        option 'regdomain' '0x35'

        option 'channel' 'auto'

        option 'country' '276'

config 'wifi-iface' 'mesh'

        option 'device' 'wifi0'

        option 'mode' 'ahdemo'

        option 'ssid' 'vt-mesh'

        option 'bssid' '02:CA:FF:EE:BA:BE'

        option 'swmerge' '1'

        option 'bgscan' '0'

        option 'maxassoc' '0'

        option 'txpower' '17'

        option 'bursting' '0'

        option 'turbo' '0'

        option 'disabled' '1'

config 'wifi-iface' 'sta_0'

        option 'device' 'wifi0'

        option 'network' 'client_0'

        option 'mode' 'sta'

        option 'ssid' 'crocbillion'

        option 'encryption' ''

        option 'key' 'mysecret'

        option 'disabled' '0'

The access point is a Billion router for now, with ssid "crocbillion", open access at present, dhcp enabled.  Other devices connect fine.

If I disable and re-enable wifi:

root@MP-20:/etc/config# wifi down

root@MP-20:/etc/config# udhcpc: bind: No such device

root@MP-20:/etc/config# wifi up

udhcpc (v1.14.4) started

Sending discover...

root@MP-20:/etc/config# Sending discover...

Sending discover...

root@MP-20:/etc/config# iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

br-lan    no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:"crocbillion"  Nickname:""

          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   

          Bit Rate:36 Mb/s   Tx-Power=17 dBm   Sensitivity=1/1  

          Retry:off   RTS thr:off   Fragment thr:off

          Encryption key:off

          Power Management:off

          Link Quality=19/70  Signal level=-77 dBm  Noise level=-96 dBm

          Rx invalid nwid:11  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath1      IEEE 802.11g  ESSID:"vt-mesh"  Nickname:""

          Mode:Ad-Hoc  Channel:0  Cell: 02:CA:FF:EE:BA:BE   

          Bit Rate:0 kb/s   Tx-Power=17 dBm   Sensitivity=1/1  

          Retry:off   RTS thr:off   Fragment thr:off

          Encryption key:off

          Power Management:off

          Link Quality=19/70  Signal level=-77 dBm  Noise level=-96 dBm

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@MP-20:/etc/config# ifconfig

ath0      Link encap:Ethernet  HWaddr 00:09:45:5B:6A:0E  

          UP BROADCAST RUNNING MULTICAST  MTU:1528  Metric:1

          RX packets:2 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:106 (106.0 B)  TX bytes:403 (403.0 B)

ath1      Link encap:Ethernet  HWaddr 06:09:45:5B:6A:0E  

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:0 (0.0 B)  TX bytes:294 (294.0 B)

br-lan    Link encap:Ethernet  HWaddr 00:09:45:5B:6A:0F  

          inet addr:10.130.1.20  Bcast:10.130.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2307 errors:0 dropped:0 overruns:0 frame:0

          TX packets:599 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:201223 (196.5 KiB)  TX bytes:95649 (93.4 KiB)

br-lan:9  Link encap:Ethernet  HWaddr 00:09:45:5B:6A:0F  

          inet addr:172.31.255.254  Bcast:172.31.255.255  Mask:255.255.255.252

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr 00:09:45:5B:6A:0F  

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2341 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1523 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:240335 (234.7 KiB)  TX bytes:144688 (141.2 KiB)

          Interrupt:4 Base address:0x1000 

lo        Link encap:Local Loopback  

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:5 errors:0 dropped:0 overruns:0 frame:0

          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:461 (461.0 B)  TX bytes:461 (461.0 B)

wifi0     Link encap:UNSPEC  HWaddr 00-09-45-5B-6A-0E-2A-C3-00-00-00-00-00-00-00-00  

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:673 errors:0 dropped:39 overruns:0 frame:29

          TX packets:362 errors:21 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:195 

          RX bytes:83621 (81.6 KiB)  TX bytes:20592 (20.1 KiB)

          Interrupt:3 Memory:b0000000-b00ffffc 

Any ideas?

Peter

[Peter Retief]

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.

[T Gillett]

Hi Peter

I have had a look at this set up.

I found some problems with trying (to remember how) to configure sta mode in the old version of OpenWrt used in SECN 1, so rather than pursue that I thought I would have a look at SECN RC3d as the config is closer to what we are currently using, and it also gives you ath5k instead of madwifi, thus avoiding that interop issue.

To set it up in RC3d, assuming a newly flashed device with its IP set up appropriately, do the following:

1. In the SECN web interface, on the Advanced page, untick the checkboxes to disable AP and Mesh, then click the Save button.

2. Add the following to /etc/config/wireless

config 'wifi-iface' 'sta_1'

        option 'device' 'radio0'

        option 'ifname' 'wlan0-3'

        option 'mode' 'sta'

        option 'network' 'client_0'

        option 'ssid' 'guest-ap'     ###

        option 'key' 'potato123'    ###

        option 'encryption' 'psk'   ###

        option 'disabled' '0' 

This example uses SSID 'guest-ap' with 'psk' encryption and passphrase 'potato123'. Adjust to suit.

Note: keep the SSID strings simple alpha-numeric. I had issues with some mixed case and special character strings. 

3. Add the following to /etc/config/network:

config 'interface' 'client_0'

        option 'proto' 'static'

        option 'ipaddr' '10.130.1.138'         ###

        option 'netmask' '255.255.255.0'   ###

        option 'gateway' '10.130.1.252'     ###

This example assigns a static IP to the MP that is in the subnet used by the host AP. 

You can use DHCP also:

config 'interface' 'client_0'

        option 'proto' 'dhcp'

That's it. Reboot and see what happens.

One thing to remember with this set up is that it is designed to allow an MP to be configured with a VoIP/SIP account for an upstream provider.

I have set this up in the demo and it tests OK, at least for outgoing calls. See attached doc.

What you can _not_ do is connect directly to other MPs on a peer to peer basis as you can over a mesh.

This is because of the networking between the client devices. 

You can not ping one MP from another. Neither can you ping the host AP device from an MP.

This is a bit strange and I can not quite understand why this is so in such a simple wifi host - client set up. 

I don't think it is anything in our network configuration, but someone smarter than me may be able to spot it.

I don't know what your exact requirement for this system was in terms of peer to peer calling, or calling via an upstream SIP provider/device. But hopefully this will be of some use.

I suggest you do some testing to see what mileage you can get out of it.

If you decide to go ahead I should (hopefully) be able to give you some updated SECN 2 code for the MP01-FXS device before you go live.

We plan to revisit the WiFi Client mode of operation in a future release of SECN2 so that the devices can be used in relay mode and support peer to peer calling.  But it is a complication we don't want in the current release :-)

Regards

Terry

To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/001001cf88ba%24593bce60%240bb36b20%24%40gmail.com.

[Peter Retief]

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.

[T Gillett]

Hi Peter

That sounds promising.

I don't think there is much between RC3c and RC3d that will affect what you are doing.

You are probably right about my having the IP wrong on the LAN side - I was trying several different arrangements and probably got mixed up in the end. I will go back and check it.

Regarding the issue of LAN to WAN connectivity. Where is this an issue?

There is no WAN on the MP01, so I am obviously missing something...

Terry

To view this discussion on the web visit https://groups.google.com/d/msgid/village-telco-dev/000d01cf8925%24131d5b40%24395811c0%24%40gmail.com.