I am working in a company with 3 sites.
London (A) is the main site with 2 subnets separated with NAT network.
Manchester (B) basic broadband router act as DHCP and DNS for local clients
Dublin (C) Basic broadband router act as local DHCP and DNS for clients.
In Site A there are 2 networks, 1>> DHCP, DNS, Xchange Server, File Share Server, local database for access 2003, on server 2012 R2. Subnet: 192.168.16.X | 2>> DHCP, DNS, Microsoft WIM Imaging Solutions. Subnet: 192.168.1.X
Is there a way to connect site B & C to Site A so they can both be connected to both WIM network and local internal Network?
At the moment there is no solution in place. Sites are not connected.
My goal is to have the same solution for site B & C as site A
If it can be achieved by VPN, site to site tunnel or any other.
Related
I have an AWS account with a VPC in Ireland and another in Sydney, which are connected via VPC peering.
I have 2 Windows servers, one in Ireland, one in Sydney, both are in a Private Subnet. From a server in Ireland I can RDP to the server in Sydney using it's private address, therefore my VPC peer is working.
To connect to the Ireland server, I have an OpenVPN server in the public subnet which I connect the OpenVPN client on my client machine. Once connected, I can RDP to the Ireland server. All good.
I am trying to connect to the Sydney server from my client machine, using the route client --> Ireland --> VPC link --> Sydney.
I have pushed routes via my OpenVPN config which means, when I ping the Sydney server, it now goes via the VPN instead of my home router but times out after the first hop.
C:\Windows\system32>tracert -d 10.150.224.50
Tracing route to 10.150.224.50 over a maximum of 30 hops
1 26 ms 25 ms 25 ms 10.41.0.1
2 * * * Request timed out.
I am at a loss of what happens after that hop, there is also a possibility that I have some config missing in OpenVPN. Any help / guidance would be greatly appreciated!
Unfortunately you cannot do what you want in AWS.
This is an invalid configuration, as per AWS docs:
Edge to edge routing through a gateway or private connection
If either VPC in a peering relationship has one of the following connections, you cannot extend the peering relationship to that connection:
A VPN connection or an AWS Direct Connect connection to a corporate network
An internet connection through an internet gateway
An internet connection in a private subnet through a NAT device
A gateway VPC endpoint to an AWS service; for example, an endpoint to Amazon S3.
For example, if VPC A and VPC B are peered, and VPC A has any of these connections, then instances in VPC B cannot use the connection to access resources on the other side of the connection. Similarly, resources on the other side of a connection cannot use the connection to access VPC B.
You have two options:
Configure your OpenVPN server to do NATing instead of routing and therefore "hide" the real source IP of the connection
Create another VPN connection with another OpenVPN server in Sydney region
I have a local Linux machine (L), with a network interface (eth0) connected to (currently) only one device (D).
L/eth0 only has an ipv6 link local address.
D also only has an ipv6 link local address.
Client software on L discovers D's link local address by sending a custom multicast packet over eth0. The response contain the device link local address as well as some configuration information. From there it communicates with the device using various UDP or TCP port.
My goal is to be able to use the device from a remote machine (R). The remote machine being most likely a Linux docker container running on some host - although it could be a native macOS or other.
That means running both the discovery protocol and communicate with the device. I definitely cannot modify software on the device, and cannot modify most of the client software running on the local Linux or remote machine (Limited modification could possibly be requested)
My idea was to somehow create a virtual interface on the remote machine, that would remotely be bridged to the the local machine, so that the multicast discovery works from the remote, and so that I can just connect to D link local address from the remote.
I'm not sure which tool(s) I should be using.
I'm googling various things about VPN and tunnel, TUN/TAP interfaces, bridges, VETH, VLAN, etc... but I'm having trouble connecting the dots here... I have no budget for this, so I'm looking for open source tools, or just something I can cobble up together with common tools.
Thanks
Goal:
My goal is to setup a web server and an ANS server for my website at home where it is publicly available. I can access the webpage through my public IP address outside of my network, but can't figure out how to bind that address with the domain name I purchased on namecheap.com.
What I'm Running:
I'm using
VirtualBox 6.0.4
; 3 guest machines that are running Ubuntu 18.10 (for a primary and secondary dns server and a web server)
; my host machine is running Windows 10
; bind9 for ANS (DNS) and apache2 as a web server
; and my domain name was purchased at namecheap.com
What I've Done:
I've followed the instructions on this page to setup the DNS servers : https://www.digitalocean.com/community/tutorials/how-to-configure-bind-as-an-authoritative-only-dns-server-on-ubuntu-14-04
The network setting on VirtualBox(VB) is set to "bridged adapter."
On my router, I've opened (http) port 80 for the IP address of my apache web server and (tcp/udp) port 53 for the IP address of my primary DNS server.
My questions:
I'm unclear as to which IP addresses to put in at namecheap.com under "custom DNS"?? The IP addresses of my DNS servers in VB or the IP address of the DNS servers that is provided by my router? If it's the latter, then how do I add them to the named.conf files?
Considering that the public IP address of your router does not change, you should do port forwarding in the router for your VB to be accessed from the internet, then use your router's public IP to configure in namecheap.
I have a small local network, with the following devices: a router , a Dell laptop running Ubuntu 16.04 LTS as my server, and another HP laptop to test access.
My IP addresses look like this:
router: 192.168.0.1
server: 192.168.0.101
laptop: 192.168.0.100
I have successfully setup LAMP and have one small page (/var/www/html/index.html) with one picture. I can't access this from my HP laptop by entering 192.168.0.101 into Firefox or Chrome.
In order to access your server you have to make it publicly so I will describe the steps required to do it:
Login to your router, search for Port Forwarding section and forward the port 80(HTTP Port) to 192.168.0.101(Your Web Server). You can find a guide for Port Forwarding after selecting your router model here : https://portforward.com/router.htm
Access your webserver by your external Ip. http://yourexternalip
(Optional) If you have dynamic Ip, you can set a Dynamic DNS to create a domain name that will always point to your webserver even your Ip will change after a router reboot or something like that. You can read this guide for setting up a DDNS: https://www.howtogeek.com/66438/how-to-easily-access-your-home-network-from-anywhere-with-ddns/
i am trying to add multi ssl sites to my azure vm machine, but i am missing something.
i tried "Add-AzureVirtualIP" ,"New-AzureReservedIP","Set-AzureReservedIPAssociation","Set-AzurePublicIP"
i can see the new ip in powershell , but when i add the bindings in the iis dialog box, its doesn't work
on my own servers i usually added the new IPs that my isp provided withen the network ip4 properties and it was so easy, now i have no internal ips nor external port forword working
any ideas