Hi Hanno,
Here is a package patch you or others can try instead. The chilli
configuration comes out of one or more /etc/config/chilli UCI objects.
Each 'option' is a chilli option and 'tundev' is required (use tun0,
tun1, etc). If it works for you, we can make it a formal patch
submission.
Cheer
I believe the key is to give the visitor/user notice... so they know
their searches are being weighted toward a location/retailer and can
decide if that is something worth the free access. I don't think it is
any more 'man in the middle' as Google itself or in violation of any
terms of service prov
profile
Signed-off-by: David Bird <[EMAIL PROTECTED]>
Index: package/hostapd/files/hostapd.sh
===
--- package/hostapd/files/hostapd.sh(revision 11362)
+++ package/hostapd/files/hostapd.sh(working copy)
@@ -44,13 +44,
Hi devs,
I'm playing around with UCI configurations a bit, and was wondering if
it is desirable for programs to share certain configurations. For
instance, the hostapd UCI config patch I submitted allows the setting of
a RADIUS server. Other programs use RADIUS too, so I'm thinking of the
followin
s pkg,
but the ddns UCI config may be used for other similar programs just the same.
The "interface" is also required and multiple ddns blocks with different
interfaces/settings are possible.
Signed-off-by: David Bird <[EMAIL PROTECTED]>
Index: net/ez-ipupdate
Signed-off-by: David Bird <[EMAIL PROTECTED]>
Index: package/hostapd/files/hostapd.sh
===
--- package/hostapd/files/hostapd.sh(revision 11352)
+++ package/hostapd/files/hostapd.sh(working copy)
@@ -42,7
