Sponsored Content
Full Discussion: Not able to find the new NIC
Operating Systems Solaris Not able to find the new NIC Post 302516592 by solaris_user on Sunday 24th of April 2011 10:05:57 AM
Old 04-24-2011
Thanks for information guys Smilie
 

9 More Discussions You Might Find Interesting

1. Solaris

How do I find what kind of NIC card the server has?

All, I see that there are 2 nic card available . How can I know all the details about these 2 nic cards. -rw-r--r-- 1 root root 10 Apr 16 15:00 hostname.bge0 -rw-r--r-- 1 root other 17 Apr 22 08:56 hostname.bge2 please let me know thanks -prasad (4 Replies)
Discussion started by: p4cldba
4 Replies

2. Solaris

Cause of NIC changes ...?

Hi , I came across a SUN server whereby it was installed with additional ethernet card. By right in any configuration, you would probably see the onboard ports Net0,Net1 and so on should correspond to e1000g0,e1000g1... But instead the ext PCI takes precedence in the order and the Net0 becomes... (3 Replies)
Discussion started by: incredible
3 Replies

3. HP-UX

how can I determine which NIC card is virtual NIC Card

how can I determine which NIC card is virtual NIC Card which condition can make a decision Does HP UX have Virtual Network Adapter Concept if ,it has where I can Find if I Install Virutal Network Adapter or which command that i can get it or which software can generate thanks (2 Replies)
Discussion started by: alert0919
2 Replies

4. AIX

AIX -How to find which NIC is on which PCI card

Hi All, How can I find out which is ETH5 on my AIX P5 system. I have about seven different NIC card on this. I did move the cable to each one but still I was not able to see the link light up when I did netstat -v Any idea? Thanks. (2 Replies)
Discussion started by: samnyc
2 Replies

5. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

I couldn't install my nic in solaris 10. I compiled and added the driver but failed to attach the driver and ifconfig output shows only loopback dev. Please see the following output and tell me whether my nic has been detected and why the driver failed to attach? My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies

6. IP Networking

squid proxy: one NIC for inbound & one NIC for outbound?

