€•       Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ%/translations/zh_CN/networking/arcnet”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/zh_TW/networking/arcnet”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/it_IT/networking/arcnet”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/ja_JP/networking/arcnet”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/ko_KR/networking/arcnet”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/sp_SP/networking/arcnet”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒ?/var/lib/git/docbuild/linux/Documentation/networking/arcnet.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒARCnet”h]”hŒARCnet”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒnote”“”)”}”(hŒ¬See also arcnet-hardware.txt in this directory for jumper-setting
and cabling information if you're like many of us and didn't happen to get a
manual with your ARCnet card.”h]”hŒ	paragraph”“”)”}”(hŒ¬See also arcnet-hardware.txt in this directory for jumper-setting
and cabling information if you're like many of us and didn't happen to get a
manual with your ARCnet card.”h]”hŒ°See also arcnet-hardware.txt in this directory for jumper-setting
and cabling information if youâ€™re like many of us and didnâ€™t happen to get a
manual with your ARCnet card.”…””}”(hhÑhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K	hhËubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhh¶hžhhŸh³h NubhÐ)”}”(hŒVSince no one seems to listen to me otherwise, perhaps a poem will get your
attention::”h]”hŒUSince no one seems to listen to me otherwise, perhaps a poem will get your
attention:”…””}”(hhåhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhŒliteral_block”“”)”}”(hŒDThis driver's getting fat and beefy,
But my cat is still named Fifi.”h]”hŒDThis driver's getting fat and beefy,
But my cat is still named Fifi.”…””}”hhõsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h Khh¶hžhubhÐ)”}”(hŒŒHmm, I think I'm allowed to call that a poem, even though it's only two
lines.  Hey, I'm in Computer Science, not English.  Give me a break.”h]”hŒ’Hmm, I think Iâ€™m allowed to call that a poem, even though itâ€™s only two
lines.  Hey, Iâ€™m in Computer Science, not English.  Give me a break.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhÐ)”}”(hŒŽThe point is:  I REALLY REALLY REALLY REALLY REALLY want to hear from you if
you test this and get it working.  Or if you don't.  Or anything.”h]”hŒThe point is:  I REALLY REALLY REALLY REALLY REALLY want to hear from you if
you test this and get it working.  Or if you donâ€™t.  Or anything.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhÐ)”}”(hŒÀARCnet 0.32 ALPHA first made it into the Linux kernel 1.1.80 - this was
nice, but after that even FEWER people started writing to me because they
didn't even have to install the patch.  <sigh>”h]”hŒÂARCnet 0.32 ALPHA first made it into the Linux kernel 1.1.80 - this was
nice, but after that even FEWER people started writing to me because they
didnâ€™t even have to install the patch.  <sigh>”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhÐ)”}”(hŒ/Come on, be a sport!  Send me a success report!”h]”hŒ/Come on, be a sport!  Send me a success report!”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhÐ)”}”(hŒI(hey, that was even better than my original poem... this is getting bad!)”h]”hŒI(hey, that was even better than my original poem... this is getting bad!)”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhŒwarning”“”)”}”(hX§  If you don't e-mail me about your success/failure soon, I may be forced to
start SINGING.  And we don't want that, do we?

(You know, it might be argued that I'm pushing this point a little too much.
If you think so, why not flame me in a quick little e-mail?  Please also
include the type of card(s) you're using, software, size of network, and
whether it's working or not.)

My e-mail address is: apenwarr@worldvisions.ca”h]”(hÐ)”}”(hŒyIf you don't e-mail me about your success/failure soon, I may be forced to
start SINGING.  And we don't want that, do we?”h]”hŒ}If you donâ€™t e-mail me about your success/failure soon, I may be forced to
start SINGING.  And we donâ€™t want that, do we?”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K$hjK  ubhÐ)”}”(hŒü(You know, it might be argued that I'm pushing this point a little too much.
If you think so, why not flame me in a quick little e-mail?  Please also
include the type of card(s) you're using, software, size of network, and
whether it's working or not.)”h]”hX  (You know, it might be argued that Iâ€™m pushing this point a little too much.
If you think so, why not flame me in a quick little e-mail?  Please also
include the type of card(s) youâ€™re using, software, size of network, and
whether itâ€™s working or not.)”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K'hjK  ubhÐ)”}”(hŒ.My e-mail address is: apenwarr@worldvisions.ca”h]”(hŒMy e-mail address is: ”…””}”(hjk  hžhhŸNh NubhŒ	reference”“”)”}”(hŒapenwarr@worldvisions.ca”h]”hŒapenwarr@worldvisions.ca”…””}”(hju  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:apenwarr@worldvisions.ca”uh1js  hjk  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K,hjK  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jI  hh¶hžhhŸh³h NubhÐ)”}”(hŒ'These are the ARCnet drivers for Linux.”h]”hŒ'These are the ARCnet drivers for Linux.”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K.hh¶hžhubhÐ)”}”(hX­  This new release (2.91) has been put together by David Woodhouse
<dwmw2@infradead.org>, in an attempt to tidy up the driver after adding support
for yet another chipset. Now the generic support has been separated from the
individual chipset drivers, and the source files aren't quite so packed with
#ifdefs! I've changed this file a bit, but kept it in the first person from
Avery, because I didn't want to completely rewrite it.”h]”(hŒBThis new release (2.91) has been put together by David Woodhouse
<”…””}”(hjŸ  hžhhŸNh Nubjt  )”}”(hŒdwmw2@infradead.org”h]”hŒdwmw2@infradead.org”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:dwmw2@infradead.org”uh1js  hjŸ  ubhX^  >, in an attempt to tidy up the driver after adding support
for yet another chipset. Now the generic support has been separated from the
individual chipset drivers, and the source files arenâ€™t quite so packed with
#ifdefs! Iâ€™ve changed this file a bit, but kept it in the first person from
Avery, because I didnâ€™t want to completely rewrite it.”…””}”(hjŸ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K0hh¶hžhubhÐ)”}”(hXU  The previous release resulted from many months of on-and-off effort from me
(Avery Pennarun), many bug reports/fixes and suggestions from others, and in
particular a lot of input and coding from Tomasz Motylewski.  Starting with
ARCnet 2.10 ALPHA, Tomasz's all-new-and-improved RFC1051 support has been
included and seems to be working fine!”h]”hXW  The previous release resulted from many months of on-and-off effort from me
(Avery Pennarun), many bug reports/fixes and suggestions from others, and in
particular a lot of input and coding from Tomasz Motylewski.  Starting with
ARCnet 2.10 ALPHA, Tomaszâ€™s all-new-and-improved RFC1051 support has been
included and seems to be working fine!”…””}”(hjÁ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K7hh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒ!Where do I discuss these drivers?”h]”hŒ!Where do I discuss these drivers?”…””}”(hjÒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÏ  hžhhŸh³h K?ubhÐ)”}”(hX
  Tomasz has been so kind as to set up a new and improved mailing list.
Subscribe by sending a message with the BODY "subscribe linux-arcnet YOUR
REAL NAME" to listserv@tichy.ch.uj.edu.pl.  Then, to submit messages to the
list, mail to linux-arcnet@tichy.ch.uj.edu.pl.”h]”(hŒ¢Tomasz has been so kind as to set up a new and improved mailing list.
Subscribe by sending a message with the BODY â€œsubscribe linux-arcnet YOUR
REAL NAMEâ€ to ”…””}”(hjà  hžhhŸNh Nubjt  )”}”(hŒlistserv@tichy.ch.uj.edu.pl”h]”hŒlistserv@tichy.ch.uj.edu.pl”…””}”(hjè  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:listserv@tichy.ch.uj.edu.pl”uh1js  hjà  ubhŒ1.  Then, to submit messages to the
list, mail to ”…””}”(hjà  hžhhŸNh Nubjt  )”}”(hŒlinux-arcnet@tichy.ch.uj.edu.pl”h]”hŒlinux-arcnet@tichy.ch.uj.edu.pl”…””}”(hjü  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ&mailto:linux-arcnet@tichy.ch.uj.edu.pl”uh1js  hjà  ubhŒ.”…””}”(hjà  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KAhjÏ  hžhubhÐ)”}”(hŒ*There are archives of the mailing list at:”h]”hŒ*There are archives of the mailing list at:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KFhjÏ  hžhubhŒblock_quote”“”)”}”(hŒ2http://epistolary.org/mailman/listinfo.cgi/arcnet
”h]”hÐ)”}”(hŒ1http://epistolary.org/mailman/listinfo.cgi/arcnet”h]”jt  )”}”(hj,  h]”hŒ1http://epistolary.org/mailman/listinfo.cgi/arcnet”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j,  uh1js  hj*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KHhj&  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h KHhjÏ  hžhubhÐ)”}”(hŒíThe people on linux-net@vger.kernel.org (now defunct, replaced by
netdev@vger.kernel.org) have also been known to be very helpful, especially
when we're talking about ALPHA Linux kernels that may or may not work right
in the first place.”h]”(hŒThe people on ”…””}”(hjH  hžhhŸNh Nubjt  )”}”(hŒlinux-net@vger.kernel.org”h]”hŒlinux-net@vger.kernel.org”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ mailto:linux-net@vger.kernel.org”uh1js  hjH  ubhŒ (now defunct, replaced by
”…””}”(hjH  hžhhŸNh Nubjt  )”}”(hŒnetdev@vger.kernel.org”h]”hŒnetdev@vger.kernel.org”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:netdev@vger.kernel.org”uh1js  hjH  ubhŒ—) have also been known to be very helpful, especially
when weâ€™re talking about ALPHA Linux kernels that may or may not work right
in the first place.”…””}”(hjH  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KJhjÏ  hžhubeh}”(h]”Œ where-do-i-discuss-these-drivers”ah ]”h"]”Œ!where do i discuss these drivers?”ah$]”h&]”uh1h´hh¶hžhhŸh³h K?ubhµ)”}”(hhh]”(hº)”}”(hŒOther Drivers and Info”h]”hŒOther Drivers and Info”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj†  hžhhŸh³h KQubhÐ)”}”(hŒ4You can try my ARCNET page on the World Wide Web at:”h]”hŒ4You can try my ARCNET page on the World Wide Web at:”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KShj†  hžhubj%  )”}”(hŒ%http://www.qis.net/~jschmitz/arcnet/
”h]”hÐ)”}”(hŒ$http://www.qis.net/~jschmitz/arcnet/”h]”jt  )”}”(hj«  h]”hŒ$http://www.qis.net/~jschmitz/arcnet/”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j«  uh1js  hj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KUhj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h KUhj†  hžhubhÐ)”}”(hŒ¬Also, SMC (one of the companies that makes ARCnet cards) has a WWW site you
might be interested in, which includes several drivers for various cards
including ARCnet.  Try:”h]”hŒ¬Also, SMC (one of the companies that makes ARCnet cards) has a WWW site you
might be interested in, which includes several drivers for various cards
including ARCnet.  Try:”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KWhj†  hžhubj%  )”}”(hŒhttp://www.smc.com/
”h]”hÐ)”}”(hŒhttp://www.smc.com/”h]”jt  )”}”(hjÛ  h]”hŒhttp://www.smc.com/”…””}”(hjÝ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÛ  uh1js  hjÙ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K[hjÕ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h K[hj†  hžhubhÐ)”}”(hŒMPerformance Technologies makes various network software that supports
ARCnet:”h]”hŒMPerformance Technologies makes various network software that supports
ARCnet:”…””}”(hj÷  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K]hj†  hžhubj%  )”}”(hŒ5http://www.perftech.com/ or ftp to ftp.perftech.com.
”h]”hÐ)”}”(hŒ4http://www.perftech.com/ or ftp to ftp.perftech.com.”h]”(jt  )”}”(hŒhttp://www.perftech.com/”h]”hŒhttp://www.perftech.com/”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j  uh1js  hj	  ubhŒ or ftp to ftp.perftech.com.”…””}”(hj	  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K`hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h K`hj†  hžhubhÐ)”}”(hŒeNovell makes a networking stack for DOS which includes ARCnet drivers.  Try
FTPing to ftp.novell.com.”h]”hŒeNovell makes a networking stack for DOS which includes ARCnet drivers.  Try
FTPing to ftp.novell.com.”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kbhj†  hžhubhÐ)”}”(hX\  You can get the Crynwr packet driver collection (including arcether.com, the
one you'll want to use with ARCnet cards) from
oak.oakland.edu:/simtel/msdos/pktdrvr. It won't work perfectly on a 386+
without patches, though, and also doesn't like several cards.  Fixed
versions are available on my WWW page, or via e-mail if you don't have WWW
access.”h]”hXd  You can get the Crynwr packet driver collection (including arcether.com, the
one youâ€™ll want to use with ARCnet cards) from
oak.oakland.edu:/simtel/msdos/pktdrvr. It wonâ€™t work perfectly on a 386+
without patches, though, and also doesnâ€™t like several cards.  Fixed
versions are available on my WWW page, or via e-mail if you donâ€™t have WWW
access.”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kehj†  hžhubeh}”(h]”Œother-drivers-and-info”ah ]”h"]”Œother drivers and info”ah$]”h&]”uh1h´hh¶hžhhŸh³h KQubhµ)”}”(hhh]”(hº)”}”(hŒInstalling the Driver”h]”hŒInstalling the Driver”…””}”(hjS  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjP  hžhhŸh³h KnubhÐ)”}”(hŒ;All you will need to do in order to install the driver is::”h]”hŒ:All you will need to do in order to install the driver is:”…””}”(hja  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KphjP  hžhubhô)”}”(hŒ…make config
        (be sure to choose ARCnet in the network devices
        and at least one chipset driver.)
