Tag Info

New answers tagged

-1

To have correctly working an ethernet device need the exact MAC address that hetzner give in the control pannel, therefore add it to ethernet from the xencenter network settings.


0

Use of a /32 netmask (either statically or via DHCP) seems to be an increasingly common default configuration applied by VPS providers* to Linux hosts — presumably to reduce broadcast traffic. I'm not certain whether such a configuration would work as intended on a Windows-based host, but a working manual configuration of a Linux host looks something like ...


1

You have 2 options: Use a bigger subnet (e.g. instead of /24 use a /23) Add another VLAN and configure the router/firewall to forward required traffic. Solution 1: You will need to change the network mask on all machines connected on the current VLAN. Because you are using only a slice of 192.168.0.0/16, you can grow your VLAN to have a maximum of 65534 ...


-2

You should go and re-read the wikipedia article for subnetting. A basic grasp of IPv4 addresses will help you more with your homework than just copying answers off here. You didn't explicitly state it in the question, but I'll assume you have a /24 network and want to divide it into one 1x /25 and 2x /26 So you end up with 134.7.1.0/25, 134.7.1.128/26 and ...


0

I have found the solution to my problem. I added a virtual IP alias within pfSense with an IP address that matches my gateway in the sonic wall (with /26 mask bit). I then added the proper firewall rules on the pfSense and SonicWALL box (Thanks Jenny D for your comment on the OP about this). Finally, I added proper outbound NAT rules on pfSense. NAT Rule ...


0

To sum it up: Install and configure DNS on one of the Vnet servers: https://technet.microsoft.com/en-us/library/cc730921.aspx Assign an internal static IP to the VM you installed DNS on: https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-private-ip/ Configure the Vnet to use the DNS IP addresses for name ...


3

They are 50% in the same network :) IP1 can access hosts 10.150.1.1-10.150.1.6 directly, and IP2 can access hosts 10.150.1.1-10.150.1.30 directly. IP1 cannot access host 10.150.1.7 at all, because it is the broadcast address for that network. In practice, this kind of configuration doesn't work, and one of the host's netmasks must be fixed to match the ...


0

I'd like to know... Would this work? Yes Did I use the right amount of routers? Subjective, as you could do the same thing with a single router Did I configure everything correctly? Again a little subjective, if you could explain why you are splitting them like this it would help more. Plus, do I need to configure static routing ...


1

One possible solution: Add a second(even a third) NIC card to your controlling PC, then configure with the other IP addresses to connect directly with the other routers. Magic packets will then pass out the associated NIC based on destination IP in the WOL command (IP, MAC, subnet, port).



Top 50 recent answers are included