China 
Africa 
Explore chapters and articles related to this topic
High-Performance Switch/Routers
Published in James Aweya, Designing Switch/Routers, 2023
At the SSH client side, an IP address, localhost, or any other host name can be used to specify the host to be connected to [RFC4254]. A company may use Remote SSH Forwarding to provide a user outside its network, access to an internal web server, or expose an internal web service to outside users and the public Internet (e.g., an employee working from home). It should be noted that this feature may also be exploited by malicious users or attackers.Configuring Remote SSH Port Forwarding: When a connection is received on a port for which a party has requested remote forwarding, a channel is opened to be used to forward that port to the other side using a message indicating the following: SSH_MSG_CHANNEL_OPEN, “forwarded-tcpip”, the sender’s channel number, initial data window size, maximum packet size, the IP address and port on the SSH server, the IP address (or hostname) and port of the destination machine, and the remote SSH user and SSH server IP address.
LabVIEW Features
Published in Rick Bitter, Taqi Mohiuddin, Matt Nawrocki, LabVIEW™ Advanced Programming Techniques, 2017
Rick Bitter, Taqi Mohiuddin, Matt Nawrocki
Viewing the front panel of a VI with a Web browser is a straightforward procedure. Before you can view the front panel, make sure the Web server has been enabled and the VI has been opened. The VI must be loaded in memory before anyone can look at it from the Web. Then, from any machine that is allowed access to the Web server, type the URL of the machine running the Web server into the browser. To the end of the URL add the VI name with the html extension. Insert a plus sign or % 20 in the URL to represent the spaces in your VI name. For example, to monitor a VI named “test program.vi” you would enter in the following URL into your browser: http://111.111.111.11/test/program.html. This assumes the IP address of the Web server is 111.111.111.11. If you are trying to view a VI on the local machine you could use “localhost” instead of the IP address. Depending on the company you are working for, and your network specifics, the system administrator may need to set permissions or perform other system administrator intervention.
The Switch/Router
Published in James Aweya, Switch/Router Architectures, 2019
IPv4 specifies the address range 127.0.0.0/8 (127.0.0.1 through 127.255.255.254) for loopback addresses. This allows any information that an entity within the device sends on the loopback address to be addressed directly (turned back) to the same device. The most commonly used IP address for a loopback interface is IPv4 address 127.0.0.1 and IPv6 address ::1. Also, the standard domain name corresponding to the loopback address is “localhost”.
Simulated-based methodology for the interface configuration of cyber-physical production systems
Published in International Journal of Production Research, 2021
Abderrahim Ait-Alla, Markus Kreutz, Daniel Rippel, Michael Lütjen, Michael Freitag
Moreover, the results show that increasing the number of sensors also increases the number of received messages. While this result has been expected, it indicates that for larger systems with many sensors, the reliability of the communication technology has to be considered. In the case of this simulation study, both instances of AnyLogic were executed on the same computer using the loopback interface (localhost) for the TCP/IP connection. Nevertheless, during the tests, it became apparent that increasing the simulation speed beyond a certain threshold resulted in lost messages, as the interface was not capable of handling the quick succession of messages for larger scenarios. The current implementation allows executing both instances on different computers to evaluate possible communication technologies. This becomes important in case of deployment of the proposed changes, as different technologies could be available, again at different costs.
State behavior analysis in validating the web service framework
Published in International Journal of Computers and Applications, 2021
From the constructed model we can experiment the WS using all the states to interpret the behaviors for analysis. This model is suitable for REST and RESTful services. Initially this model tested with localhost with the single user. Then the model is tested with multiple users to generate service log for a large size of services. If the service is too small or too large is not the case for the modeling. Any size it could be applicable in the state machine representation model. The log is captured for the duration of regular and long intervals. The log has features for handling restful and restless category namely, analysis of the state behavior like the status of the state, time spent on each state, observing states with a threshold to make the service alerts for warning, critical or liveliness. Then we created ejobfair service and deployed in localhost to learn the behaviors. We carried the same ejobservice for detailed work to analyze state behaviors in the cloud environment. The data set primarily consists of job posting and recruiter details. The list of services built for the Applicant and the Recruiter are ApplicantRegister-ApplicantLogin-RecruiterRegister-RecruiterLogin-PostJobs-SearchJob-AppliedJobs-SearchApplicant-ScheduledInterview-InterviewStatus. The data set generated is a set of logs of user request and actions for different WS. Their stamp time is also recorded for analysis.
CKshare: secured cloud-based knowledge-sharing blockchain for injection mold redesign
Published in Enterprise Information Systems, 2019
Zhi Li, Xinlai Liu, W. M. Wang, Ali Vatankhah Barenji, George Q. Huang
Furthermore, to achieve the desired functionality, a rule-based smart contract (price, payment and date) was developed and deployed for dictating the rules of the platform in terms of knowledge-sharing between user and provider. The smart contact was generated with the knowledge provider data (Price, payment method, multiple uses etc.) and then transferred to the Ethereum blockchain. In the proposed platform, six nodes with a wallet address were created in Ganache, where we assumed that each wallet had 100 Ethereum tokens (ETH tokens) for transaction purposes. Notably, the number of ETH tokens to cover the Gas limit and tax for each transaction was 2,100. Localhost was used for debugging the platform. Figure 8 illustrates the transaction visualization for a user node with five provider nodes.