realmar / dhcpv6-client-android

Get an IPv6 address using DHCPv6. Be future-proof.

realmar

Is this a secret?

dhcpv6-client-android's Issues

This app is very unreliable on Nougat

Almost every time I connected to Wi-Fi I need to start this app and start dhcp6c manually or it doesn't get a IPv6 address.

I'm suspecting that the issue is using a BroadcastReceiver for network changes is deprecated.

App stopped working after system update

I just updated to 7.1.2 and I can't get this to work any more.

xiaomi6 can't install

Every time, I try to click install button, it show
"retry?
couldn't cope files, please try again or open an issue……“

the rom version is miui 9 7.9.8
android version is 7.1.1

Feature request: systemless install

Would you pleaase consider packing this as a Magisk module?

Publish on F-Droid

Please consider to publish the android app on F-Droid, the most popular repository for android FOSS applications.
More information is available on the F-Droid documentation.

Missing http://realmar.daduke.org/dhcp/dhcpv6_base.zip

This and http://realmar.daduke.org/dhcp/dhcpv6_update.zip are giving 404 not found errors. Any chance of making them available somewhere else?

Old process of 'dhcp6c' prevents getting a new IPv6 address`

Sometimes the client is not working, even if I perform a 'manually invoke'.
I tried executing dhcp6c manually in terminal with command dhcp6c -c /etc/wide-dhcpv6/dhcp6c.conf -dDf wlan0 ,
and I got this error

dhcp6_ctl_init: bind(control sock): Address already in use
client6_init: failed to initialize control channel

If I kill the old process with command busybox killall dhcp6c , it will work.

So the workaround may be killing dhcp6c process before executing a new one.

Unable to Install Client - Retry

hey @realmar I know you aren't actively maintaining this project anymore, but I was hoping you could help me out with this issue really quickly. Is there a folder dir I can drop the files in manually to get this app working? I'm on an Essential PH-1 Running Oreo with A/B if that matters

Cannot mount /system as RW

Issue received via email.

Quoting from email:

---

Good day!

Your app tries to install files into /system/... which is not always possible (on some phones such my alcatel idol 6055k /system is mounted RO even on root, and I have troubles to mount it RW)

So can binary files to be install in other path than /system? If not - of course, I can place it into /system manually, but it is much harder to do.

Thank you

This app doesn't work until I adb shell into my device and run dhcp6c wlan0 as root manually

I have a problem

I have successfully rooted my phone, and the software DHCPv6 has also successfully been installed.My wifi has ipv6 adress which can be verified on my computer.
However, the DHCPv6 only show a ipv6 with fe at the first, and can not get the number sequence ,so I can't use it.
so, I want to ask what's wrong with it and how can I solve it ？

Crash

05-12 02:39:17.596  1494  1494 D AndroidRuntime: Shutting down VM
05-12 02:39:17.597  1494  1494 E AndroidRuntime: FATAL EXCEPTION: main
05-12 02:39:17.597  1494  1494 E AndroidRuntime: Process: org.daduke.realmar.dhcpv6client, PID: 1494
05-12 02:39:17.597  1494  1494 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'android.view.View android.view.View.findViewById(int)' on a null object reference
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at org.daduke.realmar.dhcpv6client.MainFragment.get_ip_addresses(MainFragment.java:87)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at org.daduke.realmar.dhcpv6client.MainFragment$2.onReceive(MainFragment.java:78)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at android.support.v4.content.LocalBroadcastManager.executePendingBroadcasts(LocalBroadcastManager.java:297)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at android.support.v4.content.LocalBroadcastManager.access$000(LocalBroadcastManager.java:46)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at android.support.v4.content.LocalBroadcastManager$1.handleMessage(LocalBroadcastManager.java:116)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6178)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
05-12 02:39:17.597  1494  1494 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)

Don't delete the dhcp6c_duid file when trying to signal the dhcp client that it should get a new ipv6 address

According to Section 9 from RFC 3315 "The DUID is designed to be unique across all DHCP clients and servers, and stable for any specific client or server - that is, the DUID used by a client or server SHOULD NOT change over time if at all possible; for example, a device's DUID should not change as a result of a change in the device's network hardware"

According to tour comment from September 26th :

To acquire an ipv6 address the app checks if the dhcp6c process is running, if that's the case it will use the "communicator binary" dhcp6ctl to signal the dhcp client that it should get a new ipv6 address.

Although this does not always work, therefore the app first deletes /data/misc/dhcp/dhcp6c_duid in order for the dhcp client to get a new address.

Deleting dhcp6c_duid forces the dhcpv6 client to generate a new DUID.