similar to: How to cascade dial status back through IAX

Dear list, I'm relatively new to using ssh. I'm trying to use the -R option to set up a forwarded port between two machines. Specifically I'd like to be able to ssh to machineB from machineA and then have a port on machineB that I can connect to machineA with. If my understanding is correct I'd need a command like: machineA> ssh -R 10000:machineA:23 machineB This should

I had a quick look for an answer to what I'd presume is a common Q but failed so wondering if somebody here would point me in the right direction, please & thanks?! I wish to use rsync to backup users' home dirs from machineA (Debian) to machineB (Fedora). I have a script, say backup.sh, in my own home dir and linked to from /etc/cron.daily and have set up the ssh keys so

I'm probably doing something I'm not supposed to even try, but I'm trying for "proof of concept" before physically setting up a distant network because of logistical issues. Anyway, I have tincd running as a service on two windows machines on the same lan. I'm trying to establish a connection between those two computers on the vpn ip's (10.20.30.1 and 10.20.40.1).

Hi, This might be a very basic question, but since i''m new to rails, can you please let me kow how to do this. My app is like this i have a menu in the left side which says "Status" and if i click this link i have a static menu displayed like this "MachineA" MachineB" and "MachineC" Upon clicking any of those machines i need to display a bunch of

I am not sure where to begin so I will be as verbose as I can to explain the problem. I have 3 servers. Their specs are: Machine A: Redhat 7.1 kernel 2.4.9-34 openssh 3.1p1-5 Machine B: Redhat 7.3 kernel 2.4.9-31 openssh 3.1p1-5 Machine C: Debian Woody kernel 2.4.18-bf2.4 openssh 3.4p1 rsync 2.5.6 I am running an rsync over ssh from Machine C to Machine B with the following: rsync --verbose

I'm using the very latest 'version 3.0.1pre3 protocol version 30', on both ends, and have seen a date/time discrepancy in the log on the receiver. The sending machine (machineA) is in US CDT while the receiver is in US PDT. Both sender and receiver have their time set correctly. a contiguous snippet from the log on the receiver : (note the first three timestamps are correct:)

Hi, I have a smb pdc running which works quite well so far, and would like to know if this feature is possible. I have two locations, and I want all users to authenticate on Machine A. Howver there are some users that are closer to machine B, and I would like to be able to have the homes of those users on machine B rather than machine A (they should authenticate on machine A anyway). Is this

Presently, the Samba documentation says that the default NetBIOS username used by client-type applications is determined by the following (from smbclient(1)), If no username is supplied, it will default to an uppercase version of the environment variable USER or LOGNAME in that order. If no username is sup- plied and neither

I have searched for this and the solutions I found were for instances where the workgroup name *was* too long. However, my workgroup name is *not* too long. The spaces between PEGASUS and ^[ are part of the message, I did not add them. If you count them there are 16 total including ending ^[. I can't figure out where the spaces are coming from. This is the same for every Samba

Perhaps a stupid question, but i will give it a try: I have two machines on libvirtd session and network on usermod. Can i (somehow) cross these two machines ? machineA: ip addr add 10.10.10.101/24 dev eth0 ip route add default via 10.10.10.102 dev eth0 machineB: ip addr add 10.10.10.102/24 dev eth0 ip route add default via 10.10.10.101 dev eth0 -- Evaggelos Balaskas - Unix System Engineer

Am 25.02.2015 um 22:48 schrieb Miguel Medalha: >> I have searched for this and the solutions I found were for instances >> where the workgroup name *was* too long. However, my workgroup name is >> *not* too long. The spaces between PEGASUS and ^[ are part of the >> message, I did not add them. If you count them there are 16 total >> including ending ^[. I

samba-bounces at lists.samba.org wrote on 02/25/2015 02:51:28 PM: > From: Reindl Harald <h.reindl at thelounge.net> > To: samba at lists.samba.org > Date: 02/25/2015 02:52 PM > Subject: Re: [Samba] Workgroup name too long > Sent by: samba-bounces at lists.samba.org > > > > Am 25.02.2015 um 22:48 schrieb Miguel Medalha: > >> I have searched for this and

>> From: Reindl Harald <h.reindl at thelounge.net> >> To: samba at lists.samba.org >> Date: 02/25/2015 02:52 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >> >> >> Am 25.02.2015 um 22:48 schrieb Miguel Medalha: >>>> I have searched for this and the solutions I found were

>> From: schulz at adi.com (Thomas Schulz) >> To: durwin at mgtsciences.com, h.reindl at thelounge.net, > samba at lists.samba.org >> Date: 02/25/2015 06:39 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >>>> From: Reindl Harald <h.reindl at thelounge.net> >>>> To: samba at

Currently we have problems with our asterisk server connect with an Eicon Diva 4BRI Card to a PBX. Asterisk is running in version 1.0.0 on RedHat Enterprise Linux 3AS with kernel 2.4.21-4.EL. The Diva server is running in version 7.5 Can someone help us in reolving the errors with incoming calls? When we try to call to an extension we get these messages in the CLI: -- creating pipe for

https://bugzilla.mindrot.org/show_bug.cgi?id=1463 Summary: Running nohup sleep 70 & and then exiting shell, hangs ssh Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:

Asterisk 1.2.16 I have an extension "102" with a Polycom 430 I am trying to protect against forwarding loops If I set the phone to forward the line to itself, extension 102 I get the following -- Got SIP response 302 "Moved Temporarily" back from 206.83.240.18 -- Now forwarding Local/102@mycontext-b2ee,2 to 'Local/102@mycontext' (thanks to

I am seeing some curious behaviour with a 1.2.32 system, which I do not understand and so can't work out how to fix it. I have a PRI routed to context default. Here is the complete default context: [default] exten => _9X.,1,Dial(IAX2/m1peer/${EXTEN:1}) exten => _20XX,1,Dial(IAX2/sipeer/${EXTEN}) exten => _X.,1,Dial(IAX2/m1peer/${EXTEN}) exten =>

I understand how to control the first local channel, but an having trouble getting the second local channel to enter stasis. I setup have the following extensions.conf to handle 1000 (basically had it setup so if first stasis not there try second, but believe second channel never processes the dial plan so even if second line was hello-world2 it would not matter. [mycontext] exten =>

Well, I thought I had my problem solved, but it is acting up again. Hopefully this time I can provide enough information. What I have is an * box setup with one X100P and TDM400 with one FXO and one FXS. For my regular setup with interfacing with my PSTN and my entire house with analog phones, the box is working great. I am trying to interface a Mediatrix 1202 device to my * box via the