make clean
make zImage”h]”hŒ…make config
        (be sure to choose ARCnet in the network devices
        and at least one chipset driver.)
make clean
make zImage”…””}”hjo  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h KrhjP  hžhubhÐ)”}”(hŒ´If you obtained this ARCnet package as an upgrade to the ARCnet driver in
your current kernel, you will need to first copy arcnet.c over the one in
the linux/drivers/net directory.”h]”hŒ´If you obtained this ARCnet package as an upgrade to the ARCnet driver in
your current kernel, you will need to first copy arcnet.c over the one in
the linux/drivers/net directory.”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KxhjP  hžhubhÐ)”}”(hŒyYou will know the driver is installed properly if you get some ARCnet
messages when you reboot into the new Linux kernel.”h]”hŒyYou will know the driver is installed properly if you get some ARCnet
messages when you reboot into the new Linux kernel.”…””}”(hj‹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K|hjP  hžhubhÐ)”}”(hŒThere are four chipset options:”h]”hŒThere are four chipset options:”…””}”(hj™  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhjP  hžhubj%  )”}”(hŒ$1. Standard ARCnet COM90xx chipset.
”h]”hŒenumerated_list”“”)”}”(hhh]”hŒ	list_item”“”)”}”(hŒ!Standard ARCnet COM90xx chipset.
”h]”hÐ)”}”(hŒ Standard ARCnet COM90xx chipset.”h]”hŒ Standard ARCnet COM90xx chipset.”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj²  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°  hj­  ubah}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1j«  hj§  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h KhjP  hžhubhÐ)”}”(hŒ¹This is the normal ARCnet card, which you've probably got. This is the only
chipset driver which will autoprobe if not told where the card is.
It following options on the command line::”h]”hŒºThis is the normal ARCnet card, which youâ€™ve probably got. This is the only
chipset driver which will autoprobe if not told where the card is.
It following options on the command line:”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KƒhjP  hžhubhô)”}”(hŒ2com90xx=[<io>[,<irq>[,<shmem>]]][,<name>] | <name>”h]”hŒ2com90xx=[<io>[,<irq>[,<shmem>]]][,<name>] | <name>”…””}”hjé  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h K‡hjP  hžhubhÐ)”}”(hŒ>If you load the chipset support as a module, the options are::”h]”hŒ=If you load the chipset support as a module, the options are:”…””}”(hj÷  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K‰hjP  hžhubhô)”}”(hŒ-io=<io> irq=<irq> shmem=<shmem> device=<name>”h]”hŒ-io=<io> irq=<irq> shmem=<shmem> device=<name>”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h K‹hjP  hžhubhÐ)”}”(hŒ—To disable the autoprobe, just specify "com90xx=" on the kernel command line.
To specify the name alone, but allow autoprobe, just put "com90xx=<name>"”h]”hŒŸTo disable the autoprobe, just specify â€œcom90xx=â€ on the kernel command line.
To specify the name alone, but allow autoprobe, just put â€œcom90xx=<name>â€”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhjP  hžhubj%  )”}”(hŒ2. ARCnet COM20020 chipset.
”h]”j¬  )”}”(hhh]”j±  )”}”(hŒARCnet COM20020 chipset.
”h]”hÐ)”}”(hŒARCnet COM20020 chipset.”h]”hŒARCnet COM20020 chipset.”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj(  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°  hj%  ubah}”(h]”h ]”h"]”h$]”h&]”jÐ  jÑ  jÒ  hjÓ  jÔ  Œstart”Kuh1j«  hj!  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h KhjP  hžhubhÐ)”}”(hX   This is the new chipset from SMC with support for promiscuous mode (packet
sniffing), extra diagnostic information, etc. Unfortunately, there is no
sensible method of autoprobing for these cards. You must specify the I/O
address on the kernel command line.”h]”hX   This is the new chipset from SMC with support for promiscuous mode (packet
sniffing), extra diagnostic information, etc. Unfortunately, there is no
sensible method of autoprobing for these cards. You must specify the I/O
address on the kernel command line.”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K’hjP  hžhubhÐ)”}”(hŒThe command line options are::”h]”hŒThe command line options are:”…””}”(hj[  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K—hjP  hžhubhô)”}”(hŒDcom20020=<io>[,<irq>[,<node_ID>[,backplane[,CKP[,timeout]]]]][,name]”h]”hŒDcom20020=<io>[,<irq>[,<node_ID>[,backplane[,CKP[,timeout]]]]][,name]”…””}”hji  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h K™hjP  hžhubhÐ)”}”(hŒ>If you load the chipset support as a module, the options are::”h]”hŒ=If you load the chipset support as a module, the options are:”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K›hjP  hžhubhô)”}”(hŒbio=<io> irq=<irq> node=<node_ID> backplane=<backplane> clock=<CKP>
timeout=<timeout> device=<name>”h]”hŒbio=<io> irq=<irq> node=<node_ID> backplane=<backplane> clock=<CKP>
timeout=<timeout> device=<name>”…””}”hj…  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h KhjP  hžhubhÐ)”}”(hX  The COM20020 chipset allows you to set the node ID in software, overriding the
default which is still set in DIP switches on the card. If you don't have the
COM20020 data sheets, and you don't know what the other three options refer
to, then they won't interest you - forget them.”h]”hX  The COM20020 chipset allows you to set the node ID in software, overriding the
default which is still set in DIP switches on the card. If you donâ€™t have the
COM20020 data sheets, and you donâ€™t know what the other three options refer
to, then they wonâ€™t interest you - forget them.”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K hjP  hžhubj%  )”}”(hŒ-3. ARCnet COM90xx chipset in IO-mapped mode.
”h]”j¬  )”}”(hhh]”j±  )”}”(hŒ*ARCnet COM90xx chipset in IO-mapped mode.
”h]”hÐ)”}”(hŒ)ARCnet COM90xx chipset in IO-mapped mode.”h]”hŒ)ARCnet COM90xx chipset in IO-mapped mode.”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K¥hj¨  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°  hj¥  ubah}”(h]”h ]”h"]”h$]”h&]”jÐ  jÑ  jÒ  hjÓ  jÔ  jF  Kuh1j«  hj¡  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h K¥hjP  hžhubhÐ)”}”(hX™  This will also work with the normal ARCnet cards, but doesn't use the shared
memory. It performs less well than the above driver, but is provided in case
you have a card which doesn't support shared memory, or (strangely) in case
you have so many ARCnet cards in your machine that you run out of shmem slots.
If you don't give the IO address on the kernel command line, then the driver
will not find the card.”h]”hXŸ  This will also work with the normal ARCnet cards, but doesnâ€™t use the shared
memory. It performs less well than the above driver, but is provided in case
you have a card which doesnâ€™t support shared memory, or (strangely) in case
you have so many ARCnet cards in your machine that you run out of shmem slots.
If you donâ€™t give the IO address on the kernel command line, then the driver
will not find the card.”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K§hjP  hžhubhÐ)”}”(hŒThe command line options are::”h]”hŒThe command line options are:”…””}”(hjÚ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K®hjP  hžhubhô)”}”(hŒcom90io=<io>[,<irq>][,<name>]”h]”hŒcom90io=<io>[,<irq>][,<name>]”…””}”hjè  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h K°hjP  hžhubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒvIf you load the chipset support as a module, the options are:
io=<io> irq=<irq> device=<name>

4. ARCnet RIM I cards.
”h]”(hŒterm”“”)”}”(hŒ=If you load the chipset support as a module, the options are:”h]”hŒ=If you load the chipset support as a module, the options are:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Kµhjý  ubhŒ
definition”“”)”}”(hhh]”(hÐ)”}”(hŒio=<io> irq=<irq> device=<name>”h]”hŒio=<io> irq=<irq> device=<name>”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K³hj  ubj¬  )”}”(hhh]”j±  )”}”(hŒARCnet RIM I cards.
”h]”hÐ)”}”(hŒARCnet RIM I cards.”h]”hŒARCnet RIM I cards.”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kµhj'  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°  hj$  ubah}”(h]”h ]”h"]”h$]”h&]”jÐ  jÑ  jÒ  hjÓ  jÔ  jF  Kuh1j«  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjý  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h Kµhjø  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jö  hjP  hžhhŸNh NubhÐ)”}”(hŒïThese are COM90xx chips which are _completely_ memory mapped. The support for
these is not tested. If you have one, please mail the author with a success
report. All options must be specified, except the device name.
Command line options::”h]”hŒîThese are COM90xx chips which are _completely_ memory mapped. The support for
these is not tested. If you have one, please mail the author with a success
report. All options must be specified, except the device name.
Command line options:”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K·hjP  hžhubhô)”}”(hŒ(arcrimi=<shmem>,<irq>,<node_ID>[,<name>]”h]”hŒ(arcrimi=<shmem>,<irq>,<node_ID>[,<name>]”…””}”hje  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h K¼hjP  hžhubhÐ)”}”(hŒ>If you load the chipset support as a module, the options are::”h]”hŒ=If you load the chipset support as a module, the options are:”…””}”(hjs  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K¾hjP  hžhubhô)”}”(hŒ4shmem=<shmem> irq=<irq> node=<node_ID> device=<name>”h]”hŒ4shmem=<shmem> irq=<irq> node=<node_ID> device=<name>”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h KÀhjP  hžhubeh}”(h]”Œinstalling-the-driver”ah ]”h"]”Œinstalling the driver”ah$]”h&]”uh1h´hh¶hžhhŸh³h Knubhµ)”}”(hhh]”(hº)”}”(hŒLoadable Module Support”h]”hŒLoadable Module Support”…””}”(hjš  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj—  hžhhŸh³h KÄubhÐ)”}”(hŒüConfigure and rebuild Linux.  When asked, answer 'm' to "Generic ARCnet
support" and to support for your ARCnet chipset if you want to use the
loadable module. You can also say 'y' to "Generic ARCnet support" and 'm'
to the chipset support if you wish.”h]”hX  Configure and rebuild Linux.  When asked, answer â€˜mâ€™ to â€œGeneric ARCnet
supportâ€ and to support for your ARCnet chipset if you want to use the
loadable module. You can also say â€˜yâ€™ to â€œGeneric ARCnet supportâ€ and â€˜mâ€™
to the chipset support if you wish.”…””}”(hj¨  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KÆhj—  hžhubhô)”}”(hŒ/make config
make clean
make zImage
make modules”h]”hŒ/make config
make clean
make zImage
make modules”…””}”hj¶  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h KÍhj—  hžhubhÐ)”}”(hX  If you're using a loadable module, you need to use insmod to load it, and
you can specify various characteristics of your card on the command
line.  (In recent versions of the driver, autoprobing is much more reliable
and works as a module, so most of this is now unnecessary.)”h]”hX  If youâ€™re using a loadable module, you need to use insmod to load it, and
you can specify various characteristics of your card on the command
line.  (In recent versions of the driver, autoprobing is much more reliable
and works as a module, so most of this is now unnecessary.)”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KÒhj—  hžhubhÐ)”}”(hŒFor example::”h]”hŒFor example:”…””}”(hjÒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K×hj—  hžhubhô)”}”(hŒacd /usr/src/linux/modules
insmod arcnet.o
insmod com90xx.o
insmod com20020.o io=0x2e0 device=eth1”h]”hŒacd /usr/src/linux/modules
insmod arcnet.o
insmod com90xx.o
insmod com20020.o io=0x2e0 device=eth1”…””}”hjà  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h KÙhj—  hžhubeh}”(h]”Œloadable-module-support”ah ]”h"]”Œloadable module support”ah$]”h&]”uh1h´hh¶hžhhŸh³h KÄubhµ)”}”(hhh]”(hº)”}”(hŒUsing the Driver”h]”hŒUsing the Driver”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjö  hžhhŸh³h KàubhÐ)”}”(hX  If you build your kernel with ARCnet COM90xx support included, it should
probe for your card automatically when you boot. If you use a different
chipset driver complied into the kernel, you must give the necessary options
on the kernel command line, as detailed above.”h]”hX  If you build your kernel with ARCnet COM90xx support included, it should
probe for your card automatically when you boot. If you use a different
chipset driver complied into the kernel, you must give the necessary options
on the kernel command line, as detailed above.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kâhjö  hžhubhÐ)”}”(hŒÁGo read the NET-2-HOWTO and ETHERNET-HOWTO for Linux; they should be
available where you picked up this driver.  Think of your ARCnet as a
souped-up (or down, as the case may be) Ethernet card.”h]”hŒÁGo read the NET-2-HOWTO and ETHERNET-HOWTO for Linux; they should be
available where you picked up this driver.  Think of your ARCnet as a
souped-up (or down, as the case may be) Ethernet card.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kçhjö  hžhubhÐ)”}”(hŒ¢By the way, be sure to change all references from "eth0" to "arc0" in the
HOWTOs.  Remember that ARCnet isn't a "true" Ethernet, and the device name
is DIFFERENT.”h]”hŒ°By the way, be sure to change all references from â€œeth0â€ to â€œarc0â€ in the
HOWTOs.  Remember that ARCnet isnâ€™t a â€œtrueâ€ Ethernet, and the device name
is DIFFERENT.”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Këhjö  hžhubeh}”(h]”Œusing-the-driver”ah ]”h"]”Œusing the driver”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kàubhµ)”}”(hhh]”(hº)”}”(hŒMultiple Cards in One Computer”h]”hŒMultiple Cards in One Computer”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj9  hžhhŸh³h KñubhÐ)”}”(hŒÞLinux has pretty good support for this now, but since I've been busy, the
ARCnet driver has somewhat suffered in this respect. COM90xx support, if
compiled into the kernel, will (try to) autodetect all the installed cards.”h]”hŒàLinux has pretty good support for this now, but since Iâ€™ve been busy, the
ARCnet driver has somewhat suffered in this respect. COM90xx support, if
compiled into the kernel, will (try to) autodetect all the installed cards.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kóhj9  hžhubhÐ)”}”(hŒ‡If you have other cards, with support compiled into the kernel, then you can
just repeat the options on the kernel command line, e.g.::”h]”hŒ†If you have other cards, with support compiled into the kernel, then you can
just repeat the options on the kernel command line, e.g.:”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K÷hj9  hžhubhô)”}”(hŒ7LILO: linux com20020=0x2e0 com20020=0x380 com90io=0x260”h]”hŒ7LILO: linux com20020=0x2e0 com20020=0x380 com90io=0x260”…””}”hjf  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h Kúhj9  hžhubhÐ)”}”(hŒeIf you have the chipset support built as a loadable module, then you need to
do something like this::”h]”hŒdIf you have the chipset support built as a loadable module, then you need to
do something like this:”…””}”(hjt  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kühj9  hžhubhô)”}”(hŒNinsmod -o arc0 com90xx
insmod -o arc1 com20020 io=0x2e0
insmod -o arc2 com90xx”h]”hŒNinsmod -o arc0 com90xx
insmod -o arc1 com20020 io=0x2e0
insmod -o arc2 com90xx”…””}”hj‚  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h Kÿhj9  hžhubhÐ)”}”(hŒ?The ARCnet drivers will now sort out their names automatically.”h]”hŒ?The ARCnet drivers will now sort out their names automatically.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj9  hžhubeh}”(h]”Œmultiple-cards-in-one-computer”ah ]”h"]”Œmultiple cards in one computer”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kñubhµ)”}”(hhh]”(hº)”}”(hŒ How do I get it to work with...?”h]”hŒ How do I get it to work with...?”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¦  hžhhŸh³h Mubj÷  )”}”(hhh]”(jü  )”}”(hX™  NFS:
Should be fine linux->linux, just pretend you're using Ethernet cards.
oak.oakland.edu:/simtel/msdos/nfs has some nice DOS clients.  There
is also a DOS-based NFS server called SOSS.  It doesn't multitask
quite the way Linux does (actually, it doesn't multitask AT ALL) but
you never know what you might need.

With AmiTCP (and possibly others), you may need to set the following
options in your Amiga nfstab:  MD 1024 MR 1024 MW 1024
(Thanks to Christian Gottschling <ferksy@indigo.tng.oche.de>
for this.)

Probably these refer to maximum NFS data/read/write block sizes.  I
don't know why the defaults on the Amiga didn't work; write to me if
you know more.
”h]”(j  )”}”(hŒNFS:”h]”hŒNFS:”…””}”(hj¾  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Mhjº  ubj  )”}”(hhh]”(hÐ)”}”(hX5  Should be fine linux->linux, just pretend you're using Ethernet cards.
oak.oakland.edu:/simtel/msdos/nfs has some nice DOS clients.  There
is also a DOS-based NFS server called SOSS.  It doesn't multitask
quite the way Linux does (actually, it doesn't multitask AT ALL) but
you never know what you might need.”h]”hX;  Should be fine linux->linux, just pretend youâ€™re using Ethernet cards.
oak.oakland.edu:/simtel/msdos/nfs has some nice DOS clients.  There
is also a DOS-based NFS server called SOSS.  It doesnâ€™t multitask
quite the way Linux does (actually, it doesnâ€™t multitask AT ALL) but
you never know what you might need.”…””}”(hjÏ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M
hjÌ  ubhÐ)”}”(hŒÃWith AmiTCP (and possibly others), you may need to set the following
options in your Amiga nfstab:  MD 1024 MR 1024 MW 1024
(Thanks to Christian Gottschling <ferksy@indigo.tng.oche.de>
for this.)”h]”(hŒžWith AmiTCP (and possibly others), you may need to set the following
options in your Amiga nfstab:  MD 1024 MR 1024 MW 1024
(Thanks to Christian Gottschling <”…””}”(hjÝ  hžhhŸNh Nubjt  )”}”(hŒferksy@indigo.tng.oche.de”h]”hŒferksy@indigo.tng.oche.de”…””}”(hjå  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ mailto:ferksy@indigo.tng.oche.de”uh1js  hjÝ  ubhŒ>
for this.)”…””}”(hjÝ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MhjÌ  ubhÐ)”}”(hŒ—Probably these refer to maximum NFS data/read/write block sizes.  I
don't know why the defaults on the Amiga didn't work; write to me if
you know more.”h]”hŒ›Probably these refer to maximum NFS data/read/write block sizes.  I
donâ€™t know why the defaults on the Amiga didnâ€™t work; write to me if
you know more.”…””}”(hjÿ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MhjÌ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjº  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h Mhj·  ubjü  )”}”(hX  DOS:
If you're using the freeware arcether.com, you might want to install
the driver patch from my web page.  It helps with PC/TCP, and also
can get arcether to load if it timed out too quickly during
initialization.  In fact, if you use it on a 386+ you REALLY need
the patch, really.
”h]”(j  )”}”(hŒDOS:”h]”hŒDOS:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Mhj  ubj  )”}”(hhh]”hÐ)”}”(hX  If you're using the freeware arcether.com, you might want to install
the driver patch from my web page.  It helps with PC/TCP, and also
can get arcether to load if it timed out too quickly during
initialization.  In fact, if you use it on a 386+ you REALLY need
the patch, really.”h]”hX  If youâ€™re using the freeware arcether.com, you might want to install
the driver patch from my web page.  It helps with PC/TCP, and also
can get arcether to load if it timed out too quickly during
initialization.  In fact, if you use it on a 386+ you REALLY need
the patch, really.”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h Mhj·  hžhubjü  )”}”(hŒ‹Windows:
See DOS :)  Trumpet Winsock works fine with either the Novell or
Arcether client, assuming you remember to load winpkt of course.
”h]”(j  )”}”(hŒWindows:”h]”hŒWindows:”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h M"hjH  ubj  )”}”(hhh]”hÐ)”}”(hŒSee DOS :)  Trumpet Winsock works fine with either the Novell or
Arcether client, assuming you remember to load winpkt of course.”h]”hŒSee DOS :)  Trumpet Winsock works fine with either the Novell or
Arcether client, assuming you remember to load winpkt of course.”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M!hjZ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjH  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h M"hj·  hžhubjü  )”}”(hX   LAN Manager and Windows for Workgroups:
These programs use protocols that
are incompatible with the Internet standard.  They try to pretend
the cards are Ethernet, and confuse everyone else on the network.

