01-14-2019
Quote:
Originally Posted by
homebeach
In this context bridging means connectivity to other networks. For example using talk to join IRC channel. This would be achieved by making a program that relays messages to IRC and back.
OK, understood. I actually use
talk - rarely, but with one working in the data center and the other colleague in the office it is often easy and convenient to use it for communication. Wouldn't your project be somewhat like the
Pidgin Chat Client just extended to support
talk? You might want to consider joining this project and writing exactly this extension.
bakunin
This User Gave Thanks to bakunin For This Post:
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Here is the scenario:
I use an OpenBSD 2.9 box as my firewall and gateway at the house. One of the boxes behind my OpenBSD box is my FreeBSDBox.
I would like to be able to use port forwarding with SSH to enable a secure connection from work to the OpenBSD box and to have the OpenBSD box... (6 Replies)
Discussion started by: auswipe
6 Replies
2. UNIX for Advanced & Expert Users
Does anyone know how to route apple talk through a bridged connection ? :eek: (1 Reply)
Discussion started by: maxamaynard
1 Replies
3. IP Networking
I have the manpage for this utility on my system, but the utility itself is not there.
My friend has the utility, but it does not work, not even on the same machine.
Does anyone remember it? What software package is it related to? Where is it configured? (1 Reply)
Discussion started by: Corona688
1 Replies
4. IP Networking
Hello,
I have an UTM that has 4 ports. I was bridged two ports of it. my pc wired to one port and other one to network. Now I can ping my default gateway but it doesn't work(I haven't access to internet) even http of gateway, what happened? what route I should added?
Thanks in advance.:confused: (0 Replies)
Discussion started by: Zaxon
0 Replies
5. Solaris
Hello all,
I was trying to hooking up several computers into my openindiana server box, the server box has few RJ45 gigabit ethernet. The desired hierarchy of the network will be shown as on the picture attached. I would like to connect each host into my gigabit ethernet because of me and my... (2 Replies)
Discussion started by: enno
2 Replies
6. IP Networking
Well I cannot be too certain of the setup, since it's a stock firmware, but I have a cheap Belkin wireless-n router and wanted to get some ideas of what may be going on while I've a few moments to ramble on about my problems... I requested the GPL source so I've just been pondering while waiting to... (0 Replies)
Discussion started by: neutronscott
0 Replies
7. What is on Your Mind?
At face value this looks bad for Android 6 and Linux.
Wi-fi security flaw 'puts devices at risk of hacks' - BBC News (1 Reply)
Discussion started by: hicksd8
1 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [ttyname]
DESCRIPTION
The talk utility is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host' or 'host!user' or 'host:user'.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX'.
When first called, talk sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to the user you wish to talk to. At this point, the recipient of the message should reply by typing
talk your_name@your_machine
It does not matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the
two parties may type simultaneously, with their output appearing in separate windows. Typing control-L '^L' will cause the screen to be
reprinted. Typing control-D '^D' will clear both parts of your screen to be cleared, while the control-D character will be sent to the
remote side (and just displayed by this talk client). Your erase, kill, and word kill characters will behave normally. To exit, just type
your interrupt character; talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state.
Permission to talk may be denied or granted by use of the mesg(1) command. At the outset talking is allowed.
FILES
/etc/hosts to find the recipient's machine
/var/run/utx.active to find the recipient's tty
SEE ALSO
mail(1), mesg(1), wall(1), who(1), write(1), talkd(8)
HISTORY
The talk command appeared in 4.2BSD.
In FreeBSD 5.3, the default behaviour of talk was changed to treat local-to-local talk requests as originating and terminating at localhost.
Before this change, it was required that the hostname (as per gethostname(3)) resolved to a valid IPv4 address (via gethostbyname(3)), making
talk unsuitable for use in configurations where talkd(8) was bound to the loopback interface (normally for security reasons).
BUGS
The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD.
Multibyte characters are not recognized.
BSD
January 21, 2010 BSD