01-19-2004
TCP over serial
Here's my config: One quadra 840av working under netBSD and successfully connected to my network. One PM 6100 connected but not booting fully into netBSD (i realize this is faulty but I figured it was worth a shot to try and install netBSD/mac68k on it due to the fact it is unsupported under the netBSD/macppc model.)
Anyways, I have a few other non-ethernet-ready machines sitting around, and i was wondering if it was at all possible to tunnel a tcp connection over the serial bus... what I want to do is to basically route the connection from the Quadra to the other machines via serial to the Quadra then to the enet network via ethernet.
Question number two... where can I find a copy of mklinux? it would seem that they're all but deceased from the world; I realize this is totally off topic, but I figured if anyone would know, it would be you. What other *NIX OSes do you think the 6100 would run (besides the wreck of a netBSD/mac68k I already have.)
Thanks everyone!
DAZ
10 More Discussions You Might Find Interesting
1. Cybersecurity
!HELLO ,
What is the maximum number of hosts on a TCP/IP internet?
plz can u help me.
:rolleyes: (2 Replies)
Discussion started by: smdakram
2 Replies
2. Cybersecurity
I have installed TCP wrappers , Good package ...
I have a problem with the hosts_options part ...
I am not able to use the twist command .. It just dosent respond
I have compiled wrappers 7.6 for Solaris 8 with ipv6 support ...
Everything works fine except the twist doesnt work
I have... (1 Reply)
Discussion started by: DPAI
1 Replies
3. IP Networking
I have written a TCP/IP client and server program. The client sends a message to the server and then the server sends a file back to the client. The client reads the buffer and stores it another file in the client side.
I need to know what are the various exceptions that I need to handle in... (0 Replies)
Discussion started by: Rajeshsu
0 Replies
4. Shell Programming and Scripting
can u tell me from where do i get
TCP/IP Source code plz. (2 Replies)
Discussion started by: pradeep83rawat
2 Replies
5. Solaris
has anyone ever tried using a client list in thier hosts.allow file
Example of hosts.allow) in.ftpd: /etc/ftp.hosts
"ftp.hosts" has my list of IP address that are allow access....
However I cant get this work...Any Comments or Help? (0 Replies)
Discussion started by: dodge_man
0 Replies
6. AIX
Hi,
Is there anyway to bring down ethernet interface using non-root ID?
Appreciate if you could advice how to do that using non-root ID and what are previleges required in order to perform the tasks.
Thanks (1 Reply)
Discussion started by: srllee
1 Replies
7. AIX
With things installed and wrapping ftpd on AIX 5.1 in hosts.deny I have;
ALL: ALL
in hosts.allow;
ftpd: x.x.x.x
ALL: x.x.x.x
I get this on connect via ftp;
421 Service not available, remote server has closed connection
So its working as far as blocking but the hosts.allow seems to be... (1 Reply)
Discussion started by: traken
1 Replies
8. Ubuntu
Hello!
I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Discussion started by: mvona
5 Replies
9. Programming
Hi guys.
I'm going to buy TCP/IP Illustrated series(3 Volumes). But I saw that these books are very outdated. But reviews at amazon says that these books are awesome.
What is your idea? Is it worth? What else do you suggest?
I'm interested in practical books from protocol design to... (1 Reply)
Discussion started by: majid.merkava
1 Replies
10. Solaris
I have problem with oracle solaris 10 running on oracle sparc T4-2 server.
Os information: 5.10 Generic_150400-03 sun4v sparc sun4v
Output from tcpstat.d script
TCP bytes: out outRetrans in inDup inUnorder
6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
LEARN ABOUT OSF1
port_names
ports(7) Miscellaneous Information Manual ports(7)
NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports
SYNOPSIS
Default Serial Ports:
/dev/tty00
/dev/tty01 (not present on a single-port system)
Parallel Port:
/dev/lp0
DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2
(COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial
printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel
port, for use with a parallel printer.
When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These
devices are located in the /dev directory.
For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a
terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if
one serial port is labeled with an icon for a terminal console) the remaining serial port.
If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also
be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports.
The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral-
lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel
printers, so fewer devices are connected to this port as compared to serial ports.
If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial
devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that
has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and
also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the
device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01).
If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you
use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2
(with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE
Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port
2.
See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the
modem(7) reference page for more information on setting up modems.
SEE ALSO
Commands: lprsetup(8)
Devices: ace(7), modem(7)
System Administration delim off
ports(7)