Sponsored Content
Full Discussion: OSI interface...
Operating Systems Solaris OSI interface... Post 302236678 by incredible on Tuesday 16th of September 2008 04:47:04 AM
Old 09-16-2008
Why don't you post this to the Networking guys.. They'll be more perfect on this.
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

What are the 7 layers of OSI model or TCP/IP

what is it?? I looked everywhere but cant seem to find it also where can I get information about the difference between NFS 2 or NFS 3?? (6 Replies)
Discussion started by: TRUEST
6 Replies

2. IP Networking

The OSI-model

after reading a paper about the OSI-model I'm not exactly sure how to look at this model. Does data (a file) travel from the application level "down" each layer at the client Application V Presentation V Session V Transport V Network V Data link V | | | (Physical) | (3 Replies)
Discussion started by: J.P
3 Replies

3. Solaris

OSI 9.0 Installation

Dear After i received a demo license for OSI 9.0 from SUN , i installed the packages . but when i tried to start the osinet deamon ( /etc/rc2.d/S90osinet ) i am getting the foellowing errror # ./S90osinet start starting osi daemon/usr/sbin/osinetd cannot find a valid license (STACK 9.0)... (4 Replies)
Discussion started by: itsgeorge
4 Replies

4. Solaris

OSI 9.0 Installation some question

Hi. I get the folloing message if i try to start the osinet deamon: # /etc/rc2.d/S90osinet start starting osi daemonunable to unload all the osi modules some OSI applications may be running unable to start OSI daemon # Has anyone an idea what is going wrong? Answers to mail: (Note... (1 Reply)
Discussion started by: morenqfj
1 Replies

5. Solaris

Command line Interface or GUI Interface not shown on solaris

Dear all, I am a newbie in solaris and I need your advice. I have a Solaris version 5.9 installed on Sunfire V240. I am able to ssh the machine from putty remotely. My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies

6. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies

7. Debian

OSI application for Debian...

Is there OSI telecom application which can be installed on debian similar to Solstice Solaries OSI ? I need to get it on debian to build cmise and communicate with Network element . (0 Replies)
Discussion started by: atiato
0 Replies

8. Solaris

Unable to start OSI deamon

dear all, i am working on test server with solaris 10 , after installing OSI deamon i stopped it for a test now when i am starting again i am getting this message that i ggoled and search evrywhere and haven't any response i will be glade for any help in here mate the error was : ./osinet... (1 Reply)
Discussion started by: semaan
1 Replies
NFE(4)							   BSD Kernel Interfaces Manual 						    NFE(4)

NAME
nfe -- NVIDIA nForce MCP Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device nfe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_nfe_load="YES" DESCRIPTION
The nfe driver supports PCI Ethernet adapters based on the NVIDIA nForce Media and Communications Processors (MCP), such as the nForce, nForce 2, nForce 3, CK804, MCP04, MCP51, MCP55, MCP61, MCP65, MCP67, MCP73, MCP77 and MCP79 Ethernet controller chips. Supported features include (hardware support provided): o Receive/Transmit IP/TCP/UDP checksum offload o Hardware VLAN tag insertion/stripping o TCP segmentation offload (TSO) o MSI/MSI-X o Jumbo Frames Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The nfe driver supports the following media types: autoselect Enable autoselection of the media type and options. 10baseT/UTP Set 10Mbps operation. 100baseTX Set 100Mbps (Fast Ethernet) operation. 1000baseT Set 1000Mbps (Gigabit Ethernet) operation (recent models only). The nfe driver supports the following media options: half-duplex Force half duplex operation. full-duplex Force full duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The nfe driver supports the following NVIDIA MCP onboard adapters: o NVIDIA nForce MCP Networking Adapter o NVIDIA nForce MCP04 Networking Adapter o NVIDIA nForce 430 MCP12 Networking Adapter o NVIDIA nForce 430 MCP13 Networking Adapter o NVIDIA nForce MCP51 Networking Adapter o NVIDIA nForce MCP55 Networking Adapter o NVIDIA nForce MCP61 Networking Adapter o NVIDIA nForce MCP65 Networking Adapter o NVIDIA nForce MCP67 Networking Adapter o NVIDIA nForce MCP73 Networking Adapter o NVIDIA nForce MCP77 Networking Adapter o NVIDIA nForce MCP79 Networking Adapter o NVIDIA nForce2 MCP2 Networking Adapter o NVIDIA nForce2 400 MCP4 Networking Adapter o NVIDIA nForce2 400 MCP5 Networking Adapter o NVIDIA nForce3 MCP3 Networking Adapter o NVIDIA nForce3 250 MCP6 Networking Adapter o NVIDIA nForce3 MCP7 Networking Adapter o NVIDIA nForce4 CK804 MCP8 Networking Adapter o NVIDIA nForce4 CK804 MCP9 Networking Adapter LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.nfe.msi_disable Whether or not MSI support is enabled in the driver. The default value is 0. hw.nfe.msix_disable Whether or not MSI-X support is enabled in the driver. The default value is 0. SYSCTL VARIABLES
The following sysctl(8) variables can be used to modify or monitor nfe behavior. dev.nfe.%d.process_limit Maximum number of Rx events to be processed in the event loop before rescheduling a taskqueue. The accepted range is 50 to 255, the default value is 192. The interface does not need to be brought down and up again before a change takes effect. SEE ALSO
altq(4), arp(4), intro(4), miibus(4), netintro(4), pci(4), polling(4), rgephy(4), sysctl(8), ifconfig(8) HISTORY
The nfe device driver first appeared in OpenBSD 3.9, and then in FreeBSD 7.0. AUTHORS
The nfe driver was written by Jonathan Gray <jsg@openbsd.org> and Damien Bergamini <damien@openbsd.org>. The nfe driver was ported to FreeBSD by Shigeaki Tagashira <shigeaki@se.hiroshima-u.ac.jp>. BSD
January 15, 2011 BSD
All times are GMT -4. The time now is 05:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy