![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
![]() | The contents of the IP forwarding algorithm page were merged into IP routing. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. (2015-10-17) |
I've moved this contribution by 203.90.124.66. Its not quite ready for inclusion. ~ KvnG 16:15, 11 October 2013 (UTC)
Both bridging and IP Forwarding allow XP to act as a router between subnets. You would use this if you have two different network segments and you need to have traffic from both available. This is particularly useful if the two network segments are of different media types.
The network bridge allows you to connect LAN segments by selecting the appropriate network connection icons and clicking Bridge Connections. Similar buttons allow you to enable the bridge and add connections to it. The network bridge manages your LAN segments and creates a single subnet for the entire network. There is no configuration required, and you do not need purchase additional hardware such as routers or bridges. IP addressing, address allocation, and name resolution is highly simplified in a single subnet IP network.
The network bridge can create connections between different types of network media. In a traditional network, if you are using mixed media types you need a separate subnet for each type of media, and packet forwarding is required between each one of the network's multiple subnets. Packet forwarding is required because different protocols are used for different types of media. Network Bridge automates the configuration that is required in order to forward information from one type of media to another.
If you just need to enable Netbios traffic, you can use the XP native support for Bridging. For TCP/IP you need to make a registry entry to enable IP forwarding.
Set this key to 1 to enable routing, or 0 to disable (disabled is the default): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter
See: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/columns/cableguy/cg0102.asp victorv (Vendor) 23 Jun 03 8:51 Suppose you have 2 NETs in your company with no physical connection
NET A: net=192.168.1.0 NM=255.255.255.0 DG=192.168.1.251
NET B: net=192.168.2.0 NM=255.255.255.0 DG=192.168.2.251
192.168.1.251 and 192.168.2.251 are 2 routers one for each network
If you ping a PC of NET B from one of the NET A you see timeout.
The best way to understand this is to think your Pc with 2 nics (also if it is not mandatory).
you wire nic 1 on Lan A and give IpAd = 192.168.1.100 you wire nic 2 on Lan B and give IpAd = 192.168.2.100
Now the 2 network are linked by your PC : from your PC you can ping address of both net, but other PC of NET A cannot still see PC of NET B.
In one PC of net A, you can add a another gateway putting the adress of your PC (192.168.1.100)
In one PC of net B, you can add a another gateway and you can put the 2nd adress of your PC (192.168.2.100)
If you activate IP-Forwarding, (probably you have a NT4) your PC can acts as router between networks.
Contact me for more details Ajnas 9944855619
It is not clear from the article as it stands exactly what distinguishes IP forwarding from Routing or IP forwarding algorithm. ~ KvnG 14:20, 30 September 2014 (UTC)
The result of the move request was: Moved ( non-admin closure) — Andy W. ( talk) 01:32, 10 November 2016 (UTC)
IP forwarding → IP routing – More accurate article name as most part of this article uses term "routing" rather than "forwarding", and can be more distinct from packet forwarding. UU ( talk) 18:39, 22 October 2016 (UTC) --Relisting. — Amakuru ( talk) 14:35, 1 November 2016 (UTC)
After reviewing and some edit work, I found that the old article title was actually more appropriate to the then-content of the article. But the topic of IP forwarding should be discussed in the broader context of IP routing not vice-versa. As much of the original content was more or less plagiarized from a single source, it is time to redirect the focus of the article to the wider subject matter and distinguish it more prominently from its cousins Routing and Packet forwarding. Kbrose ( talk) 15:04, 12 November 2016 (UTC)
![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
![]() | The contents of the IP forwarding algorithm page were merged into IP routing. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. (2015-10-17) |
I've moved this contribution by 203.90.124.66. Its not quite ready for inclusion. ~ KvnG 16:15, 11 October 2013 (UTC)
Both bridging and IP Forwarding allow XP to act as a router between subnets. You would use this if you have two different network segments and you need to have traffic from both available. This is particularly useful if the two network segments are of different media types.
The network bridge allows you to connect LAN segments by selecting the appropriate network connection icons and clicking Bridge Connections. Similar buttons allow you to enable the bridge and add connections to it. The network bridge manages your LAN segments and creates a single subnet for the entire network. There is no configuration required, and you do not need purchase additional hardware such as routers or bridges. IP addressing, address allocation, and name resolution is highly simplified in a single subnet IP network.
The network bridge can create connections between different types of network media. In a traditional network, if you are using mixed media types you need a separate subnet for each type of media, and packet forwarding is required between each one of the network's multiple subnets. Packet forwarding is required because different protocols are used for different types of media. Network Bridge automates the configuration that is required in order to forward information from one type of media to another.
If you just need to enable Netbios traffic, you can use the XP native support for Bridging. For TCP/IP you need to make a registry entry to enable IP forwarding.
Set this key to 1 to enable routing, or 0 to disable (disabled is the default): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter
See: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/columns/cableguy/cg0102.asp victorv (Vendor) 23 Jun 03 8:51 Suppose you have 2 NETs in your company with no physical connection
NET A: net=192.168.1.0 NM=255.255.255.0 DG=192.168.1.251
NET B: net=192.168.2.0 NM=255.255.255.0 DG=192.168.2.251
192.168.1.251 and 192.168.2.251 are 2 routers one for each network
If you ping a PC of NET B from one of the NET A you see timeout.
The best way to understand this is to think your Pc with 2 nics (also if it is not mandatory).
you wire nic 1 on Lan A and give IpAd = 192.168.1.100 you wire nic 2 on Lan B and give IpAd = 192.168.2.100
Now the 2 network are linked by your PC : from your PC you can ping address of both net, but other PC of NET A cannot still see PC of NET B.
In one PC of net A, you can add a another gateway putting the adress of your PC (192.168.1.100)
In one PC of net B, you can add a another gateway and you can put the 2nd adress of your PC (192.168.2.100)
If you activate IP-Forwarding, (probably you have a NT4) your PC can acts as router between networks.
Contact me for more details Ajnas 9944855619
It is not clear from the article as it stands exactly what distinguishes IP forwarding from Routing or IP forwarding algorithm. ~ KvnG 14:20, 30 September 2014 (UTC)
The result of the move request was: Moved ( non-admin closure) — Andy W. ( talk) 01:32, 10 November 2016 (UTC)
IP forwarding → IP routing – More accurate article name as most part of this article uses term "routing" rather than "forwarding", and can be more distinct from packet forwarding. UU ( talk) 18:39, 22 October 2016 (UTC) --Relisting. — Amakuru ( talk) 14:35, 1 November 2016 (UTC)
After reviewing and some edit work, I found that the old article title was actually more appropriate to the then-content of the article. But the topic of IP forwarding should be discussed in the broader context of IP routing not vice-versa. As much of the original content was more or less plagiarized from a single source, it is time to redirect the focus of the article to the wider subject matter and distinguish it more prominently from its cousins Routing and Packet forwarding. Kbrose ( talk) 15:04, 12 November 2016 (UTC)