Do we need an interface router per each subnetwork? [closed] - networking

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have the knowledge to do subnetingmath, but I confused what device that is used to separate each subnet from other ones? who will route packets to the right subnetwork destination? If it is the router, do we need an interface per each subnetwork?

It is the router the one in charge of routing the packets to the right subnetworks. You need to assign each subnetwork to a different interface, but this does not necessarily mean physical interfaces. You can use virtual interfaces as well.
Here's a Cisco link about them:
http://www.cisco.com/en/US/docs/ios/12_4/interface/configuration/guide/inb_virt.html

If you have multiple internal subnets, the industry standard is to create sub-interfaces and encapsulate as a DOT1Q trunk between the router and the switch.
Example R1
Interfaces:
S0/0/0 - used for WAN
Fa0/1 -physical internal interface
Fa0/1.100 Data VLAN (sub-interface)
Fa0/1.200 Voice VLAN (sub-interface)
Switch. Will have VLANs 100 and 200 on it and the trunk port will be configured as encapsulation DOT1Q. With these commands.
"switchport mode trunk"
"switchport trunk encapsulation dot1q"
I have literally done this thousands of times. Don't waste money on separate router interfaces for internal subnets.
Hope this helps.

Related

How to set up 2 separate VLAN on one switch (HP v1910-48G switch) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I need some advice on how to set up 2 VLAN(on one switch, I have HP v1910-48G switch) that separate broadcast domain and also share a single internet connection.
Whilst remaining separate so that the two networks cannot communicate with each other.
I'm not sure on how to create vlans on that spesific switch, but i'll give you what to look for. First off you will need to create your two diffrent vlans, assign them their own vlan ID and take note of them.
Then find an overview or list of your diffrent ports, you will then have to tag or untag ports depending on what kind of type that port will have.
Tag - When putting multiple vlans in one cable, or trunking between two switches.
Untag - What ports that will be a part of that vlan
Here is an example. I have one router, a switch, and 20 computers. I connect a cable to the router to the switch (backbone) on port 1. I then connect my computers on the switch from port 2-21.
Now i create the diffrent vlans, i create one that is named guestnet and one called companynet. I then untag the backbone (port 1) with both guestnet and companynet (if you dont want access to the internet on one of those vlans you dont untag the backbone with that vlan, then its just LAN only.)
Now i can untag the ports that the computers will connect to. I tag port 2-11 with guestnet and 12-21 with companynet. Theese vlans cannot communicate between them, which is great for seperating guests from the company files and servers.
Hope this helped!
-Kad

Using one ethernet interface to communicate with two routers separately [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
We have a computer that needs to communicate with two routers over one physical ethernet interface. I know this sounds weird, but each router is actually interfaced to an Iridium L Band receiver/transmitter, and we are hoping to double our bandwidth by using two.
I would like to be able to select which link to send data over at the application level, but I'm not quite sure how to do it. My first thought was to establish a virtual IP address in addition to the pre-configured static IP address and use two separate sockets to send() data out over each "interface" separately. My question is, how do I make it so that only one of the routers actually routes the data out to a remote host? The IP addresses and subnet masks of the Iridium transceivers are configurable. Is it possible to make one transceiver only listen to the data coming from one computer IP address? Subnets maybe?
Create vlan inter faces in your machine
ip link add link eth0 name eth0.1 type vlan id 10
ip link add link eth0 name eth0.2 type vlan id 20
assign ip address to eth0.1 and eth0.2 in two networks. Later you can choose which one to bind at application level.
say like this
ifconfig eth0.1 192.168.10.2/24 up
ifconfig eth0.2 192.168.20.2/24 up
Then configure your router in two networks rather than one. Your computer and the routers should be connected to trunk port in the switch. Configure your routers to be in two networks rather than same. Configure subinterfaces in routers so that they listen for vlan 10 and 20 respectively. (how exactly to do this depends on the type of router) I can give you commands only for cisco.

Router vs Switch (Network Address Translation) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I understand that a router uses NAT to translate the public IP we get from the ISP to say 300 local IPs. Does a switch perform the same function? If not, how's it different?
No, a switch cannot perform NAT and translate public(s) IP addresses into private addresses.
A switch is a network device that filters and forwards packets between LAN segments. Switches operate at the data link layer (layer 2). So, they are not aware of IP addresses which are network layer (layer 3). A switch keeps a record of the MAC addresses of all the devices connected to it. With this information, a switch can identify which system is sitting on which port. So when a frame is received, it knows exactly which port to send it to, without significantly increasing network response times.
Routers are network devices used to interconnect two different networks (with different IP addressing schemes).

What is the purpose of LAN IP addresses? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
whats the purpose of local IP addresses if there are mac addresses? ARP maps mac addresses to IP addresses but I don't see why it's needed, because I thought data on LANs are sent as frames which only care about the mac addresses.
Long ago and far away, there was more to the world than Ethernet LANs, and application writers didn't care whether your PC was attached to an Ethernet, a Token Ring, an XNS net, or dial-up. IP provides a layer of abstraction and coherence across the top of all those and many more, allowing application authors to ignore the differences between them.
And what happens if you want to talk to a macine that isn't on your local area network (such as StackOverflow).
IP allows routing of packets anywhere, not just locally in your current network segment and, though it's mostly over Ethernet now, IP can equally well work over other underlying layers, giving a consistent view to the upper layers. This is vital given how much stuff is actually built on IP (DNS, FTP, SSH, HTTP and so on).
Machines almost certainly will cache IP-to-ethernet details to speed up subsequent transfers so the impact of translation on the LAN isn't so bad.

can IPv6 eliminate mac address [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
MAC address are used for uniquely identifying my computer.
IP address are used for routing the packets to the network, as it has got a hierarchial structure, but it doesn't uniquely identifies a computer. So, after IPv6, each computer will have a unique IP address, so will there be any need of MAC address then?
Please do correct me, if I had understood something wrong.
No. MAC addresses operate at layer 2 ("data link layer"). The Internet Protocol (both IPv4 and IPv6) operates at layer 3 ("network layer").
These two layers are complimentary, and do not "replace" each other. For more information, read up on the TCP/IP suite.
IPv6 stateless address autoconfiguration (SLAAC) uses the MAC address to generate the address, but that does not mean they "replace" each other. It's simply a characteristic of the layer 2 interface being inherited by the layer 3 addressing. Other than that, completely complimentary.

Resources