12-07-2010
Quote:
Originally Posted by
DGPickett
It does have the lowest Rx, it just likes to talk? Maybe the talk suppresses others on the collision domain, so it appears to be the fastest way out, which makes more talk, suppression. Some systems are naturally unstable in subtle ways.
That doesn't really help.
10 More Discussions You Might Find Interesting
1. Solaris
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
2. UNIX for Advanced & Expert Users
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
3. IP Networking
Hello, I am trying to get clarity on a few things and am looking for some info.
In every article I have read about link aggregation and lacp, it can be used combine physical links to create 1 logical link for increased bandwidth.
But what it doesn't say is if this is limited by source/dst. ... (1 Reply)
Discussion started by: jaredo
1 Replies
4. IP Networking
I have some linux machines that I am trying to increase the throughput to on a single connection. They connect to a switch with two 1GbE lines and the switch does not have Link Aggregation support for these machines. I have tried bonding with balance-rr, balance-alb, but the machines can only... (4 Replies)
Discussion started by: Eruditass
4 Replies
5. Solaris
Me again :)
I'm trying to find a page describing the L2, L3 und L4 modes of dladm.
It's nice to read "hashed by ip header", but how should I use that?
On the file-server it's ok to have the six interfaces serving six clients each on it's own. But an rsync connection via switch between two... (8 Replies)
Discussion started by: PatrickBaer
8 Replies
6. HP-UX
Hi,
I want to Break the Link Aggregation. My aggregation are lan0+lan1 = lan900.
Now I want to break this and put the IP in lan0. But i have cluster environment and this is the main database server.
So It need to change in cluster script.
But I dont know where I have to change it.
Please... (1 Reply)
Discussion started by: mkiron
1 Replies
7. IP Networking
HI all,
First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place.
I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
Discussion started by: elliottlc
0 Replies
8. AIX
Hi Everyone,
Is it possible to configure bonding over bonded interface in AIX?
For example:
server has for NIC port:
ent0
ent1
ent2
ent3
First I create a EtherChannel ent4 from ent0 and ent1.
and then I create a EtherChannel ent5 from ent2 and ent3.
Can I create a EtherChannel... (1 Reply)
Discussion started by: nnnnnnine
1 Replies
9. IP Networking
Hi
ihave three link of internet and iwant to put one linux front of a firewall that this three linux speard firewall such az load balance and fialover but dont close any port and protocol and only firewall have been internet what way can i use for it ?
are there any script and services do that... (0 Replies)
Discussion started by: mnnn
0 Replies
10. UNIX for Advanced & Expert Users
Hi All,
I have done IEEE 802.3ad Dynamic link aggregation bond configuration with name bond0 which has 4 slaves (each 25GB/s) in it on cent os 6.8. Issue i am facing is bonding throughput is only 50GB/s not 100GB/s. below are the configuration files :
DEVICE=bond0
IPADDR=xx.xx.xx.xx... (1 Reply)
Discussion started by: omkar.jadhav
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.
CONFIGURATION
The talk utility relies on the talkd system daemon. See talkd(8) for information about enabling talkd.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmpx 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
August 21, 2008 BSD