However, v2.00 and higher of the Linux ARCnet driver supports this
protocol via the 'arc0e' device.  See the section on "Multiprotocol
Support" for more information.

Using the freeware Samba server and clients for Linux, you can now
interface quite nicely with TCP/IP-based WfWg or Lan Manager
networks.
”h]”(j  )”}”(hŒ'LAN Manager and Windows for Workgroups:”h]”hŒ'LAN Manager and Windows for Workgroups:”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h M/hjw  ubj  )”}”(hhh]”(hÐ)”}”(hŒ¥These programs use protocols that
are incompatible with the Internet standard.  They try to pretend
the cards are Ethernet, and confuse everyone else on the network.”h]”hŒ¥These programs use protocols that
are incompatible with the Internet standard.  They try to pretend
the cards are Ethernet, and confuse everyone else on the network.”…””}”(hjŒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M%hj‰  ubhÐ)”}”(hŒ¥However, v2.00 and higher of the Linux ARCnet driver supports this
protocol via the 'arc0e' device.  See the section on "Multiprotocol
Support" for more information.”h]”hŒ­However, v2.00 and higher of the Linux ARCnet driver supports this
protocol via the â€˜arc0eâ€™ device.  See the section on â€œMultiprotocol
Supportâ€ for more information.”…””}”(hjš  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M)hj‰  ubhÐ)”}”(hŒ‰Using the freeware Samba server and clients for Linux, you can now
interface quite nicely with TCP/IP-based WfWg or Lan Manager
networks.”h]”hŒ‰Using the freeware Samba server and clients for Linux, you can now
interface quite nicely with TCP/IP-based WfWg or Lan Manager
networks.”…””}”(hj¨  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M-hj‰  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjw  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h M/hj·  hžhubjü  )”}”(hXÆ  Windows 95:
Tools are included with Win95 that let you use either the LANMAN
style network drivers (NDIS) or Novell drivers (ODI) to handle your
ARCnet packets.  If you use ODI, you'll need to use the 'arc0'
device with Linux.  If you use NDIS, then try the 'arc0e' device.
See the "Multiprotocol Support" section below if you need arc0e,
you're completely insane, and/or you need to build some kind of
hybrid network that uses both encapsulation types.
”h]”(j  )”}”(hŒWindows 95:”h]”hŒWindows 95:”…””}”(hjÆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h M8hjÂ  ubj  )”}”(hhh]”hÐ)”}”(hX¹  Tools are included with Win95 that let you use either the LANMAN
style network drivers (NDIS) or Novell drivers (ODI) to handle your
ARCnet packets.  If you use ODI, you'll need to use the 'arc0'
device with Linux.  If you use NDIS, then try the 'arc0e' device.
See the "Multiprotocol Support" section below if you need arc0e,
you're completely insane, and/or you need to build some kind of
hybrid network that uses both encapsulation types.”h]”hXÉ  Tools are included with Win95 that let you use either the LANMAN
style network drivers (NDIS) or Novell drivers (ODI) to handle your
ARCnet packets.  If you use ODI, youâ€™ll need to use the â€˜arc0â€™
device with Linux.  If you use NDIS, then try the â€˜arc0eâ€™ device.
See the â€œMultiprotocol Supportâ€ section below if you need arc0e,
youâ€™re completely insane, and/or you need to build some kind of
hybrid network that uses both encapsulation types.”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M2hjÔ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjÂ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h M8hj·  hžhubjü  )”}”(hX¼  OS/2:
I've been told it works under Warp Connect with an ARCnet driver from
SMC.  You need to use the 'arc0e' interface for this.  If you get
the SMC driver to work with the TCP/IP stuff included in the
"normal" Warp Bonus Pack, let me know.

ftp.microsoft.com also has a freeware "Lan Manager for OS/2" client
which should use the same protocol as WfWg does.  I had no luck
installing it under Warp, however.  Please mail me with any results.
”h]”(j  )”}”(hŒOS/2:”h]”hŒOS/2:”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h MBhjñ  ubj  )”}”(hhh]”(hÐ)”}”(hŒëI've been told it works under Warp Connect with an ARCnet driver from
SMC.  You need to use the 'arc0e' interface for this.  If you get
the SMC driver to work with the TCP/IP stuff included in the
"normal" Warp Bonus Pack, let me know.”h]”hŒõIâ€™ve been told it works under Warp Connect with an ARCnet driver from
SMC.  You need to use the â€˜arc0eâ€™ interface for this.  If you get
the SMC driver to work with the TCP/IP stuff included in the
â€œnormalâ€ Warp Bonus Pack, let me know.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M;hj  ubhÐ)”}”(hŒÈftp.microsoft.com also has a freeware "Lan Manager for OS/2" client
which should use the same protocol as WfWg does.  I had no luck
installing it under Warp, however.  Please mail me with any results.”h]”hŒÌftp.microsoft.com also has a freeware â€œLan Manager for OS/2â€ client
which should use the same protocol as WfWg does.  I had no luck
installing it under Warp, however.  Please mail me with any results.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M@hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjñ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h MBhj·  hžhubjü  )”}”(hX  NetBSD/AmiTCP:
These use an old version of the Internet standard ARCnet
protocol (RFC1051) which is compatible with the Linux driver v2.10
ALPHA and above using the arc0s device. (See "Multiprotocol ARCnet"
below.)  ** Newer versions of NetBSD apparently support RFC1201.

”h]”(j  )”}”(hŒNetBSD/AmiTCP:”h]”hŒNetBSD/AmiTCP:”…””}”(hj2  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h MIhj.  ubj  )”}”(hhh]”hÐ)”}”(hX   These use an old version of the Internet standard ARCnet
protocol (RFC1051) which is compatible with the Linux driver v2.10
ALPHA and above using the arc0s device. (See "Multiprotocol ARCnet"
below.)  ** Newer versions of NetBSD apparently support RFC1201.”h]”hX  These use an old version of the Internet standard ARCnet
protocol (RFC1051) which is compatible with the Linux driver v2.10
ALPHA and above using the arc0s device. (See â€œMultiprotocol ARCnetâ€
below.)  ** Newer versions of NetBSD apparently support RFC1201.”…””}”(hjC  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MEhj@  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj.  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh³h MIhj·  hžhubeh}”(h]”h ]”h"]”h$]”h&]”uh1jö  hj¦  hžhhŸh³h Nubeh}”(h]”Œhow-do-i-get-it-to-work-with”ah ]”h"]”Œ how do i get it to work with...?”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒUsing Multiprotocol ARCnet”h]”hŒUsing Multiprotocol ARCnet”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjk  hžhhŸh³h MLubhÐ)”}”(hŒaThe ARCnet driver v2.10 ALPHA supports three protocols, each on its own
"virtual network device":”h]”hŒeThe ARCnet driver v2.10 ALPHA supports three protocols, each on its own
â€œvirtual network deviceâ€:”…””}”(hj|  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MNhjk  hžhubj%  )”}”(hXY  ======  ===============================================================
arc0    RFC1201 protocol, the official Internet standard which just
        happens to be 100% compatible with Novell's TRXNET driver.
        Version 1.00 of the ARCnet driver supported _only_ this
        protocol.  arc0 is the fastest of the three protocols (for
        whatever reason), and allows larger packets to be used
        because it supports RFC1201 "packet splitting" operations.
        Unless you have a specific need to use a different protocol,
        I strongly suggest that you stick with this one.

arc0e   "Ethernet-Encapsulation" which sends packets over ARCnet
        that are actually a lot like Ethernet packets, including the
        6-byte hardware addresses.  This protocol is compatible with
        Microsoft's NDIS ARCnet driver, like the one in WfWg and
        LANMAN.  Because the MTU of 493 is actually smaller than the
        one "required" by TCP/IP (576), there is a chance that some
        network operations will not function properly.  The Linux
        TCP/IP layer can compensate in most cases, however, by
        automatically fragmenting the TCP/IP packets to make them
        fit.  arc0e also works slightly more slowly than arc0, for
        reasons yet to be determined.  (Probably it's the smaller
        MTU that does it.)

arc0s   The "[s]imple" RFC1051 protocol is the "previous" Internet
        standard that is completely incompatible with the new
        standard.  Some software today, however, continues to
        support the old standard (and only the old standard)
        including NetBSD and AmiTCP.  RFC1051 also does not support
        RFC1201's packet splitting, and the MTU of 507 is still
        smaller than the Internet "requirement," so it's quite
        possible that you may run into problems.  It's also slower
        than RFC1201 by about 25%, for the same reason as arc0e.

        The arc0s support was contributed by Tomasz Motylewski
        and modified somewhat by me.  Bugs are probably my fault.
======  ===============================================================
”h]”hŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j˜  hj•  ubj™  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K?uh1j˜  hj•  ubhŒtbody”“”)”}”(hhh]”(hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hÐ)”}”(hŒarc0”h]”hŒarc0”…””}”(hj½  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MRhjº  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¸  hjµ  ubj¹  )”}”(hhh]”hÐ)”}”(hXÉ  RFC1201 protocol, the official Internet standard which just
happens to be 100% compatible with Novell's TRXNET driver.
Version 1.00 of the ARCnet driver supported _only_ this
protocol.  arc0 is the fastest of the three protocols (for
whatever reason), and allows larger packets to be used
because it supports RFC1201 "packet splitting" operations.
Unless you have a specific need to use a different protocol,
I strongly suggest that you stick with this one.”h]”hXÏ  RFC1201 protocol, the official Internet standard which just
happens to be 100% compatible with Novellâ€™s TRXNET driver.
Version 1.00 of the ARCnet driver supported _only_ this
protocol.  arc0 is the fastest of the three protocols (for
whatever reason), and allows larger packets to be used
because it supports RFC1201 â€œpacket splittingâ€ operations.
Unless you have a specific need to use a different protocol,
I strongly suggest that you stick with this one.”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MRhjÑ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¸  hjµ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j³  hj°  ubj´  )”}”(hhh]”(j¹  )”}”(hhh]”hÐ)”}”(hŒarc0e”h]”hŒarc0e”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M[hjñ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¸  hjî  ubj¹  )”}”(hhh]”hÐ)”}”(hX—  "Ethernet-Encapsulation" which sends packets over ARCnet
that are actually a lot like Ethernet packets, including the
6-byte hardware addresses.  This protocol is compatible with
Microsoft's NDIS ARCnet driver, like the one in WfWg and
LANMAN.  Because the MTU of 493 is actually smaller than the
one "required" by TCP/IP (576), there is a chance that some
network operations will not function properly.  The Linux
TCP/IP layer can compensate in most cases, however, by
automatically fragmenting the TCP/IP packets to make them
fit.  arc0e also works slightly more slowly than arc0, for
reasons yet to be determined.  (Probably it's the smaller
MTU that does it.)”h]”hX£  â€œEthernet-Encapsulationâ€ which sends packets over ARCnet
that are actually a lot like Ethernet packets, including the
6-byte hardware addresses.  This protocol is compatible with
Microsoftâ€™s NDIS ARCnet driver, like the one in WfWg and
LANMAN.  Because the MTU of 493 is actually smaller than the
one â€œrequiredâ€ by TCP/IP (576), there is a chance that some
network operations will not function properly.  The Linux
TCP/IP layer can compensate in most cases, however, by
automatically fragmenting the TCP/IP packets to make them
fit.  arc0e also works slightly more slowly than arc0, for
reasons yet to be determined.  (Probably itâ€™s the smaller
MTU that does it.)”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M[hj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¸  hjî  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j³  hj°  ubj´  )”}”(hhh]”(j¹  )”}”(hhh]”hÐ)”}”(hŒarc0s”h]”hŒarc0s”…””}”(hj+	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhhj(	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¸  hj%	  ubj¹  )”}”(hhh]”(hÐ)”}”(hXú  The "[s]imple" RFC1051 protocol is the "previous" Internet
standard that is completely incompatible with the new
standard.  Some software today, however, continues to
support the old standard (and only the old standard)
including NetBSD and AmiTCP.  RFC1051 also does not support
RFC1201's packet splitting, and the MTU of 507 is still
smaller than the Internet "requirement," so it's quite
possible that you may run into problems.  It's also slower
than RFC1201 by about 25%, for the same reason as arc0e.”h]”hX  The â€œ[s]impleâ€ RFC1051 protocol is the â€œpreviousâ€ Internet
standard that is completely incompatible with the new
standard.  Some software today, however, continues to
support the old standard (and only the old standard)
including NetBSD and AmiTCP.  RFC1051 also does not support
RFC1201â€™s packet splitting, and the MTU of 507 is still
smaller than the Internet â€œrequirement,â€ so itâ€™s quite
possible that you may run into problems.  Itâ€™s also slower
than RFC1201 by about 25%, for the same reason as arc0e.”…””}”(hjB	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhhj?	  ubhÐ)”}”(hŒpThe arc0s support was contributed by Tomasz Motylewski
and modified somewhat by me.  Bugs are probably my fault.”h]”hŒpThe arc0s support was contributed by Tomasz Motylewski
and modified somewhat by me.  Bugs are probably my fault.”…””}”(hjP	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mrhj?	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¸  hj%	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j³  hj°  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j®  hj•  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j“  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ  hjŠ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h MQhjk  hžhubhÐ)”}”(hŒÇYou can choose not to compile arc0e and arc0s into the driver if you want -
this will save you a bit of memory and avoid confusion when eg. trying to
use the "NFS-root" stuff in recent Linux kernels.”h]”hŒËYou can choose not to compile arc0e and arc0s into the driver if you want -
this will save you a bit of memory and avoid confusion when eg. trying to
use the â€œNFS-rootâ€ stuff in recent Linux kernels.”…””}”(hjƒ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mvhjk  hžhubhÐ)”}”(hŒùThe arc0e and arc0s devices are created automatically when you first
ifconfig the arc0 device.  To actually use them, though, you need to also
ifconfig the other virtual devices you need.  There are a number of ways you
can set up your network then:”h]”hŒùThe arc0e and arc0s devices are created automatically when you first
ifconfig the arc0 device.  To actually use them, though, you need to also
ifconfig the other virtual devices you need.  There are a number of ways you
can set up your network then:”…””}”(hj‘	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mzhjk  hžhubj¬  )”}”(hhh]”(j±  )”}”(hXæ  Single Protocol.

This is the simplest way to configure your network: use just one of the
two available protocols.  As mentioned above, it's a good idea to use
only arc0 unless you have a good reason (like some other software, ie.
WfWg, that only works with arc0e).

If you need only arc0, then the following commands should get you going::

     ifconfig arc0 MY.IP.ADD.RESS
     route add MY.IP.ADD.RESS arc0
     route add -net SUB.NET.ADD.RESS arc0
     [add other local routes here]

If you need arc0e (and only arc0e), it's a little different::

     ifconfig arc0 MY.IP.ADD.RESS
     ifconfig arc0e MY.IP.ADD.RESS
     route add MY.IP.ADD.RESS arc0e
     route add -net SUB.NET.ADD.RESS arc0e

arc0s works much the same way as arc0e.

”h]”(hÐ)”}”(hŒSingle Protocol.”h]”hŒSingle Protocol.”…””}”(hj¦	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M€hj¢	  ubhÐ)”}”(hŒ÷This is the simplest way to configure your network: use just one of the
two available protocols.  As mentioned above, it's a good idea to use
only arc0 unless you have a good reason (like some other software, ie.
WfWg, that only works with arc0e).”h]”hŒùThis is the simplest way to configure your network: use just one of the
two available protocols.  As mentioned above, itâ€™s a good idea to use
only arc0 unless you have a good reason (like some other software, ie.
WfWg, that only works with arc0e).”…””}”(hj´	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M‚hj¢	  ubhÐ)”}”(hŒIIf you need only arc0, then the following commands should get you going::”h]”hŒHIf you need only arc0, then the following commands should get you going:”…””}”(hjÂ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M‡hj¢	  ubhô)”}”(hŒ}ifconfig arc0 MY.IP.ADD.RESS
route add MY.IP.ADD.RESS arc0
route add -net SUB.NET.ADD.RESS arc0
[add other local routes here]”h]”hŒ}ifconfig arc0 MY.IP.ADD.RESS
route add MY.IP.ADD.RESS arc0
route add -net SUB.NET.ADD.RESS arc0
[add other local routes here]”…””}”hjÐ	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h M‰hj¢	  ubhÐ)”}”(hŒ=If you need arc0e (and only arc0e), it's a little different::”h]”hŒ>If you need arc0e (and only arc0e), itâ€™s a little different:”…””}”(hjÞ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MŽhj¢	  ubhô)”}”(hŒifconfig arc0 MY.IP.ADD.RESS
ifconfig arc0e MY.IP.ADD.RESS
route add MY.IP.ADD.RESS arc0e
route add -net SUB.NET.ADD.RESS arc0e”h]”hŒifconfig arc0 MY.IP.ADD.RESS
ifconfig arc0e MY.IP.ADD.RESS
route add MY.IP.ADD.RESS arc0e
route add -net SUB.NET.ADD.RESS arc0e”…””}”hjì	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h Mhj¢	  ubhÐ)”}”(hŒ'arc0s works much the same way as arc0e.”h]”hŒ'arc0s works much the same way as arc0e.”…””}”(hjú	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M•hj¢	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hjŸ	  hžhhŸh³h Nubj±  )”}”(hXÛ  More than one protocol on the same wire.

Now things start getting confusing.  To even try it, you may need to be
partly crazy.  Here's what *I* did. :) Note that I don't include arc0s in
my home network; I don't have any NetBSD or AmiTCP computers, so I only
use arc0s during limited testing.

I have three computers on my home network; two Linux boxes (which prefer
RFC1201 protocol, for reasons listed above), and one XT that can't run
Linux but runs the free Microsoft LANMAN Client instead.

Worse, one of the Linux computers (freedom) also has a modem and acts as
a router to my Internet provider.  The other Linux box (insight) also has
its own IP address and needs to use freedom as its default gateway.  The
XT (patience), however, does not have its own Internet IP address and so
I assigned it one on a "private subnet" (as defined by RFC1597).

To start with, take a simple network with just insight and freedom.
Insight needs to:

     - talk to freedom via RFC1201 (arc0) protocol, because I like it
       more and it's faster.
     - use freedom as its Internet gateway.

That's pretty easy to do.  Set up insight like this::

     ifconfig arc0 insight
     route add insight arc0
     route add freedom arc0  /* I would use the subnet here (like I said
                                     to in "single protocol" above),
                                     but the rest of the subnet
                                     unfortunately lies across the PPP
                                     link on freedom, which confuses
                                     things. */
     route add default gw freedom

And freedom gets configured like so::

     ifconfig arc0 freedom
     route add freedom arc0
     route add insight arc0
     /* and default gateway is configured by pppd */

Great, now insight talks to freedom directly on arc0, and sends packets
to the Internet through freedom.  If you didn't know how to do the above,
you should probably stop reading this section now because it only gets
worse.

Now, how do I add patience into the network?  It will be using LANMAN
Client, which means I need the arc0e device.  It needs to be able to talk
to both insight and freedom, and also use freedom as a gateway to the
Internet.  (Recall that patience has a "private IP address" which won't
work on the Internet; that's okay, I configured Linux IP masquerading on
freedom for this subnet).

So patience (necessarily; I don't have another IP number from my
provider) has an IP address on a different subnet than freedom and
insight, but needs to use freedom as an Internet gateway.  Worse, most
DOS networking programs, including LANMAN, have braindead networking
schemes that rely completely on the netmask and a 'default gateway' to
determine how to route packets.  This means that to get to freedom or
insight, patience WILL send through its default gateway, regardless of
the fact that both freedom and insight (courtesy of the arc0e device)
could understand a direct transmission.

I compensate by giving freedom an extra IP address - aliased 'gatekeeper' -
that is on my private subnet, the same subnet that patience is on.  I
then define gatekeeper to be the default gateway for patience.

To configure freedom (in addition to the commands above)::

     ifconfig arc0e gatekeeper
     route add gatekeeper arc0e
     route add patience arc0e

This way, freedom will send all packets for patience through arc0e,
giving its IP address as gatekeeper (on the private subnet).  When it
talks to insight or the Internet, it will use its "freedom" Internet IP
address.

You will notice that we haven't configured the arc0e device on insight.
This would work, but is not really necessary, and would require me to
assign insight another special IP number from my private subnet.  Since
both insight and patience are using freedom as their default gateway, the
two can already talk to each other.

It's quite fortunate that I set things up like this the first time (cough
cough) because it's really handy when I boot insight into DOS.  There, it
runs the Novell ODI protocol stack, which only works with RFC1201 ARCnet.
In this mode it would be impossible for insight to communicate directly
with patience, since the Novell stack is incompatible with Microsoft's
Ethernet-Encap.  Without changing any settings on freedom or patience, I
simply set freedom as the default gateway for insight (now in DOS,
remember) and all the forwarding happens "automagically" between the two
hosts that would normally not be able to communicate at all.