I am new in squid proxy. My question is how to (and if it's necessary) to set one NIC for inbound traffic (http requests) and one NIC for outbound traffic (http answers)? Thank you in advance! (4 Replies)
Discussion started by: aixlover
4 Replies

7. Solaris

How can I find which NIC is used to talk to a given host (except traceroute)

Hi all, I'm having some trouble identifying what route is being used to talk to a target host. I can figure it out by looking at the routing tables but I want to automate this and don't much feel like scripting the network mask logic when I'd think there'd be a way to have the OS do it for me.... (5 Replies)
Discussion started by: Smiling Dragon
5 Replies

8. Red Hat

I want to tune NIC's rps, rfs and xps value. which NIC device should I modify.

Dear All I want tune my NIC's rps, rfs and xps value. In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1). Here is the question? Which device should I modify ? eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0) Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies

9. Linux

Add two different subnet public IPs to single NIC or two different NIC on same box

Hello Admins, My ask is how can I add two different subnet IPs to same box with two different gateways? The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware. How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
WVDIAL(1)						      General Commands Manual							 WVDIAL(1)

NAME
wvdial - PPP dialer with built-in intelligence. SYNOPSIS
wvdial --help | --version | --chat | --config | option=value | --no-syslog | section... DESCRIPTION
wvdial is an intelligent PPP dialer, which means that it dials a modem and starts PPP in order to connect to the Internet. It is something like the chat(8) program, except that it uses heuristics to guess how to dial and log into your server rather than forcing you to write a login script. When wvdial starts, it first loads its configuration from /etc/wvdial.conf and ~/.wvdialrc which contains basic information about the modem port, speed, and init string, along with information about your Internet Service Provider (ISP), such as the phone number, your username, and your password. Then it initializes your modem and dials the server and waits for a connection (a CONNECT string from the modem). It understands and responds to typical connection problems (like BUSY and NO DIALTONE). Any time after connecting, wvdial will start PPP if it sees a PPP sequence from the server. Otherwise, it tries to convince the server to start PPP by doing the following: - responding to any login/password prompts it sees; - interpreting "choose one of the following"-style menus; - eventually, sending the word "ppp" (a common terminal server command). If all of this fails, wvdial just runs pppd(8) and hopes for the best. It will bring up the connection, and then wait patiently for you to drop the link by pressin CTRL-C. OPTIONS
Several options are recognized by wvdial. --chat Run wvdial as a chat replacement from within pppd, instead of the more normal method of having wvdial negotiate the connection and then call pppd. --remotename Override the Remote Name setting in the dialer configuration section of the configuration file. This is mainly useful when you dial to multiple systems with the same user name and password, and you don't want to use inheritance to override this setting (which is the recommended way to do it). --config [configfile] Run wvdial with configfile as the configuration file (instead of /etc/wvdial.conf). This is mainly useful only if you want to have per-user configurations, or you want to avoid having dial-up information (usernames, passwords, calling card numbers, etc.) in a system wide configuration file. --no-syslog Don't output debug information to the syslog daemon (only useful together with --chat). --help Prints a short message describing how to use wvdial and exits. --version Displays wvdial's version number and exits. wvdial is normally run without command line options, in which case it reads its configuration from the [Dialer Defaults] section of /etc/wvdial.conf. (The configuration file is described in more detail in wvdial.conf(5) manual page.) One or more sections of /etc/wvdial.conf may be specified on the command line. Settings in these sections will override settings in [Dialer Defaults]. For example, the command: wvdial phone2 will read default options from the [Dialer Defaults] section, then override any or all of the options with those found in the [Dialer phone2] section. If more than one section is specified, they are processed in the order they are given. Each section will override all the sections that came before it. For example, the command: wvdial phone2 pulse shh will read default options from the [Dialer Defaults] section, then override any or all of the options with those found in the [Dialer phone2] section, followed by the [Dialer pulse] section, and lastly the [Dialer shh] section. Using this method, it is possible to easily configure wvdial to switch between different internet providers, modem init strings, account names, and so on without specifying the same configuration information over and over. BUGS
"Intelligent" programs are frustrating when they don't work right. This version of wvdial has only minimal support for disabling or over- riding its "intelligence", with the "Stupid Mode", "Login Prompt", and "Password Prompt" options. So, in general if you have a nice ISP, it will probably work, and if you have a weird ISP, it might not. Still, it's not much good if it doesn't work for you, right? Don't be fooled by the fact that wvdial finally made it to version 1.00; it could well contain many bugs and misfeatures. Let us know if you have problems by sending e-mail to <wvdial@nit.ca>. Also, there is now a mailing list for discussion about wvdial. If you are having problems, or have anything else to say, send e-mail to <wvdial-list@lists.nit.ca>. You may encounter some error messages if you don't have write access to /etc/ppp/pap-secrets and /etc/ppp/chap-secrets. Unfortunately, there's really no nice way around this yet. FILES
/etc/wvdial.conf Configuration file which contains modem, dialing, and login information. See /dev/ttyS* Serial port devices. /etc/ppp/peers/wvdial Required for correct authentication in pppd version 2.3.0 or newer. /etc/ppp/{pap,chap}-secrets Contains a list of usernames and passwords used by pppd for authentication. wvdial maintains this list automatically. AUTHORS
Dave Coombs and Avery Pennarun for Net Integration Technologies, as part of the Worldvisions Weaver project. We would like to thank SuSE and RedHat for adding a number of various cool features to Thanks guys! SEE ALSO
wvdial.conf(5), wvdialconf(1), pppd(8), chat(8). FAQ: http://www.dsb3.com/wvdial/ Worldvisions WvDial May 2001 WVDIAL(1)
All times are GMT -4. The time now is 02:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy