You put that command inside the file /etc/rc.local that runs at every boot but before the exit 0 in this file.
Another solution can be to only release your ip address and request a new one by sending signals tho the dhcp client daemon running for this interface.
@linksys54glnew Can you try the following procedure for your wireless link?
determine the interface which has the ip lease with the shell command ifconfig, for example: eth0.2
Then release th ip address by sending the USR2 signal to the dhcp client with (use your determined interface name):
kill -SIGUSR2 $(cat /var/run/udhcpc-eth0.2.pid)
Your ip address should be gone on the interface, check with ifconfig.
Wait some time (e.g. 5 seconds) and request a new ip with sending the signal USR1 to the dhcp client:
kill -SIGUSR1 $(cat /var/run/udhcpc-eth0.2.pid)
Your should have a new ip address on the interface, check with ifconfig.
If this works for your connection, you don´t have to restart your other interfaces.
Probably you will get the same ip address if the dhcp server doesn´t allow a manual release of the ip address.
1 Like
an other question,
if i logged in the router on the client,
the router becames an ip from the client,
did the router send an ip question to the client after some time?
because it also could be,
that the router send a question to the client,
becomes no answer from it and cancelled the conection. so not the client cancel the conection, the router to this from himself??.. is this possible?
and also i have looked in the system-logs,
I have sites of sites
CTRL-EVENT-BEACON-LOSS
CTRL-EVENT-BEACON-LOSS
CTRL-EVENT-BEACON-LOSS
what could that be??
I don't understand your question...
What client and which question?
1 Like
hi juppin,
i have updatet the router yesterday to 19.07rc,
know it locks stable.
at 18.06 always the router sends a dhcp question to the client and wait for the answer, if they givn't them one the router stops the connection to the client.
today i testet the "new" version and it locks,
that now this is better configured in the basic network dhcp system.
but for sure i give you a feedback the next days,
maybe it runs good, if not i must build a script as you show me.
at first thanks a lot for the fast response,
i give you a feedback, best regards
so now the problem is actually,
it drops down the internet.
the router has send the dhcp-question;
: sending renew to 10.255.255.254
Sat Nov 30 19:27:50 2019 daemon.notice netifd: wwan2 (3716): udhcpc: sending renew to 10.255.255.254
Sat Nov 30 19:35:20 2019 daemon.notice netifd: wwan2 (3716): udhcpc: sending renew to 10.255.255.254
Sat Nov 30 19:39:05 2019 daemon.notice netifd: wwan2 (3716): udhcpc: sending renew to 10.255.255.254
Sat Nov 30 19:40:57 2019 daemon.notice netifd: wwan2 (3716): udhcpc: sending renew to 10.255.255.254
Sat Nov 30 19:41:53 2019 daemon.notice netifd: wwan2 (3716): udhcpc: sending renew to 0.0.0.0
Sat Nov 30 19:41:53 2019 daemon.notice netifd: wwan2 (3716): udhcpc: lease of my ip(i have clean that from text) obtained, lease time 3600
then....
Reason: 15=4WAY_HANDSHAKE_TIMEOUT
and it losts the i-net connection,
until i will manually press by the wifi client; disaple and enable then a view secouds later, all is ok.
so maybe someone can help me with this problem,
thanks
This message comes from the hostapd daemon, right?
The 4 way handshake is a essential part of the connection establishment for your wifi connection and I think your DHCP renew request does also timeout due to a weak wifi signal.
Do you have a weak wifi signal on your client connection?
Probably you need a better place for your wifi station or a directed antenna.
yes handshake is from hostapd.
wifi-signal is good it has 65% from the client.
and yes the dhcp request to the client,
comes often from the router, i think 6x from the router
before the connection crash
yes and again,
after 3600 the router requests as client,
and sometimes the acces point who i will access,
do not send an answer... i will be crazy but ok,
i must find a solution, it is an hotspot,
so i cannat config that shi....
Now i really need a solution,
so that the router dont send a request.
or i connect all 60min via script,
but i think it is a little bit buggy because the router has the master on the same wifichip.
maybe someone,
had an solution,
thanks