For those who like diagrams, I have created two "virtual subnets" on the
same physical ARCnet wire.  You can picture it like this::


       [RFC1201 NETWORK]                   [ETHER-ENCAP NETWORK]
   (registered Internet subnet)           (RFC1597 private subnet)

                          (IP Masquerade)
       /---------------\         *            /---------------\
       |               |         *            |               |
       |               +-Freedom-*-Gatekeeper-+               |
       |               |    |    *            |               |
       \-------+-------/    |    *            \-------+-------/
               |            |                         |
            Insight         |                      Patience
                        (Internet)


”h]”(hÐ)”}”(hŒ(More than one protocol on the same wire.”h]”hŒ(More than one protocol on the same wire.”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M˜hj
  ubhÐ)”}”(hŒûNow things start getting confusing.  To even try it, you may need to be
partly crazy.  Here's what *I* did. :) Note that I don't include arc0s in
my home network; I don't have any NetBSD or AmiTCP computers, so I only
use arc0s during limited testing.”h]”(hŒeNow things start getting confusing.  To even try it, you may need to be
partly crazy.  Hereâ€™s what ”…””}”(hj 
  hžhhŸNh NubhŒemphasis”“”)”}”(hŒ*I*”h]”hŒI”…””}”(hj*
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j(
  hj 
  ubhŒ™ did. :) Note that I donâ€™t include arc0s in
my home network; I donâ€™t have any NetBSD or AmiTCP computers, so I only
use arc0s during limited testing.”…””}”(hj 
  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mšhj
  ubhÐ)”}”(hŒÈI have three computers on my home network; two Linux boxes (which prefer
RFC1201 protocol, for reasons listed above), and one XT that can't run
Linux but runs the free Microsoft LANMAN Client instead.”h]”hŒÊI have three computers on my home network; two Linux boxes (which prefer
RFC1201 protocol, for reasons listed above), and one XT that canâ€™t run
Linux but runs the free Microsoft LANMAN Client instead.”…””}”(hjB
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MŸhj
  ubhÐ)”}”(hXe  Worse, one of the Linux computers (freedom) also has a modem and acts as
a router to my Internet provider.  The other Linux box (insight) also has
its own IP address and needs to use freedom as its default gateway.  The
XT (patience), however, does not have its own Internet IP address and so
I assigned it one on a "private subnet" (as defined by RFC1597).”h]”hXi  Worse, one of the Linux computers (freedom) also has a modem and acts as
a router to my Internet provider.  The other Linux box (insight) also has
its own IP address and needs to use freedom as its default gateway.  The
XT (patience), however, does not have its own Internet IP address and so
I assigned it one on a â€œprivate subnetâ€ (as defined by RFC1597).”…””}”(hjP
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M£hj
  ubhÐ)”}”(hŒUTo start with, take a simple network with just insight and freedom.
Insight needs to:”h]”hŒUTo start with, take a simple network with just insight and freedom.
Insight needs to:”…””}”(hj^
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M©hj
  ubj%  )”}”(hŒ€- talk to freedom via RFC1201 (arc0) protocol, because I like it
  more and it's faster.
- use freedom as its Internet gateway.
”h]”hŒbullet_list”“”)”}”(hhh]”(j±  )”}”(hŒTtalk to freedom via RFC1201 (arc0) protocol, because I like it
more and it's faster.”h]”hÐ)”}”(hŒTtalk to freedom via RFC1201 (arc0) protocol, because I like it
more and it's faster.”h]”hŒVtalk to freedom via RFC1201 (arc0) protocol, because I like it
more and itâ€™s faster.”…””}”(hjy
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M¬hju
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°  hjr
  ubj±  )”}”(hŒ%use freedom as its Internet gateway.
”h]”hÐ)”}”(hŒ$use freedom as its Internet gateway.”h]”hŒ$use freedom as its Internet gateway.”…””}”(hj‘
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M®hj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°  hjr
  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jp
  hŸh³h M¬hjl
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h M¬hj
  ubhÐ)”}”(hŒ5That's pretty easy to do.  Set up insight like this::”h]”hŒ6Thatâ€™s pretty easy to do.  Set up insight like this:”…””}”(hj³
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M°hj
  ubhô)”}”(hXµ  ifconfig arc0 insight
route add insight arc0
route add freedom arc0  /* I would use the subnet here (like I said
                                to in "single protocol" above),
                                but the rest of the subnet
                                unfortunately lies across the PPP
                                link on freedom, which confuses
                                things. */
route add default gw freedom”h]”hXµ  ifconfig arc0 insight
route add insight arc0
route add freedom arc0  /* I would use the subnet here (like I said
                                to in "single protocol" above),
                                but the rest of the subnet
                                unfortunately lies across the PPP
                                link on freedom, which confuses
                                things. */
route add default gw freedom”…””}”hjÁ
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h M²hj
  ubhÐ)”}”(hŒ%And freedom gets configured like so::”h]”hŒ$And freedom gets configured like so:”…””}”(hjÏ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M¼hj
  ubhô)”}”(hŒsifconfig arc0 freedom
route add freedom arc0
route add insight arc0
/* and default gateway is configured by pppd */”•O      h]”hŒsifconfig arc0 freedom
route add freedom arc0
route add insight arc0
/* and default gateway is configured by pppd */”…””}”hjÝ
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h M¾hj
  ubhÐ)”}”(hŒßGreat, now insight talks to freedom directly on arc0, and sends packets
to the Internet through freedom.  If you didn't know how to do the above,
you should probably stop reading this section now because it only gets
worse.”h]”hŒáGreat, now insight talks to freedom directly on arc0, and sends packets
to the Internet through freedom.  If you didnâ€™t know how to do the above,
you should probably stop reading this section now because it only gets
worse.”…””}”(hjë
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÃhj
  ubhÐ)”}”(hX€  Now, how do I add patience into the network?  It will be using LANMAN
Client, which means I need the arc0e device.  It needs to be able to talk
to both insight and freedom, and also use freedom as a gateway to the
Internet.  (Recall that patience has a "private IP address" which won't
work on the Internet; that's okay, I configured Linux IP masquerading on
freedom for this subnet).”h]”hXˆ  Now, how do I add patience into the network?  It will be using LANMAN
Client, which means I need the arc0e device.  It needs to be able to talk
to both insight and freedom, and also use freedom as a gateway to the
Internet.  (Recall that patience has a â€œprivate IP addressâ€ which wonâ€™t
work on the Internet; thatâ€™s okay, I configured Linux IP masquerading on
freedom for this subnet).”…””}”(hjù
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÈhj
  ubhÐ)”}”(hXQ  So patience (necessarily; I don't have another IP number from my
provider) has an IP address on a different subnet than freedom and
insight, but needs to use freedom as an Internet gateway.  Worse, most
DOS networking programs, including LANMAN, have braindead networking
schemes that rely completely on the netmask and a 'default gateway' to
determine how to route packets.  This means that to get to freedom or
insight, patience WILL send through its default gateway, regardless of
the fact that both freedom and insight (courtesy of the arc0e device)
could understand a direct transmission.”h]”hXW  So patience (necessarily; I donâ€™t have another IP number from my
provider) has an IP address on a different subnet than freedom and
insight, but needs to use freedom as an Internet gateway.  Worse, most
DOS networking programs, including LANMAN, have braindead networking
schemes that rely completely on the netmask and a â€˜default gatewayâ€™ to
determine how to route packets.  This means that to get to freedom or
insight, patience WILL send through its default gateway, regardless of
the fact that both freedom and insight (courtesy of the arc0e device)
could understand a direct transmission.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÏhj
  ubhÐ)”}”(hŒÐI compensate by giving freedom an extra IP address - aliased 'gatekeeper' -
that is on my private subnet, the same subnet that patience is on.  I
then define gatekeeper to be the default gateway for patience.”h]”hŒÔI compensate by giving freedom an extra IP address - aliased â€˜gatekeeperâ€™ -
that is on my private subnet, the same subnet that patience is on.  I
then define gatekeeper to be the default gateway for patience.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÙhj
  ubhÐ)”}”(hŒ:To configure freedom (in addition to the commands above)::”h]”hŒ9To configure freedom (in addition to the commands above):”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÝhj
  ubhô)”}”(hŒMifconfig arc0e gatekeeper
route add gatekeeper arc0e
route add patience arc0e”h]”hŒMifconfig arc0e gatekeeper
route add gatekeeper arc0e
route add patience arc0e”…””}”hj1  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h Mßhj
  ubhÐ)”}”(hŒÚThis way, freedom will send all packets for patience through arc0e,
giving its IP address as gatekeeper (on the private subnet).  When it
talks to insight or the Internet, it will use its "freedom" Internet IP
address.”h]”hŒÞThis way, freedom will send all packets for patience through arc0e,
giving its IP address as gatekeeper (on the private subnet).  When it
talks to insight or the Internet, it will use its â€œfreedomâ€ Internet IP
address.”…””}”(hj?  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mãhj
  ubhÐ)”}”(hXC  You will notice that we haven't configured the arc0e device on insight.
This would work, but is not really necessary, and would require me to
assign insight another special IP number from my private subnet.  Since
both insight and patience are using freedom as their default gateway, the
two can already talk to each other.”h]”hXE  You will notice that we havenâ€™t configured the arc0e device on insight.
This would work, but is not really necessary, and would require me to
assign insight another special IP number from my private subnet.  Since
both insight and patience are using freedom as their default gateway, the
two can already talk to each other.”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mèhj
  ubhÐ)”}”(hX~  It's quite fortunate that I set things up like this the first time (cough
cough) because it's really handy when I boot insight into DOS.  There, it
runs the Novell ODI protocol stack, which only works with RFC1201 ARCnet.
In this mode it would be impossible for insight to communicate directly
with patience, since the Novell stack is incompatible with Microsoft's
Ethernet-Encap.  Without changing any settings on freedom or patience, I
simply set freedom as the default gateway for insight (now in DOS,
remember) and all the forwarding happens "automagically" between the two
hosts that would normally not be able to communicate at all.”h]”hXˆ  Itâ€™s quite fortunate that I set things up like this the first time (cough
cough) because itâ€™s really handy when I boot insight into DOS.  There, it
runs the Novell ODI protocol stack, which only works with RFC1201 ARCnet.
In this mode it would be impossible for insight to communicate directly
with patience, since the Novell stack is incompatible with Microsoftâ€™s
Ethernet-Encap.  Without changing any settings on freedom or patience, I
simply set freedom as the default gateway for insight (now in DOS,
remember) and all the forwarding happens â€œautomagicallyâ€ between the two
hosts that would normally not be able to communicate at all.”…””}”(hj[  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mîhj
  ubhÐ)”}”(hŒƒFor those who like diagrams, I have created two "virtual subnets" on the
same physical ARCnet wire.  You can picture it like this::”h]”hŒ†For those who like diagrams, I have created two â€œvirtual subnetsâ€ on the
same physical ARCnet wire.  You can picture it like this:”…””}”(hji  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Møhj
  ubhô)”}”(hXd      [RFC1201 NETWORK]                   [ETHER-ENCAP NETWORK]
(registered Internet subnet)           (RFC1597 private subnet)

                       (IP Masquerade)
    /---------------\         *            /---------------\
    |               |         *            |               |
    |               +-Freedom-*-Gatekeeper-+               |
    |               |    |    *            |               |
    \-------+-------/    |    *            \-------+-------/
            |            |                         |
         Insight         |                      Patience
                     (Internet)”h]”hXd      [RFC1201 NETWORK]                   [ETHER-ENCAP NETWORK]
