Why? What are you trying to accomplish with that? It sounds to me as if you're trying to fight symptoms while in fact you should be resolving the problem which caused those symptoms.How link up via network driver (igb and ix) without connecting the cable?
I try manual set media, but i have status "no carrier"![]()
Absolutely, but that probably has nothing to do with the "no carrier" error.Can I disable auto-negotiation?
Education task.Why? What are you trying to accomplish with that?
I tried, but still have status "no carrier"You could use ifconfig(8) to set up parameters such as media or mediaopts
Already did so (for fiber too).You might be able to trick it using a loopback plug.
Teacher linux fanat, linux have ethtool (autoneg off).Tell your teacher it's technically not possible to get the carrier active without actually having a carrier active.
Auto negotiation has nothing to do with carrier detection.Teacher linux fanat, linux have ethtool (autoneg off).
It won't help either, just recently I tried to "solve" a similar problem with exotic hardware configuration without transformers at PHY's. Since I didn't know that there was a problem in hardware (missing pull-ups), I thought ethtool can help, but it kept showing NOCARRIER anyway.linux have ethtool
I'll save you the search, if_tap(4):In Linux you can create a dummy interface. Try googling that for FreeBSD also.
The tap interface is a software loopback mechanism that can be loosely
described as the network interface analog of the pty(4), that is, tap
does for network interfaces what the pty(4) driver does for terminals.
The tap driver, like the pty(4) driver, provides two interfaces: an
interface like the usual facility it is simulating (an Ethernet network
interface in the case of tap, or a terminal for pty(4)), and a character-
special device ``control'' interface. A client program transfers Ether-
net frames to or from the tap ``control'' interface. The tun(4) inter-
face provides similar functionality at the network layer: a client will
transfer IP (by default) packets to or from a tun(4) ``control'' inter-
face.