1
\$\begingroup\$

I made an Ethernet switch using the Microchip KSZ8895 chip. To verify the hardware, I connected my computer to one of the ports. I used the command "Get-NetAdapter | SELECT name, * | where name -eq 'Ethernet 3'" in PowerShell via CMD to retrieve Ethernet information, as you can see below. According to this information, the Ethernet is active, running in full duplex mode, and operating at 100Mb. I set the subnet mask to 255.255.255.0, connected two computers to this Ethernet switch, and tried to ping, but it didn't work. What could be the reason? Or does the output of the command "Get-NetAdapter | SELECT name, * | where name -eq 'Ethernet 3'" guide us correctly?

img1

img2

I thought there might be a problem with autonegotiation, so I set both the Ethernet switch and the computer to autonegotiation. However, the result didn't change

\$\endgroup\$
1
  • 1
    \$\begingroup\$ please do not post pictures of text, post the text instead \$\endgroup\$
    – jsotola
    Commented Sep 26 at 9:41

1 Answer 1

0
\$\begingroup\$

You should let both ends of the link auto-assign link-local addresses of the form 169.254.0.0 with netmask 255.255.0.0. This is default behavior and you don't need to override it. That's how any modern OS behaves when there's no DHCP server available on the network being connected to.

Then the two nodes will be able to communicate. You obviously have to look up the address on both ends of the link if you're sending unicast traffic - e.g. unicast ping as you did.

\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.