New answers tagged subnet
The Ethernet address on the frame is the MAC address of the router (layer 2). The payload of the ethernet frame, like an IP packet (layer 3) still contains the original destination IP address. The router will create a new frame frame with the MAC address of the destination computer containing the original payload.
Actually, the answer wasn't as messy as I expected but it's not exactly obvious. It was clear that naively adding the route + the second gateway wasn't working (nor should it work - you can't have multiple gateways in this way): sudo ip route add X.Y.Z.64/27 via X.Y.Z.65 dev eth1 RTNETLINK answers: File exists A friend pointed me to a page describing how ...
Well there are some things you can test. First and for all, in your topic you write about vlans. Is the server connected to a switch? If so, are the ports correctly configured in the right VLAN (access port?) etc... Is your server a virtual machine? Is the VLAN properly configured on the virtual NIC (portgroup on ESX f.e.)? 2nd: Is your server able to ...
IP is a Layer-3 addressing scheme, so your subnet layout will only matter for routers. Switches work on Layer-2 and do not deal with IP addresses at all. In Short, a workstation wanting to contact another IP will do a bitwise comarison of netmask and local subnet address. When this results in a local address (your target), an ARP broadcast for that address ...
STILL WONDERING Why doesn't the provided AWS DNS Server work in this case? PROBLEM The problem was that DNS names weren't resolving via the local DNS server than Amazon provided when originally creating the VPC. I discovered that I could make outgoing HTTP/HTTPS connections to IP addresses, which didn't need to contact a DNS server to resolve. SOLUTION ...
Hetzner's firewalls are blocking virtual mac addresses, that's why you gotta do it the "routing way" You need to give your server an IP address from your new subnet allowing it to communicate there. So basically your first ip is the route to the outworld and the subnet is controlled by your hosts ip (the server you bought). One thing what I hate about ...
Your computer is probably connected to an Ethernet switch, which is only going to transmit broadcast traffic or traffic bound to your computer's MAC address. This is the difference between a switch, which gives each computer a dedicated Ethernet collision domain, and an Ethernet hub, which shares a collision domain across all connected devices. In a ...
The problem is that your default gateway (192.168.3.1) isn't aware that the 192.168.2.0/24 hosts are on the same subnet. It probably thinks that the contiguous subnet is 192.168.3.2 - 192.168.4.254. Expand your DHCP scope to encompass 192.168.4.0/24 and you should be OK. Stop using 192.168.2.0/24.
No, if you do not have direct access to B. IP packet do not pass any information where it should go except final destination IP. So router has to determine its next hop only by his routing table and destination IP.
The problem is that you have two separate IP networks in the same broadcast domain, and therefore you don't get the behavior you want. You need to set up separate VLANs for the different devices you have, so that there is only one DHCP server per network/broadcast domain.
Top 50 recent answers are included