Quantcast
Channel: VMware Communities : Discussion List - VMware Fusion® (for Mac)
Viewing all articles
Browse latest Browse all 12061

PXE Error, pxe-e32 TFTP Open Timeout across vmnet

$
0
0

Hi All,

 

I am completely stuck as my setup has worked  for the last few weeks and has just  stopped working today.


I am running VMware Fusion 6.02 on Max OS X. I have two guest machines, the first is an Ubunutu 10.04 install that runs a dhcp and tftp server for PXE booting kernel images. The second is just a generic Ubuntu 64-bit virtual machine that PXE boots the image provided by the Ubuntu 10.04 VM.

 

I have set up a custom vmnet for the two virtual machines using the following commands:

 

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_DHCP no
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_HOSTONLY_SUBNET 192.168.0.0
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_HOSTONLY_NETMASK 255.255.255.0
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_VIRTUAL_ADAPTER yes

 

Using vmnet-sniffer on my mac and wireshark in my Ubunutu 10.04 VM I can see the packets are making it from the failing pxe booted vm to the Ubuntu 10.04 vm. The pxe boot vm successfully receives a DHCP address and then fails on tftp with PXE-E32 TFTP open timeout.

 

The packet log of this is as follows:

 

len  590 src 00:0c:29:d0:4e:26 dst ff:ff:ff:ff:ff:ff IP src 0.0.0.0         dst 255.255.255.255 UDP src port 68 dst port 67
len  342 src 00:0c:29:f8:7c:77 dst ff:ff:ff:ff:ff:ff IP src 192.168.0.1     dst 255.255.255.255 UDP src port 67 dst port 68
len  590 src 00:0c:29:d0:4e:26 dst ff:ff:ff:ff:ff:ff IP src 0.0.0.0         dst 255.255.255.255 UDP src port 68 dst port 67
len  342 src 00:0c:29:f8:7c:77 dst ff:ff:ff:ff:ff:ff IP src 192.168.0.1     dst 255.255.255.255 UDP src port 67 dst port 68
len   42 src 00:0c:29:d0:4e:26 dst ff:ff:ff:ff:ff:ff ARP sender 00:0c:29:d0:4e:26 192.168.0.101   target 00:00:00:00:00:00 192.168.0.1     ARP request
len   42 src 00:50:56:c0:00:06 dst 00:0c:29:d0:4e:26 ARP sender 00:50:56:c0:00:06 192.168.0.1     target 00:0c:29:d0:4e:26 192.168.0.101   ARP reply
len   42 src 00:0c:29:f8:7c:77 dst 00:0c:29:d0:4e:26 ARP sender 00:0c:29:f8:7c:77 192.168.0.1     target 00:0c:29:d0:4e:26 192.168.0.101   ARP reply
len   69 src 00:0c:29:d0:4e:26 dst 00:50:56:c0:00:06 IP src 192.168.0.101   dst 192.168.0.1     UDP src port 2070 dst port 69
len   70 src 00:50:56:c0:00:06 dst 00:0c:29:d0:4e:26 IP src 192.168.0.1     dst 192.168.0.101   ICMP unknown type 3
len   69 src 00:0c:29:d0:4e:26 dst 00:50:56:c0:00:06 IP src 192.168.0.101   dst 192.168.0.1     UDP src port 2071 dst port 69
len   70 src 00:50:56:c0:00:06 dst 00:0c:29:d0:4e:26 IP src 192.168.0.1     dst 192.168.0.101   ICMP unknown type 3

 

So, I investigated the ICMP unknown type 3 error, which is Destination Unreachable (Port Unreachable)

 

a nmap -sU localhost produces the following

 

PORT     STATE            SERVICE
67/udp   open|filtered    dhcps
69/udp   open|filtered    tftp
111/udp  open|filtered    rpcbind
2049/udp open|filtered   nfs
5353/udp open|filtered   zeroconf

 

Also, a  netstat -nulp | grep '69' further confirms the tftp daemon running
4:udp        0      0 0.0.0.0:69              0.0.0.0:*                           4159/in.tftpd  

 

The only major changes to the system were an install of vmware tools on the Ubuntu 10.04 vm last week.

 

I know the configurations for the servers are correct on the Ubuntu 10.04 VM. As I can set the network adapter to the thunderbolt Ethernet, which is able to push out DHCP addresses and PXE images to a physical machine connected to the mac via a switch. PXE boot is only failing when going across the custom vmnet to the other vm.

 

Any help or suggestions would be greatly appreciated.


Viewing all articles
Browse latest Browse all 12061

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>