Sponsored Content
Full Discussion: Bridging Talk
Top Forums Programming Bridging Talk Post 303028804 by homebeach on Tuesday 15th of January 2019 10:59:29 AM
Old 01-15-2019
Rather than being client my program would work as a relay bridge.



--- Post updated at 03:59 PM ---

Here seems to be some source codes for GNU Talk: GNU Talk Homepage. I was planning to use those as the basis of my program. I need to see how it is possible to redirect messages from talk.
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Bridging with SSH Tunnels

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

apple talk

Does anyone know how to route apple talk through a bridged connection ? :eek: (1 Reply)
Discussion started by: maxamaynard
1 Replies

3. IP Networking

UNIX talk

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

problem with bridging!!! :(

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

openindiana bridging problem (brctl)

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

Linux Bridging, Wireless AP, IPv6 multicast and autoconfiguration.

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?

Anybody want to talk about Krack?

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
Talk 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'. 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' or 'pts/X'. When first called, talk contacts the talk daemon on the other user's machine, which 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 that user. At this point, he then replies by typing talk your_name@your_machine It doesn't 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; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state. As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win- dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less often. If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output. FILES
/etc/hosts to find the recipient's machine /var/run/utmp to find the recipient's tty SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8) BUGS
The protocol used to communicate with the talk daemon is braindead. Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some vendor Unixes (particularly those from Sun) have been found to use this old protocol. There's a patch from Juan-Mariano de Goyeneche (jmseyas@dit.upm.es) which makes talk/talkd, if compiled with -DSUN_HACK, compatible with SunOS/Solaris' ones. It converts messages from one protocol to the other. Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec- tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with. HISTORY
The talk command appeared in 4.2BSD. Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)
All times are GMT -4. The time now is 01:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy