![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| IP Networking Learn TCP/IP, Internet Protocol, Routing, Routers, Network protocols in this UNIX and Linux forum. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Real memory usage is reaching 99.99% | Balajipoola007 | AIX | 2 | 04-01-2009 05:26 AM |
| Linux LiveCD Router 2.0.40 (Default Router branch) | iBot | Software Releases - RSS News | 0 | 12-27-2008 09:20 AM |
| Linux LiveCD Router 2.0.30 (Default Router branch) | iBot | Software Releases - RSS News | 0 | 09-05-2008 07:50 AM |
| Linux LiveCD Router 2.0.29 (Default Router branch) | iBot | Software Releases - RSS News | 0 | 06-17-2008 01:10 AM |
| Linux LiveCD Router 2.0.27 (Default Router branch) | iBot | Software Releases - RSS News | 0 | 05-14-2008 07:30 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
trouble reaching local router interface
I have a processor (Solaris 5.8) with a router locally attached.
We're having trouble pinging the router interface from the processor with a normal ping command. The response from the router is "administratively prohibited", which normally indicates the access list on the router is bouncing the icmp request back. However, when I issue the ping command with the '-r' parameter (ping -r x.x.x.x), the response is immediately successful. When using '-r', the TTL is limited to one, and the ping is sent to a host on an attached network. The man pages state that normal routing tables are bypassed. With both methods, our network capture shows icmp leaving x.x.x.104 (solaris processor) destined for x.x.x.126 (router interface). I cannot see much difference besides that in the two packets, besides the TTL. FWIW, 'netstat -nr' is showing my default gateway to be x.x.x.126. Anyone have any ideas how I can figure out what's going on? |