Age | Commit message (Collapse) | Author | Files | Lines |
|
Agent mode is mostly done, update the entry with Session mode and VPN
Agent support.
|
|
D-Bus aborts if we feed invalid characters to it. So do some sanity
check before that.
|
|
|
|
See RFC 3315 Chapter 18.1.2. Creation and Transmission of Confirm
Messages for details
|
|
This is required so that we can decide whether to send CONFIRM
or SOLICITATION message to server.
|
|
This is needed when implementing CONFIRM message decision logic.
|
|
MRD (Maximum Retransmission Duration) is the total duration of
of retransmission of the message. This will be used when sending
Confirm message.
|
|
The message status code was initialized too late i.e., after
it was set so we lost the status code. This problem was seen
with wide-dhcpv6 server.
|
|
If there is no callback set, don't try to call readline function.
|
|
Properly handle agent confirmation input, unset the prompt when RequestInput
processing ends and set the passphrase only if it contains some text.
|
|
|
|
|
|
Calling g_dbus_client_new followed by g_dbus_client_set_proxy_handlers
cause two calls to GetManagedObjects in a row as GetNameOwner reply is
asyncronously it triggers the second call because the handlers have
been set by g_dbus_client_set_proxy_handlers.
|
|
|
|
When receiving a RequestInput Agent API D-Bus call, ask the input in a somewhat
logical order from the user with user names first and passwords next. If a
passphrase is entered, ignore any WPS pin code requests. Prepare for passphrase
length checking by going through the RequestInput message to get the 'Type'
argument.
|
|
Report error and wait for the user to reply with yes/no.
|
|
Print out the RequestBrowser URL and wait for user input to proced. Add a
helper function for getting a yes/no confirmation from the user and another
one for getting the last part of the service object path.
|
|
Unref the saved Agent D-Bus message on Release and Cancel. In response to the
Release method call unnregister Agent interface and quit if in non-interactive
mode.
|
|
In command mode remember history and do command completion, in agent mode
do neither. Enable saving and restoring of the readline prompt and add
the GIOChannel watch also for non-interactive mode.
|
|
|
|
Add agent .h and .c files containing registering and unregistering functionality.
|
|
Enable a client method call return function to exit or continue running when
in non-interactive mode. When a connmanctl_dbus_method_return_func_t returns
-EINPROGRESS in non-interactive mode, the command line client is kept running
even after the method call has been processed.
The command line client needs to keep running after a successful Agent
registration in order to process Agent method calls. Also enabling tethering
in non-interactive mode needs the client executing until SSID, passphrase and
tethering mode have been set.
|
|
|
|
A mandatory elapsed time option was missing from the sent
DHCPv6 messages. See RFC 3315 chapter 22.9 for details.
|
|
If tethering is active when device is removed, then shutdown
tethering cleanly so that tether interface and bridge are
properly removed.
|
|
Currently tethering does not support IPv6 so its listener is
not created and is null. This will cause following output
connmand[18363]: src/dnsproxy.c:destroy_tcp_listener() index 31
(connmand:18363): GLib-CRITICAL **: g_io_channel_unref: assertion `channel != NULL' failed
connmand[18363]: src/dnsproxy.c:destroy_udp_listener() index 31
(connmand:18363): GLib-CRITICAL **: g_io_channel_unref: assertion `channel != NULL' failed
|
|
|
|
Remove now obsolete memebers from the option struct and instead add a description
field. Also remove the now unnecessary include.
|
|
|
|
|
|
This came from Daniel when running ConnMan using valgrind
==20635== Conditional jump or move depends on uninitialised value(s)
==20635== at 0x49ECF4: get_name (dnsproxy.c:867)
==20635== by 0x49F3F7: parse_response (dnsproxy.c:1096)
==20635== by 0x49FD40: cache_update (dnsproxy.c:1410)
==20635== by 0x4A0FF3: forward_dns_reply (dnsproxy.c:1803)
==20635== by 0x4A15D9: udp_server_event (dnsproxy.c:1912)
==20635== by 0x3331E47A54: g_main_context_dispatch (gmain.c:2715)
==20635== by 0x3331E47D87: g_main_context_iterate.isra.24 (gmain.c:3290)
==20635== by 0x3331E48181: g_main_loop_run (gmain.c:3484)
==20635== by 0x44B600: main (main.c:670)
|
|
|
|
Updated PreferredTechnologies description.
Added SingleConnectedTechnology, AllowedTetheringTechnologies and
PersistentTetheringMode descriptions.
|
|
|
|
The received IP address was not freed.
|
|
If the desired option was last one in the message, then it was
lost because the remaining data calculation was wrong.
|
|
Make sure we do not create a new transaction id for a message
when it needs to be retransmitted.
|
|
As requested in RFC 3315 chapter 15.1, a client MUST leave
the transaction id unchanged in retransmissions of a message.
|
|
|
|
Print transaction id of sent and received messages so that it is
easier to match the packets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If user has disabled dnsproxy with -r option, then fallback to
user specified nameservers instead of using the Google one.
|
|
The listener_table can be NULL if we have started connman with -r
option. Because we return < 0 value to caller in this case,
the caller, e.g. the tethering code, has a possibility to change
its functionality, e.g. the tethering code can fall back to some
other DNS servers.
|
|
If the user has enabled persistent tethering mode in main.conf, then
try to activate tethering when technology is re-enabled, or we are
returning from offline mode, or after the device has rebooted.
|
|
|