i am developing a JavaME application which dynamically assign public ip address given by the server? how to assign public ip to mobile phone using JAVAME?
This looks like you want to implement a DHCP client. Perhaps you are better off with running a DHCP service for your network, in which case the details of the IP address assignment will be taken care of by the device's networking software.
JavaME does not provide any APIs for assigning IP adresses to network devices, in fact there are not many generic API sets that provide this functionality.
Related
I have seen in my ARM template that this properties is available in the virtual network gateway.
However, the documentation does not seem to explain how to use it.
What I need is to create a virtual network gateway with OpenVPN point to site (up to this point, no problem, it is really easy) BUT I need to be able to configure static IPs for the clients.
The privateIPAllocationMethod look promising but I would expect to see further configuration to describe which client gets which IP.
Any clue?
Currently, it does not support to configure static IPs for VPN clients. Every time a P2S connection goes live, the next available IP is allocated in the address range. Refer to this.
In fact, the privateIPAllocationMethod is belonged to the ipConfigurations properties
in the VirtualNetworkGatewayPropertiesFormat object. What you need is to find the VpnClientConfiguration object, obviously, there is no such attribute to support the static IPs configuration for the clients. See vpnclientconfiguration in the template and the Azure REST API.
I have a S2S VPN connection with an external party which works fine. However, they have advised that when requests are sent over the VPN tunnel to them, they want to see the request as coming from a public IP address, rather than from our private address range.
Is there a way to configure this in Azure?
For info, we are using the standard Azure VPN gateway as opposed to a third part device from the marketplace.
Thanks
David
If I am correctly understanding, they want to requests are sent over VPN via a public IP address, rather than from our private address range. I don't think it's possible since a VPN extends the virtual private network across the public network. and enables users to send and receive data across shared or public networks as if their computing devices were directly connected to the private network.
You could create a VPN tunnel between the local virtual network and Azure virtual network via S2S VPN gateway. The tunneling protocol is used to encapsulate and encrypt the data going to and from your device and the internet. You only can communicate with the Azure virtual network via the private address range if using VPN.
It is possible to register a domain name with the IP address of the wifi network to use it later in iis.
I've tried the website is only Displayed for computers That Same are connected to the WiFi network does not Appear in the other network.
It's POSSIBLE to do this, but why would you want to? Most WiFi "network" devices are Wireless Access Points and/or hubs that already have an embedded port80/443 web service. You would be pointing a domain to a pre-existing (and non-modifiable) host.
Can you be more specific about what you want to do?
I'm attempting to create a server using IIS.
I created a site. Configured the firewall. It's available in the browser as localhost(http://localhost:8555/) and static IP(http://10.12.66.79:8555/) too
But from another network like my phone. I tried accessing using the static IP but it failed. then I tried using the virtual IP then it show me the login page of my service provider.
what I can do next?
Hope you grab a computer networking book some time to study the basic concepts.
10...* is a private address your ISP gives to your server,
https://en.wikipedia.org/wiki/IP_address#Private_addresses
So that this server can be accessed by other devices on the same network.
Your phone is on another network (via Internet in most cases), so it won't be able to access your server.
To pass packets between two networks, many other devices and settings are required.
If you do want to do experiments, public cloud computing platforms are far better an option, as they can give your server public IP addresses that can be accessed anywhere.
you can change the mobile's default DNS to your system's(IIS) IP may be this could help you but it can be able to run locally only. Make sure that your site is working in your system through the static IP (http://10.12.66.79:8555/) if it is working properly then this could be the only problem change the DNS.
I would like to use my internal exchange servers for email notifications from an azure Web Role. The role is set up on the west us region. I need to allow this role, with multiple instances, access my corporate smtp server on port 25. IS there an appropriate range of IPs that I could open up on my corporate firewall, or is there a more secure option.
We have experience setting up networks in Azure as well as VPN gateways, I am not sure that this would be part of the solution as my understanding is not broad enough to see how I could implement something that would allow secure access to corporate networks while continuing to be publicly available.
Any help or direction would be appreciated.
Thanks
Your web role has a single (and fairly static) ip address of the load balancer, but this is of no use to you as the source ip address for outgoing data will be the ip address of the particular instance. You can get hold of this address, but not easily, and it is subject to change — every time an instance recycles, or is added, the ip address will change (although the incoming ip address, of the load balancer, remains static). So you can't provide instance public ip address ranges for the corporate firewall.
If you are familiar with VPNs and private networks on Azure, then that will be your simplest option. Your worker role ip addresses will still change, but the range is more predictable, and is defined by your subnet configuration. A worker role on a private network (VPN) will have both public and private ip addresses, so will be publicly accessible, but will send to a VPN ip address via the gateway.
Another option is to do some sort of smtp relay, either on a VM in Azure, or a managed hosting service, where the ip address is more static. This would require that a machine is setup, maintained, and running, but could probably be easily done on an extra small linux vm.
Your web roles will be part of an Azure Cloud Service. That cloud service is assigned a static public IP address by Azure. No matter how many roles you add/remove from the service the public IP will remain unchanged. You can set your SMTP server to only allow requests from that IP address.