80:
53:
22:
148:
184:
888:
used in titles, but one should examine what is actually covered in each article, and then sort the material and name the article accordingly. The article 'packet forwarding' covers the subject much more generally, without specific regard to the type of packets, only uses examples occasionally. That
432:
are titled "IP Forwarding Table MIB". However, in reading the history outlined in that chain of RFCs the IP forwarding table replaced the IP routing table and has additional fields. The IP forwarding table was itself replaced by the IP version-independent CIDR Route Table. Thus we are back to using
247:
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
889:
was the reason I reverted the previous merge operation, because it completely neglected the areas of coverage of each, and was solely based on comparing the title words. This requires some work to sort the contents and decide what the most accepted or notable subject divisions are in the field.
243:
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
549:
Within Cisco routers the term "IP forwarding" comes up from time to time as they have an "IP forwarding" table that speeds up the forwarding of packets as though they were being routed. The processing of packets that pass through a Cisco device is handled by what what they call the
239:
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.
985:!vote was uncountered for about a week. Do you still dispute the page renaming? If so, I can revert the move and re-open the request... On the other hand, I see you began some content revisions already. I'm available to assist technically if there's a need, thanks —
650:
should probably cover the subject at the highest level, in terms of routing principles and philosophies, and various types of routing mechanisms. IP routing should cover specifically the principles and issues of routing
Internet Protocol packets. If
244:
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.
645:
packets onto a set of interfaces or not, i.e. whether an interface should participate in the higher level rules of routing within the host. So one needs to decide the scope of this article first, before any renaming. The article
1019:
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
419:
After reviewing some books (listed below) I'm thinking the best tactic would be to either rename this article to "IP routing" or to keep the name as "IP forwarding" and to make it clear it's the same thing as IP routing. RFC
980:
I'm not watching this page, but I happened to see your strikeout of the closing statement, which is not exactly good practice. I should note that, in my personal observation, after WT Computing was pinged, the following
1071:
596:
cover routing for all networks and for this article to cover routing for IP networks. If that were all there were to it, I don't think I would support having separate articles. However, it looks to me as though
454:
article is mostly general purpose and has very little
Internet Protocol content. While Internet Protocol is now dominant the routing article should mention some of the other routable network protocols such as
248:
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.
380:
I agree with you that the IP forwarding article does a poor job of explaining the generic concept of forwarding plus switching and distinguishing them from routing, which is a form of forwarding. --
157:
63:
1066:
162:
609:
topics for the exchange of information about how to deliver packets. I'm not sure exactly what to do but in the end, but I do support your proposal to rename this article
1061:
783:
254:
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
251:
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.
138:
1011:
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
641:
appears in principle the same as IP routing, it seems the term is mostly used in the scope of a single host when the decision is to be made of whether to
1056:
128:
1076:
1051:
104:
282:
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.
488:
768:
Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a
816:– More accurate article name as most part of this article uses term "routing" rather than "forwarding", and can be more distinct from
87:
58:
484:
258:
1081:
33:
210:
948:
759:
362:
909:
480:
370:
374:
366:
958:
769:
39:
21:
288:
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)
934:
721:
is the relaying of packets from one network segment to another by nodes in a computer network. In addition,
325:
311:
279:
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
655:
is still needed as a topic, its scope needs to be clearly defined. I tend to think it would not be needed.
994:
797:
100:
564:
464:
385:
358:
226:
103:
on
Knowledge (XXG). If you would like to participate, please visit the project page, where you can join
291:
If you activate IP-Forwarding, (probably you have a NT4) your PC can acts as router between networks.
261:
victorv (Vendor) 23 Jun 03 8:51 Suppose you have 2 NETs in your company with no physical connection
602:
196:
533:
930:
526:
does not have an entry for forwarding in the glossary. The index only has "Forwarding, mail 435".
285:
In one PC of net A, you can add a another gateway putting the adress of your PC (192.168.1.100)
203:
on 2015-10-17. For the contribution history and old versions of the redirected page, please see
276:
The best way to understand this is to think your Pc with 2 nics (also if it is not mandatory).
986:
917:
841:
817:
789:
710:
543:
259:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/columns/cableguy/cg0102.asp
821:
734:
1033:
894:
678:
660:
606:
589:
560:
551:
523:
381:
873:
690:
618:
398:
341:
315:
230:
1045:
809:
706:
377:
where a device can behave like a router but implements it via switching and bridging.
329:
303:
913:
837:
825:
738:
472:
336:. I will direct some merge banners here and see if we can get a discussion going. ~
1029:
975:
890:
853:
656:
79:
52:
957:
Subsequent comments should be made in a new section on this talk page or in a
857:
813:
674:
610:
520:
Internetworking with TCP/IP: Volume I: Principles, Protocols, and
Architecture
492:
200:
869:
686:
614:
496:
394:
352:
337:
96:
605:
article for the process of moving packets through a routed network and the
592:
for taking a deeper look at this. It looks like your suggestion is to let
373:, all of which are not part of IP routing. There are also hybrids such as
456:
302:
It is not clear from the article as it stands exactly what distinguishes
92:
393:
Do you have any sources to back up your proposed scope for this topic? ~
861:
722:
682:
598:
593:
451:
333:
307:
429:
425:
421:
476:
147:
270:
192.168.1.251 and 192.168.2.251 are 2 routers one for each network
1037:
1000:
938:
921:
898:
877:
845:
803:
742:
694:
681:
already redirect here. Of course, we can adjust these to point at
664:
622:
567:
402:
388:
345:
318:
233:
532:(I have the 2nd edition handy but it's up to the 5th edition) by
273:
If you ping a PC of NET B from one of the NET A you see timeout.
717:
is a process used to determine which path a packet can be sent;
460:
468:
178:
15:
264:
NET A: net=192.168.1.0 NM=255.255.255.0 DG=192.168.1.251
146:
1072:
Start-Class
Computer networking articles of High-importance
267:
NET B: net=192.168.2.0 NM=255.255.255.0 DG=192.168.2.251
884:
A decision or proposal should not be based on merely the
516:
The books I checked for references to "forwarding" were:
713:, as their definitions are too similar. By definition,
205:
191:
947:
The above discussion is preserved as an archive of a
725:
describes BOTH definitions, and in practice, merging
929:. Clearly, this is a routing article. Best regards,
91:, a collaborative effort to improve the coverage of
772:. No further edits should be made to this section.
961:. No further edits should be made to this section.
912:to see if more feedback can be established. —
546:does not have an entry for forwarding in index.
536:does not have an entry for forwarding in index.
1015:should be discussed in the broader context of
856:'s proposal to end up with two articles here:
328:redirecting here. Still there's an issue with
294:Contact me for more details Ajnas 9944855619
8:
1067:High-importance Computer networking articles
209:; for the discussion at that location, see
19:
758:The following is a closed discussion of a
47:
852:I assume this request is working towards
1062:Start-Class Computer networking articles
733:will prevent from mixing up of topics.
49:
229:. Its not quite ready for inclusion. ~
554:" in both their switches and routers.
113:Knowledge (XXG):WikiProject Computing
7:
777:The result of the move request was:
673:That's reasonable but be aware that
357:I consider IP forwarding to include
85:This article is within the scope of
38:It is of interest to the following
495:could also be routed. Technically
14:
1057:Low-importance Computing articles
1077:All Computer networking articles
225:I've moved this contribution by
182:
78:
51:
20:
828:) 18:39, 22 October 2016 (UTC)
369:(PAT), and to a lesser extent,
133:This article has been rated as
1052:Start-Class Computing articles
751:Requested move 22 October 2016
568:07:33, 28 September 2016 (UTC)
403:00:36, 28 September 2016 (UTC)
389:00:22, 28 September 2016 (UTC)
319:14:20, 30 September 2014 (UTC)
116:Template:WikiProject Computing
1:
1038:15:04, 12 November 2016 (UTC)
1001:17:52, 10 November 2016 (UTC)
804:01:32, 10 November 2016 (UTC)
155:This article is supported by
107:and see a list of open tasks.
939:06:12, 2 November 2016 (UTC)
922:14:35, 1 November 2016 (UTC)
899:15:35, 25 October 2016 (UTC)
878:14:29, 25 October 2016 (UTC)
846:14:35, 1 November 2016 (UTC)
743:18:09, 22 October 2016 (UTC)
234:16:15, 11 October 2013 (UTC)
695:20:41, 4 October 2016 (UTC)
665:16:54, 1 October 2016 (UTC)
623:15:46, 1 October 2016 (UTC)
363:Network Address Translation
346:21:09, 22 August 2016 (UTC)
1098:
139:project's importance scale
154:
132:
73:
46:
954:Please do not modify it.
765:Please do not modify it.
375:Cisco Express Forwarding
367:Port address translation
685:instead if necessary. ~
540:Routing in the Internet
433:the words "IP routing".
326:IP forwarding algorithm
312:IP forwarding algorithm
192:IP forwarding algorithm
1082:All Computing articles
151:
101:information technology
28:This article is rated
189:The contents of the
158:Networking task force
150:
88:WikiProject Computing
32:on Knowledge (XXG)'s
709:should be merged to
499:could be routed too.
220:Unready contribution
534:Andrew S. Tanenbaum
613:as a first step. ~
152:
119:Computing articles
34:content assessment
1026:Packet forwarding
906:Relisting comment
848:
818:packet forwarding
787:
784:non-admin closure
731:packet forwarding
719:packet forwarding
711:packet forwarding
601:is potentially a
544:Christian Huitema
530:Computer Networks
217:
216:
177:
176:
173:
172:
169:
168:
1089:
997:
979:
956:
829:
800:
781:
767:
679:Internet routing
607:Routing protocol
552:forwarding plane
524:Douglas E. Comer
356:
324:Better now with
208:
186:
185:
179:
121:
120:
117:
114:
111:
82:
75:
74:
69:
66:
55:
48:
31:
25:
24:
16:
1097:
1096:
1092:
1091:
1090:
1088:
1087:
1086:
1042:
1041:
1009:
995:
973:
970:
965:
952:
908:. I am pinging
798:
763:
753:
350:
300:
222:
204:
183:
163:High-importance
118:
115:
112:
109:
108:
67:
61:
29:
12:
11:
5:
1095:
1093:
1085:
1084:
1079:
1074:
1069:
1064:
1059:
1054:
1044:
1043:
1008:
1005:
1004:
1003:
969:
966:
964:
963:
949:requested move
943:
942:
941:
924:
902:
901:
881:
880:
807:
775:
774:
760:requested move
754:
752:
749:
748:
747:
746:
745:
700:
699:
698:
697:
668:
667:
634:
633:
632:
631:
630:
629:
628:
627:
626:
625:
577:
576:
575:
574:
573:
572:
571:
570:
557:
556:
555:
547:
537:
527:
507:
506:
505:
504:
503:
502:
501:
500:
475:derivatives),
441:
440:
439:
438:
437:
436:
435:
434:
410:
409:
408:
407:
406:
405:
378:
299:
296:
221:
218:
215:
214:
187:
175:
174:
171:
170:
167:
166:
153:
143:
142:
135:Low-importance
131:
125:
124:
122:
105:the discussion
83:
71:
70:
68:Low‑importance
56:
44:
43:
37:
26:
13:
10:
9:
6:
4:
3:
2:
1094:
1083:
1080:
1078:
1075:
1073:
1070:
1068:
1065:
1063:
1060:
1058:
1055:
1053:
1050:
1049:
1047:
1040:
1039:
1035:
1031:
1027:
1023:
1018:
1014:
1013:IP forwarding
1006:
1002:
998:
992:
991:
990:
984:
977:
972:
971:
967:
962:
960:
955:
950:
945:
944:
940:
936:
932:
931:Codename Lisa
928:
925:
923:
919:
915:
911:
907:
904:
903:
900:
896:
892:
887:
883:
882:
879:
875:
871:
867:
863:
859:
855:
851:
850:
849:
847:
843:
839:
835:
834:
827:
823:
819:
815:
811:
810:IP forwarding
806:
805:
801:
795:
794:
793:
785:
780:
773:
771:
766:
761:
756:
755:
750:
744:
740:
736:
732:
728:
727:IP forwarding
724:
720:
716:
715:IP forwarding
712:
708:
707:IP forwarding
704:
703:
702:
701:
696:
692:
688:
684:
680:
676:
672:
671:
670:
669:
666:
662:
658:
654:
653:IP forwarding
649:
644:
640:
639:IP forwarding
636:
635:
624:
620:
616:
612:
608:
604:
600:
595:
591:
587:
586:
585:
584:
583:
582:
581:
580:
579:
578:
569:
566:
562:
558:
553:
548:
545:
541:
538:
535:
531:
528:
525:
521:
518:
517:
515:
514:
513:
512:
511:
510:
509:
508:
498:
494:
490:
486:
482:
478:
474:
470:
466:
462:
458:
453:
450:The existing
449:
448:
447:
446:
445:
444:
443:
442:
431:
427:
423:
418:
417:
416:
415:
414:
413:
412:
411:
404:
400:
396:
392:
391:
390:
387:
383:
379:
376:
372:
371:encapsulation
368:
364:
360:
354:
349:
348:
347:
343:
339:
335:
331:
330:IP forwarding
327:
323:
322:
321:
320:
317:
313:
309:
305:
304:IP forwarding
297:
295:
292:
289:
286:
283:
280:
277:
274:
271:
268:
265:
262:
260:
255:
252:
249:
245:
241:
237:
236:
235:
232:
228:
227:203.90.124.66
219:
212:
211:its talk page
207:
202:
198:
194:
193:
188:
181:
180:
164:
161:(assessed as
160:
159:
149:
145:
144:
140:
136:
130:
127:
126:
123:
106:
102:
98:
94:
90:
89:
84:
81:
77:
76:
72:
65:
60:
57:
54:
50:
45:
41:
35:
27:
23:
18:
17:
1025:
1021:
1016:
1012:
1010:
988:
987:
982:
953:
946:
926:
910:WT:COMPUTING
905:
885:
868:this move. ~
865:
832:
831:
808:
791:
790:
778:
776:
764:
757:
730:
726:
718:
714:
652:
647:
642:
638:
539:
529:
519:
483:, and IBM's
473:Banyan Vines
301:
293:
290:
287:
284:
281:
278:
275:
272:
269:
266:
263:
256:
253:
250:
246:
242:
238:
224:
223:
190:
156:
134:
86:
40:WikiProjects
959:move review
864:. If so, I
770:move review
590:Marc Kupper
561:Marc Kupper
382:Marc Kupper
206:its history
30:Start-class
1046:Categories
1017:IP routing
1007:Post-Issue
858:IP routing
833:Relisting.
814:IP routing
675:IP routing
611:IP routing
603:WP:SUMMARY
493:Token ring
491:. I think
201:IP routing
195:page were
64:Networking
497:AppleTalk
467:(and the
110:Computing
97:computing
93:computers
59:Computing
705:I think
588:Thanks,
457:Chaosnet
359:bridging
1022:Routing
989:Andy W.
983:support
968:Post-RM
927:Support
914:Amakuru
866:support
862:Routing
838:Amakuru
792:Andy W.
723:routing
683:Routing
648:Routing
643:forward
599:Routing
594:Routing
452:routing
365:(NAT),
334:Routing
308:Routing
298:Context
137:on the
1030:Kbrose
976:Kbrose
891:Kbrose
854:Kbrose
657:Kbrose
637:While
477:DECnet
428:, and
257:See:
197:merged
99:, and
36:scale.
886:words
779:Moved
487:plus
471:plus
306:from
199:into
1034:talk
1024:and
996:talk
935:talk
918:talk
895:talk
874:talk
870:Kvng
860:and
842:talk
826:talk
799:talk
739:talk
729:and
691:talk
687:Kvng
677:and
661:talk
619:talk
615:Kvng
565:talk
489:APPN
461:X.25
430:4292
426:4292
422:1354
399:talk
395:Kvng
386:talk
353:Kvng
342:talk
338:Kvng
332:vs.
316:KvnG
231:KvnG
951:.
542:by
522:by
485:SNA
481:ATM
469:IPX
465:XNS
314:. ~
310:or
129:Low
1048::
1036:)
1028:.
999:)
937:)
920:)
897:)
876:)
844:)
836:—
830:--
822:UU
820:.
812:→
802:)
788:—
762:.
741:)
735:UU
693:)
663:)
621:)
559:--
479:,
463:,
459:,
424:,
401:)
361:,
344:)
165:).
95:,
62::
1032:(
993:(
978::
974:@
933:(
916:(
893:(
872:(
840:(
824:(
796:(
786:)
782:(
737:(
689:(
659:(
617:(
563:|
550:"
397:(
384:|
355::
351:@
340:(
213:.
141:.
42::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
