Keresés

Új hozzászólás Aktív témák

  • tusi_

    addikt

    válasz McSzaby #6454 üzenetére

    Cisco egyik interface a tp-linkbe, ip add dhcp, ip nat outside.
    Másik intface ip add 10.0.0.1 255...... no shut ip nat ins.
    global. ip name-server 4.2.2.2 8.8.8.8

    ip dhcp pool inside
    network 10.0.0.0 /24
    default-router 10.0.0.1
    dns 4.2.2.2 8.8.8.8
    lease 0 8 0

    Egyébként miért nem hagyod ki a tplinket?? Lefogadom, sosem fox olyannal talizni, hogy egy tp-link mögé kell Cisco-t konfigolnod :P :R

    Nézd meg a sh int status paranccsal, hogy mi a negotiated speed és duplex mód, mert lehet, hogy a cisco és a tp.link között valami gáz van.

    [ Szerkesztve ]

    eat, sleep, play, replay

  • FecoGee

    Topikgazda

    válasz McSzaby #6454 üzenetére

    Szia!

    What’s wrong: A static default route pointing to an interface indicates that the rest of the Internet is reachable through that interface as a single flat network. Every destination address is reachable directly through that interface.

    Why does the problem occur on an Ethernet interface and not on a point-to-point link: The router does not need to know the layer-2 address of its neighbor on a point-to-point link; it has a single neighbor and the layer-2 encapsulation is static. On a multi-access interface the router has to match the destination IP address with a layer-2 address of the next-hop router or host. A static route pointing to an interface is an equivalent of telling the router that all the addresses covered by the static route’s IP prefix are directly connected.

    How does the router react: Since every IP address on the Internet is supposedly directly connected, the router needs the layer-2 MAC address of every destination host if it wants to forward the IP traffic to it. For every new destination IP address the router sends an ARP request and drops all IP packets until the ARP request is resolved. This also explains the high CPU utilization caused by the ARP process.

Új hozzászólás Aktív témák