|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
Jason
Guest
|
 Posted: Wed Jan 09, 2008 4:21 am Post subject: Problems using the extended ping command |
 |
|
When I try to use the extended ping command and specify a source IP address
I am receiving an 'invalid source' error. I have tried many different
combinations but with no joy, it does, however, work if I specify an
iterface (such as serial 0). I've also tried this on my 2611 router with
the same results, even if I type '?' at the 'source address' prompt I still
receive an eror message - does anyone have any ideas?
TIA, Jase
EAGLE2#ping
Protocol [ip]:
Target IP address: 192.168.1.2
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.3.2
% Invalid source
Source address or interface: 10.0.0.1
% Invalid source
Source address or interface: serial 0
Type of service [0]:
Set DF bit in IP header? [no]:
EAGLE2 uptime is 24 minutes
System restarted by reload
System image file is "flash:c2500-d-l_120-11.bin"
cisco 2500 (68030) processor (revision L) with 6144K/2048K bytes of memory.
Processor board ID 06110204, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
1 ISDN Basic Rate interface(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102 |
|
| Back to top |
|
 |
|
|
Scooty
Guest
|
| Posted: Wed Jan 09, 2008 4:21 am Post subject: Re: Problems using the extended ping command |
|
|
On Jan 9, 7:21 am, Jason <SpamSpamS...@SpanishInquisition.co.uk>
wrote:
| Quote: | When I try to use the extended ping command and specify a source IP address
I am receiving an 'invalid source' error. I have tried many different
combinations but with no joy, it does, however, work if I specify an
iterface (such as serial 0). I've also tried this on my 2611 router with
the same results, even if I type '?' at the 'source address' prompt I still
receive an eror message - does anyone have any ideas?
TIA, Jase
EAGLE2#ping
Protocol [ip]:
Target IP address: 192.168.1.2
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.3.2
% Invalid source
Source address or interface: 10.0.0.1
% Invalid source
Source address or interface: serial 0
Type of service [0]:
Set DF bit in IP header? [no]:
EAGLE2 uptime is 24 minutes
System restarted by reload
System image file is "flash:c2500-d-l_120-11.bin"
cisco 2500 (68030) processor (revision L) with 6144K/2048K bytes of memory..
Processor board ID 06110204, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
1 ISDN Basic Rate interface(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102
|
Can you do a sh ip int brief and post the results? |
|
| Back to top |
|
|
Thrill5
Guest
|
| Posted: Wed Jan 09, 2008 10:53 am Post subject: Re: Problems using the extended ping command |
|
|
The source address you specify must be configured on an interface on the
router and be in an UP/UP state. You can't just pick one at random,
otherwise how does the router get the replies?
"Jason" <SpamSpamSpam@SpanishInquisition.co.uk> wrote in message
news:Xns9A1FE37C7946DSpamSpamSpamSpanishI@140.99.99.130...
| Quote: | When I try to use the extended ping command and specify a source IP
address
I am receiving an 'invalid source' error. I have tried many different
combinations but with no joy, it does, however, work if I specify an
iterface (such as serial 0). I've also tried this on my 2611 router with
the same results, even if I type '?' at the 'source address' prompt I
still
receive an eror message - does anyone have any ideas?
TIA, Jase
EAGLE2#ping
Protocol [ip]:
Target IP address: 192.168.1.2
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.3.2
% Invalid source
Source address or interface: 10.0.0.1
% Invalid source
Source address or interface: serial 0
Type of service [0]:
Set DF bit in IP header? [no]:
EAGLE2 uptime is 24 minutes
System restarted by reload
System image file is "flash:c2500-d-l_120-11.bin"
cisco 2500 (68030) processor (revision L) with 6144K/2048K bytes of
memory.
Processor board ID 06110204, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
1 ISDN Basic Rate interface(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102 |
|
|
| Back to top |
|
|
Jason
Guest
|
| Posted: Wed Jan 09, 2008 3:05 pm Post subject: Re: Problems using the extended ping command |
|
|
"Thrill5" <nospam@somewhere.com> wrote in news:-
radnVkw0q_MzhnanZ2dnUVZ_uWlnZ2d@comcast.com:
| Quote: | The source address you specify must be configured on an interface on
the
router and be in an UP/UP state. You can't just pick one at random,
otherwise how does the router get the replies?
"Jason" <SpamSpamSpam@SpanishInquisition.co.uk> wrote in message
news:Xns9A1FE37C7946DSpamSpamSpamSpanishI@140.99.99.130...
When I try to use the extended ping command and specify a source IP
address
I am receiving an 'invalid source' error. I have tried many different
combinations but with no joy, it does, however, work if I specify an
iterface (such as serial 0). I've also tried this on my 2611 router
with
the same results, even if I type '?' at the 'source address' prompt I
still
receive an eror message - does anyone have any ideas?
TIA, Jase
EAGLE2#ping
Protocol [ip]:
Target IP address: 192.168.1.2
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.3.2
% Invalid source
Source address or interface: 10.0.0.1
% Invalid source
Source address or interface: serial 0
Type of service [0]:
Set DF bit in IP header? [no]:
EAGLE2 uptime is 24 minutes
System restarted by reload
System image file is "flash:c2500-d-l_120-11.bin"
cisco 2500 (68030) processor (revision L) with 6144K/2048K bytes of
memory.
Processor board ID 06110204, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
1 ISDN Basic Rate interface(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102
|
The source address I'm using is on another router which can't ping the
destination address, I'm troubleshooting the problem & running the
extended ping from this router as if the ping had originated on the
other. Both routers in question can ping each other fine, this seems
similar to examples I've seen on Cisco's site regarding the extended
ping command.
Jase |
|
| Back to top |
|
|
alexd
Guest
|
| Posted: Wed Jan 09, 2008 3:24 pm Post subject: Re: Problems using the extended ping command |
|
|
On Wed, 09 Jan 2008 09:05:02 +0000, Jason wrote:
| Quote: | The source address I'm using is on another router which can't ping the
destination address, I'm troubleshooting the problem & running the
extended ping from this router as if the ping had originated on the
other. Both routers in question can ping each other fine, this seems
similar to examples I've seen on Cisco's site regarding the extended
ping command.
|
Similar, but differing in one small regard: you're setting the source
address to be that of a different router, and it won't work.
--
<http://ale.cx/> (AIM:troffasky) (UnSoEsNpEaTm@ale.cx)
09:23:20 up 3 days, 23:47, 2 users, load average: 1.17, 1.18, 1.12
2x Broadband/IT/Telecoms support positions in Newcastle city centre.
For more info call 0191 229 8870 and ask for Steve. No agencies. |
|
| Back to top |
|
|
Jason
Guest
|
| Posted: Wed Jan 09, 2008 4:25 pm Post subject: Re: Problems using the extended ping command |
|
|
alexd <troffasky@hotmail.com> wrote in news:478492cf$0$513$bed64819
@news.gradwell.net:
| Quote: | On Wed, 09 Jan 2008 09:05:02 +0000, Jason wrote:
The source address I'm using is on another router which can't ping the
destination address, I'm troubleshooting the problem & running the
extended ping from this router as if the ping had originated on the
other. Both routers in question can ping each other fine, this seems
similar to examples I've seen on Cisco's site regarding the extended
ping command.
Similar, but differing in one small regard: you're setting the source
address to be that of a different router, and it won't work.
|
Thanks for clearing that up, I'd made some incorrect assumptions. |
|
| Back to top |
|
|
Barry Margolin
Guest
|
| Posted: Wed Jan 09, 2008 4:42 pm Post subject: Re: Problems using the extended ping command |
|
|
In article <Xns9A206A08DFF40spamspamspamSpanishI@140.99.99.130>,
Jason <spamspamspam@SpanishInquisition.co.uk> wrote:
| Quote: | alexd <troffasky@hotmail.com> wrote in news:478492cf$0$513$bed64819
@news.gradwell.net:
On Wed, 09 Jan 2008 09:05:02 +0000, Jason wrote:
The source address I'm using is on another router which can't ping the
destination address, I'm troubleshooting the problem & running the
extended ping from this router as if the ping had originated on the
other. Both routers in question can ping each other fine, this seems
similar to examples I've seen on Cisco's site regarding the extended
ping command.
Similar, but differing in one small regard: you're setting the source
address to be that of a different router, and it won't work.
Thanks for clearing that up, I'd made some incorrect assumptions.
|
This option in extended ping is NOT for spoofing, it's just there to let
you select which of the router's addresses to use. By default it uses
the address of the outgoing interface. But if you have a router
connecting nets A and B, and you want to test whether machines on net A
(or beyond) can reach net B, you can use this option to specify the
router's net B address while pinging.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group *** |
|
| Back to top |
|
|
|
|
|
|
