Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.apple2 > #26668
| From | D Finnigan <dog_cow@macgui.com> |
|---|---|
| Newsgroups | comp.sys.apple2 |
| Subject | Re: Suggestion for UII Server Program Documentation |
| Date | 2016-01-09 21:52 +0000 |
| Organization | Mac GUI |
| Message-ID | <dog_cow-1452376498@macgui.com> (permalink) |
| References | <n6ri06$ohe$1@dont-email.me> |
ultramagnus_tcv wrote: > Hello, > > I was able to get the server program to work properly after discovering > that my slots configuration had reverted back to Printer (Slot 1). > Thanks for including the program. > > I did have a couple of suggestions for the documentation since no one > person is an expert at everything. Networking is more my bailiwick than > programming. > > I think it's probably a good idea to state at the outset that one > should probably investigate their true network settings if they > sincerely want to try the program. Setting a source IP of 169.254.2.4 > and expecting to be able to communicate at 192.168.2.1 is not going to > work since there's no route between the two networks. Agreed, because 169.254.x.x isn't routable outside of the local link. But if a machine has a routable address, it can communicate with a machine that doesn't have a routable address, as long as the two are on a local link. (From what you said above, you may already know all this.) And that's my network configuration. I didn't notice that address mismatch in the source code until a few days ago, and I probably hadn't noticed it *because* it works in my configuration. Mac OS X is multi-homed and retains its link-local address even after it has obtained an address through DHCP or other means. Its behavior follows the RFC which is when communicating with a host using a link-local destination address, it will also use a link-local source address. There must be more to it in this particular case, and I should check again to see exactly what's happening with Wireshark. The challenge here is to have default addresses that will work in as many network configurations as possible, but also keep the sample programs simple too. But what assumption is correct: are more people testing with the Apple II on the local link, or are more people testing with a network where the Apple II is on a different local link? > > Also: Am I correct in saying that this program shows only one-way > communication? I could see data transmitted from 201 to 202 but not > vice-versa. Yes. I'm going to write a 2-way chat program next. Also on the to do list is a DHCP client, and a wget program that will use ProDOS to save a file downloaded via HTTP to disk. No matter what, the TCP sample program currently in the manual is going to change, because I have discovered some new techniques for transferring data to/from the W5100. Also because of the IP address problem that you mention. -- ]DF$ The Marina IP stack for Apple II-- http://marina.a2hq.com/
Back to comp.sys.apple2 | Previous | Next — Previous in thread | Next in thread | Find similar
Suggestion for UII Server Program Documentation ultramagnus_tcv <mikew@thecomputervalet.com> - 2016-01-09 12:05 -0600
Re: Suggestion for UII Server Program Documentation D Finnigan <dog_cow@macgui.com> - 2016-01-09 21:52 +0000
Re: Suggestion for UII Server Program Documentation ultramagnus_tcv <mikew@thecomputervalet.com> - 2016-01-09 17:11 -0600
Re: Suggestion for UII Server Program Documentation D Finnigan <dog_cow@macgui.com> - 2016-01-11 19:26 +0000
Re: Suggestion for UII Server Program Documentation ultramagnus_tcv <mikew@thecomputervalet.com> - 2016-01-11 17:32 -0600
Re: Suggestion for UII Server Program Documentation D Finnigan <dog_cow@macgui.com> - 2016-01-12 19:00 +0000
csiph-web