Loopback


 
Thread Tools Search this Thread
Special Forums UNIX Desktop Questions & Answers Loopback
Prev   Next
# 7  
Old 02-27-2013
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

NAT Loopback and iptables

Hello, please can you help and explain me. I have two servers. Both are RHEL6. I use the first one like router and the second one for apache. Router forwards 80 port on the second server and I can open that from the internet (mysite.com, for example). But I can not open mysite.com if i try to... (0 Replies)
Discussion started by: 6765656755
0 Replies

2. UNIX for Dummies Questions & Answers

How to Loopback?

This is in the beginning of the program: clear tput cup 1 20 echo "Welcome to UNIX I Final Assignment" tput cup 4 3 echo -e "Who would you like to look up? \c" tput cup 6 5 echo "vans, Rolland" tput cup 8 5 echo "ones, Mildred" tput cup 10 5 echo "mith, Julie" tput cup 12 5 echo... (0 Replies)
Discussion started by: thriveforana
0 Replies

3. Linux

Loopback interface doen't appear

Hi all, i have a problem with (Network in Linux) .. my issue with a HW appliance has openfiler 2.3 and is used for File Sharing using samba .. the problem is when i try to list all configured network interfaces using ifconfig -a .. i can't see the loopback interface, Although the file... (3 Replies)
Discussion started by: mabdelmageid
3 Replies

4. Red Hat

Configure floating IP on loopback interface

Hi All, I need to configure a floating IP on loopback interface of two servers (RHEL 5.4). After configuring, I'm not able to ping to that IP from a different server. I fail to understand what is missing here. I have done similar configuration in another environment & it works fine. Plz help.... (0 Replies)
Discussion started by: max_min
0 Replies

5. Solaris

Adding Loopback Interface

Hello, I have a SunOS (5.5.1) system that I need to migrate to a new IP address. I would like to have any requests destined for the old IP to be forwarded to this server. One suggestion I had was to add a route on my router that would point the old IP to the new IP. How do I add another... (2 Replies)
Discussion started by: reiklen
2 Replies

6. Filesystems, Disks and Memory

Can a Loopback Filesystem be Partitioned?

I have a disk image file created for use with the Linux version of the QEMU emulator. It's partitioned. I opened it with fdisk and the partitions show up with some extra messages about physical/logical endings: Disk knoppix.img: 0 MB, 0 bytes 16 heads, 63 sectors/track, 0 cylinders Units =... (3 Replies)
Discussion started by: deckard
3 Replies

7. AIX

loopback in 4.1.4.0 AIX server

Hi: I´ve a problem in a 4.1.4.0 AIX server because is generating a loopback in its own ip address and this are consuming all the bandwidth. I did many things trying to solve the problem but it doesn´t help. 1. Flush Routing tables 2. Get Up/Down Network interface 3. Add/remove Network... (0 Replies)
Discussion started by: terron79
0 Replies

8. Filesystems, Disks and Memory

Can I Use Loopback Devices with LVM?

I've got a RedHat 9 box with LVM support in a 2.4.22 kernel. What I would like to do is take a set of empty files created with 'dd' and concatenate them into a volume group. I've done a good deal of googling, and it seems that this is something that can be done. But when I try to use 'pvcreate'... (3 Replies)
Discussion started by: deckard
3 Replies

9. Filesystems, Disks and Memory

Using loopback devices in RAID?

Hopefully I am posting this silly question in the right place... I was wondering about the possibility of using loopback files on a physical disk to create virtual disks that could shrink or grow as needed. Something like RAID 0, but instead of using block devices, just using files. If I need... (0 Replies)
Discussion started by: deckard
0 Replies

10. UNIX for Advanced & Expert Users

Loopback Interface...Vanished???

