08-04-2004
The listed article looks at auto negotiating from a 'switch' perspective, but doesn't address host issues. Depending on your OS, you can force settings. Which OS are you running? Here's a brief synopsis of some
Solaris NIC Control settings
Cheers,
Keith
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
The Lan card in one of our UIII WS's seem doesn't work,so with ping command i can not see any of the machines in LAN and with some other tests i'm sure it's not OK.
I tried to use the second card on PCI port ,but the replaced card was one of the ordinary card for PC's ...by the way after... (1 Reply)
Discussion started by: nikk
1 Replies
2. SCO
Dear all
Im facing one problem in SCO 5.0.5 , its that in the server there are three LAN cards INTEL PRO 100 series but when we configure all the three cards then LAN stops working . self ping is possible but no one can ping the server. If we remove driver of any one card LAN starts working.
Is... (1 Reply)
Discussion started by: ccvyas
1 Replies
3. Solaris
Hi,
i have a RealTek Lan Card on my machine. Does Solaris 9 supports this lan card .
Thank You,
Shafi (3 Replies)
Discussion started by: sol8admin
3 Replies
4. SCO
hi all
i have installed SCO 5.0.5 on a "Netfinity 5000" IBM server. But the OS is not detecting the lan card. how can i detect it.... help and thanks in advance .
bidhayak (3 Replies)
Discussion started by: bidhayakm
3 Replies
5. Programming
Please tell me API in Solaris / Linux / UNIX to get status information of LAN card. (1 Reply)
Discussion started by: mansoorulhaq
1 Replies
6. Linux
Hi.
I have a lan card installed on my server. I want to check the duplex speed of it. How can I check it?
Help is appreciated.
Thank you. (3 Replies)
Discussion started by: Amol21
3 Replies
7. Solaris
Received the Timed out message consistently when I tried to jumpstart an M5000 with:
boot jsnet:speed=1000,duplex=full - install
Made the error go away by adding link-clock parameter:
boot jsnet:speed=1000,duplex=full,link-clock=master - install
"link-clock=master" disables... (1 Reply)
Discussion started by: markoakley
1 Replies
8. Solaris
Hi,
I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10).
I've done the touch / reconfigure and devfsadm, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip... (7 Replies)
Discussion started by: kerrygold
7 Replies
9. Linux
Hi,
I have this problem on RHEL box. I am using two NIC's of same model and make (Intel 82557) in the adjacent PCI slots . I am using each one for different subnet and have assigned them ipaddresses and gateways of respective subnets . While one is O.K. connecting to its ... (5 Replies)
Discussion started by: dextergenious
5 Replies
10. Red Hat
we have red hat 6 linux box
There are two lan card
one lan card eth0 have ip 10.82.190.31/24 GW 10.82.190.254
2th lan card eth1 have ip 10.82.188.33/24 GW 10.82.188.254
I have below route ... I use two route table
root@xxx# netstat -rn
Kernel IP routing table
Destination Gateway ... (5 Replies)
Discussion started by: chuikingman
5 Replies
LEARN ABOUT DEBIAN
rgephy
RGEPHY(4) BSD Kernel Interfaces Manual RGEPHY(4)
NAME
rgephy -- RealTek RTL8168/8169/8110/8211 series 10/100/1000 Gigabit Ethernet PHY driver
SYNOPSIS
To compile all available PHY drivers into the kernel, place the following line in your kernel configuration file:
device miibus
Alternatively, to selectively compile this driver into the kernel, place the following lines in your kernel configuration file instead:
device mii
device rgephy
DESCRIPTION
The rgephy driver supports the RealTek RTL8168, RTL8169, RTL8110 and RTL8211 series integrated 10/100/1000 Gigabit Ethernet PHYs.
In order to get a list of media types and options supported by a specific instance of the rgephy driver, run ifconfig -m on the instance of
its parent MAC driver.
Additionally, the rgephy driver supports the following special media option:
flag0 When manually setting media type and options via ifconfig(8), the rgephy driver by default also triggers an autonegotiation advertis-
ing the selected media. This is done in order to work around hardware issues in certain scenarios. It is believed that this behavior
does not cause harm in general but in fact can have an adverse effect in edge cases. In order to manually set the media type and
options without also triggering an autonegotiation, the rgephy driver allows to turn this behavior off via the flag0 media option.
Note that this special media option will not show up in the output of ifconfig(8), even when set.
EXAMPLES
Manually set 100BASE-TX full-duplex without also triggering an autonegotiation:
ifconfig re0 media 100baseTX mediaopt full-duplex,flag0
SEE ALSO
intro(4), miibus(4), ifconfig(8)
BSD
January 16, 2011 BSD