Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Guidance on Destination Port Unreachable in app build enviroment

Guidance on Destination Port Unreachable in app build enviroment

ArcherThompson
Established Member

I am using ctrlX Works 1.18.1 and had been working in an app build enviroment for several weeks, I was always able to ping other devices on my host machines LAN and had internet access, then I booted it up the other day and suddenly I can not access anything even on my LAN. 

I receive the following message "From 10.0.2.2 icmp_seq=1 Destination Port Unreachable" my host can ping this device, and nothing apperent has changed and I am a bit stuck on how to trace down the issue here. 

Addtionally I created a new enviroment and faced the same issues, I then had a team member try on there computer and they seem to have the exact same issue. It would therefore appear to related to something our System admin has changed but so far we have no been able to locate what exactly is the issue. Is there anyone that could provide some guidance? 

Thank you

2 REPLIES 2

nickH
Community Moderator
Community Moderator

Hi, 

its a little bit difficult for me to reproduce your issue. 

Be aware that ping does not work by default in the App Build Environment. I use wget for example to test my internet connection. In this screenshot you can see, that ping fails but wget works. This shows you, that the Internet connection does work, even though the ping fails. 

ping fails but wget works in app build environmentping fails but wget works in app build environment

 

More details about networking with our App Build Environment and with Qemu you can find here:

I hope these information can help you resolving your issue. Let me know if you got more news on the topic. 

Nick,

Interesting I seem to recall being able to ping before, I did find yesterday that a curl command worked as does wget. My root issue is suddenly I can not connect to the datalayer on my test bench, So that is what kicked off trying to ping the device and so on. I appericiate the insight. 

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist