TFTP Problem with Wan MPLS Access

Post a reply

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: TFTP Problem with Wan MPLS Access

Re: TFTP Problem with Wan MPLS Access

by aka » Fri Mar 03, 2017 12:36 pm

We'll do it, thanks.

Re: TFTP Problem with Wan MPLS Access

by nicodep » Wed Feb 08, 2017 8:21 pm

nicodep wrote:Could include in the next version the option boot via HTTP in "Boot SD card" maker
This function run great but i need to manually modify this option on each PI3
Hi Aka, just to remember this tips for your next version !

Thk

;)

Re: TFTP Problem with Wan MPLS Access

by nicodep » Sun Dec 18, 2016 9:12 pm

Hello Aka,

Could include in the next version the option boot via HTTP in "Boot SD card" maker
This function run great but i need to manually modify this option on each PI3

Thk !

;)

Re: TFTP Problem with Wan MPLS Access

by J1mbo » Wed Nov 09, 2016 2:01 pm

Should be faster at remote sites too as there is no windowing in TFTP. Good job :)

Re: TFTP Problem with Wan MPLS Access

by aka » Wed Nov 09, 2016 2:33 am

Official 5.4.54 released.

Re: TFTP Problem with Wan MPLS Access

by nicodep » Mon Oct 24, 2016 1:47 pm

Wonderfull
it works great !

Is this a test version ? or official soon ?

Great job Aka
;)

Re: TFTP Problem with Wan MPLS Access

by aka » Mon Oct 24, 2016 1:22 am

Please, try: http://pxe.ru/files/testing/201610240221.zip
Untitled.png
Untitled.png (10.84 KiB) Viewed 10617 times

Re: TFTP Problem with Wan MPLS Access

by nicodep » Mon Oct 17, 2016 11:37 am

Hi Aka,

It's really not possible to connect PI3 in HTTP mode to download config from Wtware server ?
Because impossible to run with TFTP protocol in my Wlan

;)

Re: TFTP Problem with Wan MPLS Access

by aka » Fri Sep 30, 2016 1:30 pm

1. You can reduce mtu by 026 DHCP option.
2. I do not think it's MTU. It's related to IP ports, or service fields. Error packet (number 6581 in "Capture1 wan KO.pcapng") passed to WTware. TFTP server sent it from 69 port. OACK packets (3817, 3814 e.t.c) from port 57416 with length less then 100 bytes did not pass to WTware.

Re: How to distinct

by nicodep » Thu Sep 29, 2016 5:43 pm

The problem seems to be the MTU !
In my MPLS network SFR, the MTU is limited to 978 (without overload)

Raspberry strength and customer size to 1360 ...
Can you reduce the size of packets to the client ? 950 max

;)

Re: How to distinct

by aka » Thu Sep 29, 2016 4:17 pm

I have no ideas :( Both interactions look similar.
Can you make the same sniffs in 192.168.63 network?

Re: How to distinct

by nicodep » Thu Sep 29, 2016 1:41 pm

Re: How to distinct

by aka » Thu Sep 29, 2016 1:05 pm

I see unsuccessfull TFTP communication in sniff.
I don't see successfull TFTP communitation with different TFTP client (TFTP32) on the same site as the Raspberry.

Re: How to distinct

by nicodep » Thu Sep 29, 2016 12:22 pm

aka wrote:Can you sniff both communications (WTware and TFTPD32) with Wireshark?
Hi,

See the Wireshark log : http://www.nicodep.net/Capture1_wan_KO.zip

And the tracert from Wtware server to PI3

tracert 192.168.63.41
1 <1 ms <1 ms <1 ms 192.168.1.254
2 <1 ms <1 ms <1 ms 10.10.10.250
3 1 ms 1 ms 1 ms 101.0.79.86.rev.sfr.net [86.79.0.101]
4 24 ms 14 ms 14 ms 53.0.79.86.rev.sfr.net [86.79.0.53]
5 121 ms 50 ms 42 ms 192.168.63.41

;)

Re: How to distinct

by aka » Thu Sep 29, 2016 9:21 am

Alon wrote:Waiting eagerly for the remote SD card update functionality to be implemented.
It will. HTTPS in embedded web server was done for remote update.

Top