Hallo,
I wonder how to switch between DHCP and static IP. I found an old post,
and I wonder How this switch can be done with lwip 2.0.2.
I simply call
netifapi_dhcp_release(netif);
netifapi_dhcp_stop(netif);
// set addresses in ipaddr, netmask, gw
netifapi_netif_set_addr(netif, &ipaddr, &ip
On 7/10/2017 5:23 AM, Axel Lin wrote:
I got a dump of the data when bad fcs happened. (This time is "IP"
rather than "LCP")
214528b56a4000ee06847834c111ea0a0002420050de7add4c7bd91377a8bd50107980ef41279f7e21450001aeb56b4000ee0682f134c111ea0a0002420050de7add4c7bd91377a8bd50187980c658485
Sequence number is losted somewhere... I put l2tp->our_ns = l2tp->peer_nr
at the start of pppol2tp_input and now it works without interruptions. But
still no any ping through VPN server from Windows client to the device with
LwIP, only to static ip of the device.
--
View this message in contex
But if server requests with ns=2, nr=4, why LwIP responds with ns=3, nr=3?
nsnr
Data input: c8 02 00 14 d0 b3 00 00 [00 02] [00 04] 80 08 00 00 00 00 00 06
UDP send: c8 02 00 0c 76 c4 00 00 [00 03] [00 03]
--
View this message
No, sorry, it asks. If "Hello" is:
pppol2tp: input packet, len=20, tunnel=53427, session=0, ns=2, nr=4
Data input: c8 02 00 14 d0 b3 00 00 00 02 00 04 80 08 00 00 00 00 00 06
than in pppol2tp_udp_send:
UDP send: c8 02 00 0c 76 c4 00 00 00 03 00 03
--
View this message in context:
http://lwip
Hi Max,
I hope I am not confusing you or making an error here.
As far as I know DHCP client is handled almost completely by LwIP.
You should not worry about timers etc...
I have attached my DHCP task, take a look and I hope this helps...
This code is running with LwIP 1.41
BR,
Noam.
-Ori
That strange packed which has no reply from LwIP has a view:
pppol2tp: input packet, len=20, tunnel=53427, session=0, ns=2, nr=4
Data input: c8 02 00 14 d0 b3 00 00 00 02 00 04 80 08 00 00 00 00 00 06
We connected to VPN-server using Windows and found almost the same message:
c8
Hallo,
I have some questions about dhcp behaviour:
- Do I have to call the functions dhcp_coarse_tmr() and
dhcp_coarse_tmr() explicitly?
I have this doubt because I have seen that these functions are already
being declared as
timer callbacks in file timeout.c
- if my dhcp server has 10s as