Recently I noticed that my internet connection would not work correctly-although connected domain names could not be resolved. My resolv.conf file was fine since it is configured every time I dial up. a closer inspection showed that my loopback interface had disappearerd! Any ideas why would this... (1 Reply)
Discussion started by: silvaman
1 Replies
Login or Register to Ask a Question
syncinit(1M)						  System Administration Commands					      syncinit(1M)

NAME
syncinit - set serial line interface operating parameters SYNOPSIS
/usr/sbin/syncinit device [ [baud_rate] | [keyword=value,]... | [single-word option]] DESCRIPTION
The syncinit utility allows the user to modify some of the hardware operating modes common to synchronous serial lines. This can be useful in troubleshooting a link, or necessary to the operation of a communications package. If run without options, syncinit reports the options as presently set on the port. If options are specified, the new settings are reported after they have been made. OPTIONS
Options to syncinit normally take the form of a keyword, followed by an equal sign and a value. The exception is that a baud rate may be specified as a decimal integer by itself. Keywords must begin with the value shown in the options table, but may contain additional letters up to the equal sign. For example, loop= and loopback= are equivalent. The following options are supported: Keyword Value Effect loop yes Set the port to operate in internal loopback mode. The receiver is elec- trically disconnected from the DCE receive data input and tied to the outgoing transmit data line. Transmit data is available to the DCE. The Dig- ital Phase-Locked Loop (DPLL) may not be used as a clock source in this mode. If no other clocking options have been specified, perform the equivalent of txc=baud and rxc=baud. no Disable internal loopback mode. If no other clocking options have been spec- ified, perform the equivalent of txc=txc and rxc=rxc. echo yes Set the port to operate in auto-echo mode. The transmit data output is electrically disconnected from the transmitter and tied to the receive data input. Incoming receive data is still visible. Use of this mode in combination with local loopback mode has no value, and should be rejected by the device driver. The auto-echo mode is useful to make a system become the endpoint of a remote loopback test. no Disable auto-echo mode. nrzi yes Set the port to operate with NRZI data encoding. no Set the port to operate with NRZ data encoding. txc txc Transmit clock source will be the TxC signal (pin 15). rxc Transmit clock source will be the RxC signal (pin 17). baud Transmit clock source will be the internal baud rate generator. pll Transmit clock source will be the out- put of the DPLL circuit. rxc rxc Receive clock source will be the RxC signal (pin 17). txc Receive clock source will be the TxC signal (pin 15). baud Receive clock source will be the internal baud rate generator. pll Receive clock source will be the out- put of the DPLL circuit. speed integer Set the baud rate to integer bits per second. There are also several single-word options that set one or more paramaters at a time: Keyword Equivalent to Options: external txc=txc rxc=rxc loop=no sender txc=baud rxc=rxc loop=no internal txc=pll rxc=pll loop=no stop speed=0 EXAMPLES
Example 1 Using syncinit The following command sets the first CPU port to loop internally, using internal clocking and operating at 38400 baud: example# syncinit zsh0 38400 loop=yes device: /dev/zsh ppa: 0 speed=38400, loopback=yes, echo=no, nrzi=no, txc=baud, rxc=baud The following command sets the same port's clocking, local loopback and baud rate settings to their default values: example# syncinit zsh0 stop loop=no device: /dev/zsh ppa: 0 speed=0, loopback=no, echo=no, nrzi=no, txc=txc, rxc=rxc ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
syncloop(1M), syncstat(1M), intro(2), ioctl(2), attributes(5), zsh(7D) DIAGNOSTICS
device missing minor device number The name device does not end in a decimal number that can be used as a minor device number. bad speed: arg The string arg that accompanied the speed= option could not be interpreted as a decimal integer. Bad arg: arg The string arg did not make sense as an option. ioctl failure code = errno An ioctl(2) system called failed. The meaning of the value of errno may be found in intro(2). WARNINGS
Do not use syncinit on an active serial link, unless needed to resolve an error condition. Do not use this command casually or without being aware of the consequences. SunOS 5.11 9 Mar 1993 syncinit(1M)