10 More Discussions You Might Find Interesting
1. Red Hat
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
2. UNIX Desktop Questions & Answers
echo "vans, Rolland"
echo "Press in Your Keyboard to Quit"
echo -e "Please Enter Your Choice : \c"
case $option in
I have created the corresponding information for each input on the display so...
My question is...
How do I display the corresponding information... (6 Replies)
Discussion started by: thriveforana
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
4. Red Hat
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
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
6. Filesystems, Disks and Memory
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
I´ve a problem in a 22.214.171.124 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
8. Filesystems, Disks and Memory
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
9. Filesystems, Disks and Memory
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
10. UNIX for Advanced & Expert Users
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
ticlts(7D) Devices ticlts(7D)
ticlts, ticots, ticotsord - loopback transport providers
The devices known as ticlts, ticots, and ticotsord are ``loopback transport providers,'' that is, stand-alone networks at the transport
level. Loopback transport providers are transport providers in every sense except one: only one host (the local machine) is ``connected
to'' a loopback network. Loopback transports present a TPI (STREAMS-level) interface to application processes and are intended to be
accessed via the TLI (application-level) interface. They are implemented as clone devices and support address spaces consisting of ``flex-
addresses,'' that is, arbitrary sequences of octets of length > 0, represented by a netbuf structure.
ticlts is a datagram-mode transport provider. It offers (connectionless) service of type T_CLTS. Its default address size is TCL_DEFAULTAD-
DRSZ. ticlts prints the following error messages (see t_rcvuderr(3NSL)):
TCL_BADADDR bad address specification
TCL_BADOPT bad option specification
TCL_PEERBADSTATE peer in wrong state
ticots is a virtual circuit-mode transport provider. It offers (connection-oriented) service of type T_COTS. Its default address size is
TCO_DEFAULTADDRSZ. ticots prints the following disconnect messages (see t_rcvdis(3NSL)):
TCO_NOPEER no listener on destination address
TCO_PEERNOROOMONQ peer has no room on connect queue
TCO_PEERBADSTATE peer in wrong state
TCO_PEERINITIATED peer-initiated disconnect
TCO_PROVIDERINITIATED provider-initiated disconnect
ticotsord is a virtual circuit-mode transport provider, offering service of type T_COTS_ORD (connection-oriented service with orderly
release). Its default address size is TCOO_DEFAULTADDRSZ. ticotsord prints the following disconnect messages (see t_rcvdis(3NSL)):
TCOO_NOPEER no listener on destination address
TCOO_PEERNOROOMONQ peer has no room on connect queue
TCOO_PEERBADSTATE peer in wrong state
TCOO_PEERINITIATED provider-initiated disconnect
TCOO_PROVIDERINITIATED peer-initiated disconnect
Loopback transports support a local IPC mechanism through the TLI interface. Applications implemented in a transport provider-independent
manner on a client-server model using this IPC are transparently transportable to networked environments.
Transport provider-independent applications must not include the headers listed in the synopsis section above. In particular, the options
are (like all transport provider options) provider dependent.
ticlts and ticots support the same service types (T_CLTS and T_COTS) supported by the OSI transport-level model.
ticotsord supports the same service type (T_COTSORD) supported by the TCP/IP model.
SunOS 5.11 3 Jul 1990 ticlts(7D)