Bluetooth services does not appear
by Ferry Toth
I'm trying to make my Edison board connect to my cell phone. The cell
phone is set to do tethering over bluetooth.
I can connect my PC (which uses network-manager) to the phone . So the
phone side configuration seems to be working fine.
Also, on the Edison side I can pair/trust/connect bluetooth to the phone
fine, or I can connect to the Edison from the phone side. In neither
case does a bluetooth service appear in connmanctl. In connmanctl I ahve
a bluetooth technology and can power it on/off fine.
Does anybody know what I am doing wrong here? Any suggestions are welcomed.
Note the Edison is not running it's factory firmware, but a rather
recent Yocto Sumo.
root@edison:~# uname -a
Linux edison 4.20.0-rc5-edison-acpi-standard #1 SMP Wed Dec 5 21:29:04
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@edison:~# bluetoothctl -v
bluetoothctl: 5.48
root@edison:~# /usr/sbin/connmand -v
1.35
1 year, 10 months
Annoying 169.254.x.x settings casually disrupting my connection :(
by Gabriele Zaverio
Hi there,
I have this problem - from time to time this 169.254.x.x network come
up totally unwanted - even if I set my interfaces by hand (ifconfig /
ip etc).
A lot of times I'm correctly configured for my LAN / Internet, and
suddendly I can't connect anymore. And ifconfig show that somehow my
interface is set to some 169.254.x.x address.
IMPORTANT NOTE:
I'm using Devuan GNU/Linux, so I don't have (don't want!) any systemd
bloatware around.
I don't have avahi-daemon or similar bloatware installed
This happens with dhclient running or not running.
I'm searching for a way to BLOCK this behaviour.
How can I FORBID this "Zeroconf / RFC3927 / apipa / whatever"
abomination to disrupt my network settings?
Please help me, my only way around this is to tweak the entire connman
source code :(
PS: *NO SYSTEMD*
Thank you everybody! :)
--
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio
Museo dell'Informatica funzionante - Freaknet Computer Museum
http://museum.freaknet.org || http://freaknet.org/asbesto
GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6 BBC5 EA15 9A4E 613D 44D7
1 year, 11 months
[PATCH] iptables: Set ip6t_ip6 flags if IPv6 rule protocol is set.
by Jussi Laakkonen
Flags is required to be set as IP6T_F_PROTO if protocol for IPv6 rule is
being set (INCLUDEDIR/linux/netfilter_ipv6/ip6_tables.h). Without this
being set, ICMPv6 rules, for example, are installed to ip6tables but no
packet matches the rule as protocol check is skipped in kernel.
---
src/iptables.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/src/iptables.c b/src/iptables.c
index 305a553f..a3581d22 100644
--- a/src/iptables.c
+++ b/src/iptables.c
@@ -2978,6 +2978,10 @@ static int parse_xt_modules(int c, bool invert,
ctx->proto = IPPROTO_IPV6;
fw6.ipv6.proto = ctx->proto;
+
+ /* Flags must be set for IPv6 if protocol is set. */
+ fw6.ipv6.flags |= IP6T_F_PROTO;
+
break;
default:
return 0;
@@ -3280,8 +3284,15 @@ static int parse_rule_spec(struct connman_iptables *table,
if (ctx->type == AF_INET)
ctx->ip->proto = ctx->proto;
- if (ctx->type == AF_INET6)
+ if (ctx->type == AF_INET6) {
ctx->ipv6->proto = ctx->proto;
+
+ /*
+ * Flags must be set for IPv6 if
+ * protocol is set.
+ */
+ ctx->ipv6->flags |= IP6T_F_PROTO;
+ }
}
break;
case 'j':
--
2.19.2
1 year, 11 months
[PATCHv2] iptables: Set protocol family in xtables setup.
by Jussi Laakkonen
When xtables loads a library for a match (-m) the protocol family is
used to get a correct version loaded. If a change has been made using a
match modifier in iptables rule with, e.g., IPv4 protocol family the
global xtables_matches array holding xtables_match structures is not
reset or changed (at least in iptables 1.6.1) to IPv6 when
xtables_init_all() (or any of the initialization functions) is called.
This commit fixes the issue of not being able to set some IPv6 rules
after IPv4 rules with matches have been set (or the other way around).
The family for the global variable xtables_matches has to be explicitely
updated when changing between IP protocol families.
Otherwise adding the following rules would result a failure, where
iptables calls exit() on ConnMan on the IPv6 rule:
__connman_firewall_add_rule(ctx, "filter", "INPUT", "-m conntrack
--ctstate ESTABLISHED,RELATED -j ACCEPT");
__connman_firewall_add_ipv6_rule(ctx, "filter", "INPUT", "-m conntrack
--ctstate ESTABLISHED,RELATED -j ACCEPT");
Depending on the match type, iptables may result in an error. The exit()
is called if the required library for the match cannot be loaded. This
change allows to avoid such situations.
---
src/iptables.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/iptables.c b/src/iptables.c
index 305a553f..a188f99a 100644
--- a/src/iptables.c
+++ b/src/iptables.c
@@ -3330,6 +3330,7 @@ static int current_type = -1;
static int setup_xtables(int type)
{
int err;
+ struct xtables_match *xt_m;
DBG("%d", type);
@@ -3351,6 +3352,13 @@ static int setup_xtables(int type)
}
if (!err) {
+ /*
+ * Set the match type, otherwise loading of matches in xtables
+ * will fail when IP protocol family has changed.
+ */
+ for (xt_m = xtables_matches; xt_m; xt_m = xt_m->next)
+ xt_m->family = type;
+
current_type = type;
} else {
connman_error("error initializing xtables");
--
2.19.1
1 year, 11 months
