Posts made by PJB1983

@sebastian-roth thx for the support!

@george1421 that did the trick!
Thx for the support!

@george1421 THX!

@sebastian-roth can you see something in the file attached?

N_EKS - appliance_MX-MX64 N_EKS_IF-LAN.pcap

@george1421 then i’ll get

18:47:45.022319 IP 192.168.5.121.2070 > 95.0.0.85.69: 30 RRQ “undionly.kpxe” octet tsize 0
18:47:45.061293 IP 192.168.5.121.2071 > 95.0.0.85.69: 35 RRQ “undionly.kpxe” octet blksize 1456

@george1421 the answer from Meraki Support:

The two sites are using MTU 1432 size due to protocol overhead. This is the recommended value. The best option here is to adjust the MTU of the PXE. Increasing the MTU would result in an MTU greater than 1500 which may lead to fragmentation. Also, Meraki does not support Jumbo size MTU. Should you require further assistance, please do not hesitate to reach out to us asap.

@george1421 i’ve changed the block size and rebooted the device.
But that did not solve the problem.
If i ask meraki support to increase the MTU for the site-to-site VPN, will that solve it?

@george1421

Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04

@sebastian-roth thx for your reply, but i doesn’t have a CLI on the Meraki Firewall. I have to contact support i guess.

@george1421 the max MTU size is 1404.
I’ve installed the FOG server on a Linux Ubuntu.

@george1421 thx for your reply.
the support on this forum is incredible.

I’ve done a ping with 1300 packet size -> No problem
1500 packet size -> Packet need to be fragmented but DF set.

I’ll search on my Meraki security appliance to increase the packet size.
Does this have some consequences for my network performance?

@sebastian-roth hi thx for your reply.
the support on this forum is incredible.

I’ve done a ping with 1300 packet size -> No problem
1500 packet size -> Packet need to be fragmented but DF set.

I’ll search on my Meraki security appliance to increase the packet size.
Does this have some consequences for my network performance?

@george1421

I think the UDP request had a bad length?
What can i do about it?

reading from file -, link-type EN10MB (Ethernet)
13:02:42.546737 ARP, Request who-has 192.168.5.121 tell 192.168.5.1, length 28
13:02:42.547604 ARP, Reply 192.168.5.121 is-at 00:15:5d:00:fc:09, length 46
13:02:47.831592 IP 95.0.0.85.59214 > 192.168.5.121.2071: UDP, bad length 1460 > 1400
13:02:47.831592 IP 95.0.0.85 > 192.168.5.121: ip-proto-17
13:02:57.548243 ARP, Request who-has 192.168.5.121 tell 192.168.5.1, length 28
13:03:04.618441 ARP, Request who-has 192.168.5.1 tell 192.168.5.121, length 46
13:03:04.618441 ARP, Reply 192.168.5.1 is-at e0:55:3d:8f:6e:50, length 28
13:03:04.625881 IP 192.168.5.121.2070 > 95.0.0.85.69: 30 RRQ “undionly.kpxe” octet tsize 0
13:03:04.650645 IP 95.0.0.85.48771 > 192.168.5.121.2070: UDP, length 14
13:03:04.651880 IP 192.168.5.121.2070 > 95.0.0.85.48771: UDP, length 17
13:03:04.667062 IP 192.168.5.121.2071 > 95.0.0.85.69: 35 RRQ “undionly.kpxe” octet blksize 1456
13:03:04.692814 IP 95.0.0.85.52966 > 192.168.5.121.2071: UDP, length 15
13:03:04.693826 IP 192.168.5.121.2071 > 95.0.0.85.52966: UDP, length 4
13:03:04.718623 IP 95.0.0.85.52966 > 192.168.5.121.2071: UDP, bad length 1460 > 1400
13:03:04.718623 IP 95.0.0.85 > 192.168.5.121: ip-proto-17
13:03:05.719924 IP 95.0.0.85.52966 > 192.168.5.121.2071: UDP, bad length 1460 > 1400
13:03:05.719924 IP 95.0.0.85 > 192.168.5.121: ip-proto-17
13:03:07.721833 IP 95.0.0.85.52966 > 192.168.5.121.2071: UDP, bad length 1460 > 1400
13:03:07.721833 IP 95.0.0.85 > 192.168.5.121: ip-proto-17
13:03:11.726666 IP 95.0.0.85.52966 > 192.168.5.121.2071: UDP, bad length 1460 > 1400
13:03:11.726666 IP 95.0.0.85 > 192.168.5.121: ip-proto-17
13:03:12.550408 ARP, Request who-has 192.168.5.121 tell 192.168.5.1, length 28
13:03:12.551594 ARP, Reply 192.168.5.121 is-at 00:15:5d:00:fc:09, length 46
13:03:19.731344 IP 95.0.0.85.52966 > 192.168.5.121.2071: UDP, bad length 1460 > 1400
13:03:19.731344 IP 95.0.0.85 > 192.168.5.121: ip-proto-17
13:03:27.552009 ARP, Request who-has 192.168.5.121 tell 192.168.5.1, length 28
13:03:27.553072 ARP, Reply 192.168.5.121 is-at 00:15:5d:00:fc:09, length 46

@george1421 thx for the reply.
I’ll run wireshark asap and send the link to the pcap file.

@sebastian-roth thx for your reply.
The Meraki security appliance provide ip addresses and a gateway for that perticular site (school).

Hi,

I’m using the fog server for twee weeks now. Everything works perfect in the same subnet. Now I want to deploy an image to a remote client.

All my locations are connected to each other with site-tot-site VPN of Meraki. I use the built-in DHCP service from the Meraki security appliane. I’ve set the boot next server and tftp option (66) value to the IP address of the Ubuntu FOG server. i’ve defined also the boot filename: undionly.kpxe

I can ping the FOG server from the remote client.
I get this error:
PXE-32: TFTP open Timeout

What am I overlooking?

thx