Sponsored Content
Operating Systems Solaris Can't setup gateway other than 127.0.0.1? Post 302315263 by Sun Fire on Tuesday 12th of May 2009 02:30:49 AM
Old 05-12-2009
I think If installation didn't ask about "networked" and "non-networked", this means you need to search for the driver for that network interface.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

rc=127 can't fork

I have a script to download a file using wget. It works if I execute it from the command line. But, if I run it in cron, it doesnt work and I am getting the following in the cron log: > CMD: /export/home/username/test > username 23159 c Tue Aug 1 14:40:00 2006 < username 23159 c Tue Aug ... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

2. AIX

NIM server setup on etherchannel setup environment

I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it? I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame. Any help is appreciated. (1 Reply)
Discussion started by: pdtak
1 Replies

3. Linux

GNUGK-How to setup static gateway to gateway routing

Dear Sir I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper. I am having a problem, configuring static call routing on GNUGK in the section ... (0 Replies)
Discussion started by: mfondoum
0 Replies

4. Solaris

multitude of packets from 127.0.0.1

I was checking routing table, and noticed that our server has a lot packets from localhost: Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- .. 127.0.0.1 127.0.0.1 ... (1 Reply)
Discussion started by: orange47
1 Replies

5. UNIX for Advanced & Expert Users

wait - return code 127

Hi All, I am trying to create background processes and then check their status later. But I am getting return codes as 0,127 randomly On checking the return codes for wait, I found the below. Do I need to treat return code of 127 as successful as well?? as we know the process id passed is... (7 Replies)
Discussion started by: tostay2003
7 Replies

6. IP Networking

127.0.0.1 vs 0.0.0.0

Which one should I use in '/etc/hosts'? Please explain in details. Random quotes on the topic: (2 Replies)
Discussion started by: useretail
2 Replies

7. UNIX for Advanced & Expert Users

Issue setup Transparent proxy and Gateway using Squid on CentOS 7

Hello, We are migrating our gateways from CentOS 6 to CentOS 7 and for setting up a transparent proxy using squid and Firewalld i am using below configuration. #Firewalld configurations firewall-cmd --permanent --zone=public --add-forward-port=port=80:proto=tcp:toport=3128:toaddr=LAN_IP... (4 Replies)
Discussion started by: sunnysthakur
4 Replies

8. Linux

Not able to setup CentOS 7 as gateway [Using squid proxy]

Hello, Did anyone setup a CentOS7 as a gateway (with squid transparent proxy). I am trying to do so but not able to setup. I setup squid , iptables (using it instead of firewalld) and all the necessary IPtables rules but nothing work. It work previously but access.log of squid not getting... (4 Replies)
Discussion started by: sunnysthakur
4 Replies

9. UNIX for Beginners Questions & Answers

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

Dear friends I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
pcelx(7D)																 pcelx(7D)

NAME
pcelx - 3COM EtherLink III PCMCIA Ethernet Adapter SYNOPSIS
network@<socket>:pcelx<socket> The pcelx driver supports the 3COM EtherLink III PCMCIA PC Card as a standard Ethernet type of device conforming to the DLPI interface specification. The driver supports the hot-plugging of the PC Card. The PPA (Physical Point of Attachment) is defined by the socket number the PC Card is inserted in. This means that for IP use, the PC Card should always be plugged into the same socket that the network interface was initially brought up on or else a network reconfiguration should be done to take down the old interface and bring up the new one. The 3C589, 3C589B, and 3C589C versions of the PC Card are supported on the platform. The 3C589B and 3C589C are supported on the SPARC platform. PRECONFIGURE
o For IBM ThinkPad 760E series systems and systems using the TI PCI1130 PCI-to-CardBus chip (such as the Dell Latitude XPi CD) only: Before bringing the system onto the network, put the PC Card into 8-bit mode by creating a file called /kernel/drv/pcelx.conf contain- ing force-8bit=1;. o It is not possible to boot or install the Solaris software using a 3Com EtherLink III PC Card device. o If the 3Com PC Card device is recognized, the pcelx driver is automatically loaded, ports and IRQs allocated, and special files cre- ated (if they don't already exist). No manual configuration of the hardware is necessary or possible. Known Problems and Limitations Network services are automatically started when the system is booted. These services are not started when a network interface is added or shut down after the system has been brought up. CONFIGURATION
Configuration procedures include initial installation and configuration, identifying an unrecognized card and configuring two or more cards. Initial Installation and Configuration For initial installation and configuration, do the following steps: 1. Install the Solaris software. 2. Boot the system. 3. Insert the 3Com EtherLink III PC Card device. Identifying an Unrecognized Card If you insert a 3C589 card and it is not recognized (no special files created), use the prtconf command and attempt to identify the prob- lem: 1. Become root. 2. Run the prtconf -D command to see if your 3C589 card is recognized. A recognized device will appear in the prtconf output. For example: # prtconf -D . . . pcic, instance #0 (driver name: pcic) . . . network, instance #0 (driver name: pcelx) 3. If pcelx does not appear in the prtconf output, there is a problem with the PC Card adapter configuration or with the hardware. You can determine whether the problem is with the card or the adapter by attempting to use the card on another machine or by using it on the same machine using DOS. Configuring Two or More Cards Because the 3C589 card is not supported during Solaris installation, you must update network configuration files before it can be used as a network interface: 1. Create a /etc/hostname.pcelx# file (where # is a socket number) to specify the host name to be associated with this interface. 2. Add an IP address for the new host name to the /etc/inet/hosts file. 3. Ensure that the associated network is listed in /etc/inet/netmasks. 4. Ensure that the Name Service Switch /etc/nssswitch.conf configuration file includes the network and local services you need. 5. Reboot the system. Special Files Device naming in /dev follows standard LAN device naming with the exception that the PPA (physical point of attachment) unit number is the socket where the card resides, not the instance. For the pcelx driver, /dev/pcelx0 (or PPA 0 of /dev/pcelx) is the card in socket 0, while a card in socket 1 is /dev/pcelx1 (or PPA 1 of /dev/pcelx). Hot Plugging If you remove the 3C589 card, any information you send is discarded, and no error messages are given. When you reinsert the card in the same socket, the device operates normally. The behavior is similar to temporarily disconnecting the device from the network. /kernel/drv/pcelx pcelx driver /dev/pcelx DLPI Style 2 device /dev/pcelxn DLPI Style 1 device where: n is the PCMCIA physical socket number. pcmcia(7D) 20 Oct 2000 pcelx(7D)
All times are GMT -4. The time now is 04:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy