08-04-2010
Can you ping unix.com ? If so DNS trouble seems unlikely...
10 More Discussions You Might Find Interesting
1. IP Networking
If the cable modem that the cable company is using doesn't support unix is there a way around that . Are there drivers I can get online or is there a way to configure redhat lenix (that's what I will be using) to work with the cable modem. Or is there a way to buy a third party cable modem that... (3 Replies)
Discussion started by: gparsons70
3 Replies
2. UNIX for Dummies Questions & Answers
I recently installed Caldera 2.4 (successfully:p ), but I cannot seem to get my cable modem up and running! My ISP is AT&T and I'm using @home. I've tried using DHCP and that didn't work either. I briefly read the cable modem HOWTO, but the lsmod didn't list my network card (3COM). What do I do now? (4 Replies)
Discussion started by: zorro
4 Replies
3. UNIX for Dummies Questions & Answers
Caldera eDesktop 2.4 - Cable Modem
my NIC card has been detected, but funny scenario:
#dmesg
eth0: RealTek rtl8139 Fast Ethernet at 0x2400, IRQ 0, 00:50:ba:43:a0:ef
/*I noticed that it detected the correct module (rtl8139) but I'm using D-Link and not RealTek, which uses the same module.... (1 Reply)
Discussion started by: zorro
1 Replies
4. UNIX for Dummies Questions & Answers
Is anyone using a cable modem with unix and if so does your cable co. support unix or did you get that going on your own and how.
Thank you for all your help. (5 Replies)
Discussion started by: gparsons70
5 Replies
5. IP Networking
I can do all this in windows, but Im trying to run the SuSe 8.0 professional as a gateway. I have the local (private) LAN setup with no problems, but Im having troubles getting it to use DHCP to go out on the external card to the service provider, which only uses Dynamic IP's. WHere, what and how... (3 Replies)
Discussion started by: ftn96
3 Replies
6. UNIX for Dummies Questions & Answers
hi , i have sparc machine , i want to connect my le0 (ethernet interface) directly to cable modem ,
i have created a file resolv.conf,hosts, dhcp.le0,defaultrouter,nisswitch,hostname.le0. i dont know my cable companies <domain name> and <name server assigned to me> , also they even dont know how... (5 Replies)
Discussion started by: raju
5 Replies
7. UNIX for Dummies Questions & Answers
I have a XP computer which is my primary. I recently, well just today installed a old version of Mandrake Linux 6.5 I had laying on a self collecting dust on a old PII 233mhz that had to be vacummed out before I could use it.
I have my XP computer connected by 10/100 NIC to a cable modem. My... (1 Reply)
Discussion started by: garfunkle
1 Replies
8. BSD
hi
I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system.
When I type, I get
# ifconfig -a
lo0 : ....
...
...
rl0 : ....
...
...
vr0 : ...
...
...
I have two network cards (the machine will be a router).
I created... (1 Reply)
Discussion started by: fnoyan
1 Replies
9. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
10. Cybersecurity
hi
im running a web server running, connected to my cable modem, which, as usual, has 2 different network address. one from "outside"(ie from isp), and the
other for the internal network.
im giving a static ip to the server.how do i access this server from outside the network across "the... (2 Replies)
Discussion started by: R00tSc0rpi0n
2 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)