(registered Internet subnet)           (RFC1597 private subnet)

                       (IP Masquerade)
    /---------------\         *            /---------------\
    |               |         *            |               |
    |               +-Freedom-*-Gatekeeper-+               |
    |               |    |    *            |               |
    \-------+-------/    |    *            \-------+-------/
            |            |                         |
         Insight         |                      Patience
                     (Internet)”…””}”hjw  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h Mühj
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hjŸ	  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jÐ  jÑ  jÒ  hjÓ  jÔ  uh1j«  hjk  hžhhŸh³h M€ubeh}”(h]”Œusing-multiprotocol-arcnet”ah ]”h"]”Œusing multiprotocol arcnet”ah$]”h&]”uh1h´hh¶hžhhŸh³h MLubhµ)”}”(hhh]”(hº)”}”(hŒIt works: what now?”h]”hŒIt works: what now?”…””}”(hjœ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj™  hžhhŸh³h MubhÐ)”}”(hŒÑSend mail describing your setup, preferably including driver version, kernel
version, ARCnet card model, CPU type, number of systems on your network, and
list of software in use to me at the following address:”h]”hŒÑSend mail describing your setup, preferably including driver version, kernel
version, ARCnet card model, CPU type, number of systems on your network, and
list of software in use to me at the following address:”…””}”(hjª  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj™  hžhubj%  )”}”(hŒapenwarr@worldvisions.ca
”h]”hÐ)”}”(hŒapenwarr@worldvisions.ca”h]”jt  )”}”(hj¾  h]”hŒapenwarr@worldvisions.ca”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:apenwarr@worldvisions.ca”uh1js  hj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj¸  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hŸh³h Mhj™  hžhubhÐ)”}”(hŒèI do send (sometimes automated) replies to all messages I receive.  My email
can be weird (and also usually gets forwarded all over the place along the
way to me), so if you don't get a reply within a reasonable time, please
resend.”h]”hŒêI do send (sometimes automated) replies to all messages I receive.  My email
can be weird (and also usually gets forwarded all over the place along the
way to me), so if you donâ€™t get a reply within a reasonable time, please
resend.”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj™  hžhubeh}”(h]”Œit-works-what-now”ah ]”h"]”Œit works: what now?”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒIt doesn't work: what now?”h]”hŒIt doesnâ€™t work: what now?”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjñ  hžhhŸh³h MubhÐ)”}”(hŒÙDo the same as above, but also include the output of the ifconfig and route
commands, as well as any pertinent log entries (ie. anything that starts
with "arcnet:" and has shown up since the last reboot) in your mail.”h]”hŒÝDo the same as above, but also include the output of the ifconfig and route
commands, as well as any pertinent log entries (ie. anything that starts
with â€œarcnet:â€ and has shown up since the last reboot) in your mail.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhjñ  hžhubhÐ)”}”(hXÚ  If you want to try fixing it yourself (I strongly recommend that you mail me
about the problem first, since it might already have been solved) you may
want to try some of the debug levels available.  For heavy testing on
D_DURING or more, it would be a REALLY good idea to kill your klogd daemon
first!  D_DURING displays 4-5 lines for each packet sent or received.  D_TX,
D_RX, and D_SKB actually DISPLAY each packet as it is sent or received,
which is obviously quite big.”h]”hXÚ  If you want to try fixing it yourself (I strongly recommend that you mail me
about the problem first, since it might already have been solved) you may
want to try some of the debug levels available.  For heavy testing on
D_DURING or more, it would be a REALLY good idea to kill your klogd daemon
first!  D_DURING displays 4-5 lines for each packet sent or received.  D_TX,
D_RX, and D_SKB actually DISPLAY each packet as it is sent or received,
which is obviously quite big.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M!hjñ  hžhubhÐ)”}”(hŒÂStarting with v2.40 ALPHA, the autoprobe routines have changed
significantly.  In particular, they won't tell you why the card was not
found unless you turn on the D_INIT_REASONS debugging flag.”h]”hŒÄStarting with v2.40 ALPHA, the autoprobe routines have changed
significantly.  In particular, they wonâ€™t tell you why the card was not
found unless you turn on the D_INIT_REASONS debugging flag.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M)hjñ  hžhubhÐ)”}”(hX‚  Once the driver is running, you can run the arcdump shell script (available
from me or in the full ARCnet package, if you have it) as root to list the
contents of the arcnet buffers at any time.  To make any sense at all out of
this, you should grab the pertinent RFCs. (some are listed near the top of
arcnet.c).  arcdump assumes your card is at 0xD0000.  If it isn't, edit the
script.”h]”hX„  Once the driver is running, you can run the arcdump shell script (available
from me or in the full ARCnet package, if you have it) as root to list the
contents of the arcnet buffers at any time.  To make any sense at all out of
this, you should grab the pertinent RFCs. (some are listed near the top of
arcnet.c).  arcdump assumes your card is at 0xD0000.  If it isnâ€™t, edit the
script.”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M-hjñ  hžhubhÐ)”}”(hŒyBuffers 0 and 1 are used for receiving, and Buffers 2 and 3 are for sending.
Ping-pong buffers are implemented both ways.”h]”hŒyBuffers 0 and 1 are used for receiving, and Buffers 2 and 3 are for sending.
Ping-pong buffers are implemented both ways.”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M4hjñ  hžhubhÐ)”}”(hX¦  If your debug level includes D_DURING and you did NOT define SLOW_XMIT_COPY,
the buffers are cleared to a constant value of 0x42 every time the card is
reset (which should only happen when you do an ifconfig up, or when Linux
decides that the driver is broken).  During a transmit, unused parts of the
buffer will be cleared to 0x42 as well.  This is to make it easier to figure
out which bytes are being used by a packet.”h]”hX¦  If your debug level includes D_DURING and you did NOT define SLOW_XMIT_COPY,
the buffers are cleared to a constant value of 0x42 every time the card is
reset (which should only happen when you do an ifconfig up, or when Linux
decides that the driver is broken).  During a transmit, unused parts of the
buffer will be cleared to 0x42 as well.  This is to make it easier to figure
out which bytes are being used by a packet.”…””}”(hjH  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M7hjñ  hžhubhÐ)”}”(hŒIYou can change the debug level without recompiling the kernel by typing::”h]”hŒHYou can change the debug level without recompiling the kernel by typing:”…””}”(hjV  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M>hjñ  hžhubhô)”}”(hŒ1ifconfig arc0 down metric 1xxx
/etc/rc.d/rc.inet1”h]”hŒ1ifconfig arc0 down metric 1xxx
/etc/rc.d/rc.inet1”…””}”hjd  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hóhŸh³h M@hjñ  hžhubhÐ)”}”(hŒŽwhere "xxx" is the debug level you want.  For example, "metric 1015" would put
you at debug level 15.  Debug level 7 is currently the default.”h]”hŒ–where â€œxxxâ€ is the debug level you want.  For example, â€œmetric 1015â€ would put
you at debug level 15.  Debug level 7 is currently the default.”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MChjñ  hžhubhÐ)”}”(hŒñNote that the debug level is (starting with v1.90 ALPHA) a binary
combination of different debug flags; so debug level 7 is really 1+2+4 or
D_NORMAL+D_EXTRA+D_INIT.  To include D_DURING, you would add 16 to this,
resulting in debug level 23.”h]”hŒñNote that the debug level is (starting with v1.90 ALPHA) a binary
combination of different debug flags; so debug level 7 is really 1+2+4 or
D_NORMAL+D_EXTRA+D_INIT.  To include D_DURING, you would add 16 to this,
resulting in debug level 23.”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MFhjñ  hžhubhÐ)”}”(hŒcIf you don't understand that, you probably don't want to know anyway.
E-mail me about your problem.”h]”hŒgIf you donâ€™t understand that, you probably donâ€™t want to know anyway.
E-mail me about your problem.”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MKhjñ  hžhubeh}”(h]”Œit-doesn-t-work-what-now”ah ]”h"]”Œit doesn't work: what now?”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒI want to send money: what now?”h]”hŒI want to send money: what now?”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¤  hžhhŸh³h MPubhÐ)”}”(hŒ?Go take a nap or something.  You'll feel better in the morning.”h]”hŒAGo take a nap or something.  Youâ€™ll feel better in the morning.”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MRhj¤  hžhubeh}”(h]”Œi-want-to-send-money-what-now”ah ]”h"]”Œi want to send money: what now?”ah$]”h&]”uh1h´hh¶hžhhŸh³h MPubeh}”(h]”Œarcnet”ah ]”h"]”Œarcnet”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”j¸  Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jõ  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jÐ  jÍ  jƒ  j€  jM  jJ  j”  j‘  jó  jð  j6  j3  j£  j   jh  je  j–  j“  jî  jë  j¡  jž  jÈ  jÅ  uŒ	nametypes”}”(jÐ  ‰jƒ  ‰jM  ‰j”  ‰jó  ‰j6  ‰j£  ‰jh  ‰j–  ‰jî  ‰j¡  ‰jÈ  ‰uh}”(jÍ  h¶j€  jÏ  jJ  j†  j‘  jP  jð  j—  j3  jö  j   j9  je  j¦  j“  jk  jë  j™  jž  jñ  jÅ  j¤  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hÐ)”}”(hŒ:Enumerated list start value not ordinal-1: "2" (ordinal 2)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ2â€ (ordinal 2)”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhjY  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h³Œline”Kuh1jW  hj!  ubjX  )”}”(hhh]”hÐ)”}”(hŒ:Enumerated list start value not ordinal-1: "3" (ordinal 3)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ3â€ (ordinal 3)”…””}”(hjx  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhju  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jr  Œsource”h³Œline”Kuh1jW  hj¡  ubjX  )”}”(hhh]”hÐ)”}”(hŒ:Enumerated list start value not ordinal-1: "4" (ordinal 4)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ4â€ (ordinal 4)”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhj  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jr  Œsource”h³Œline”Kuh1jW  hj  ubeŒtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.