Cisco Cisco 1800 2800 3800 Series 4-Port EtherSwitch High-Speed WIC Information Guide
Q&A
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 15 of 19
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static
route
route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
66.0.0.0/32 is subnetted, 1 subnets
C 66.174.50.7 is directly connected, Cellular0/2/0
10.0.0.0/24 is subnetted, 1 subnets
C 10.242.5.0 is directly connected, FastEthernet0/0
166.159.0.0/32 is subnetted, 1 subnets
C 166.159.147.238 is directly connected, Cellular0/2/0
S* 0.0.0.0/0 is directly connected, Cellular0/2/0
A.
Q.
A.
Q.
A.
Typically, on a point-to-point interface both IP addresses are on the same interface. However,
some service providers assign IP addresses that are in different subnets, and both IP
addresses are negotiated using IPCP. Normally both IP addresses belong to the same subnet,
but because the IP addresses negotiated belong to two different subnets, both routes need to
be installed in the routing table. This behavior is the right behavior; otherwise, the router
cannot forward packets.
some service providers assign IP addresses that are in different subnets, and both IP
addresses are negotiated using IPCP. Normally both IP addresses belong to the same subnet,
but because the IP addresses negotiated belong to two different subnets, both routes need to
be installed in the routing table. This behavior is the right behavior; otherwise, the router
cannot forward packets.
My customer has the link up as the primary connection. The customer can pass traffic
through the primary connection, but cannot ping or perform Telnet into the router over
the Internet from another location.
The ping problem might be due to the fact that the IP address obtained from the provider is a
dynamic address and within the provider pool. Hence a ping to this interface might be failing
because of the policies set by the service provider. The workaround is to request a static public
IP address that is dedicated to your customer; this workaround, however, costs a bit more.
The ping problem might be due to the fact that the IP address obtained from the provider is a
dynamic address and within the provider pool. Hence a ping to this interface might be failing
because of the policies set by the service provider. The workaround is to request a static public
IP address that is dedicated to your customer; this workaround, however, costs a bit more.
My customer has problems when trying to ping with a domain name, but does not have
problems pinging with IP addresses.
Add the following CLI under the cellular interface:
Add the following CLI under the cellular interface:
ppp ipcp dns request
interface Cellular0/3/0
ip address negotiated
encapsulation ppp
dialer in-band
dialer string gsm
dialer-group 1
async mode interactive
ppp chap hostname Cisco
ppp chap password 0 Cisco
ppp ipcp dns request