Not sure how cisco does PPPoE but shouldn't that make it easier being that it'd be a seperate interface, no?
Mark Odette II wrote: > > Good point there Chuck. I should have paid closer attention to that little > detail in my last post... DOH! > > The rest of what I said still stands though, as is the majority response- > NAT will have to be used. > > ... though, I must say, Darrell's most recent reply to this thread was > definitely interesting to me... never seen, or thought of that type of > solution before... Will have to keep that in mind for those single-interface > Cisco router situations. Of course, it probably won't work for PPPoE DSL, > unless you can specify "next-hop 'interface-name'" in the route map I > suppose. Hmm... very interesting. > > Mark Odette II > ... who should be in bed at this time (12:30am CST). :) > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Sunday, December 30, 2001 11:41 PM > To: [EMAIL PROTECTED] > Subject: Re: can't ping an address from anywhere but the router itself > [7:30514] > > I presume we all understand that 250.x.x.x is a fictitious address, i.e. is > used here as an example, and cannot legally be used for any reason. :-> > > If Pac Bell assigned you a /24, and stated that dot 254 is the DSL gateway, > do they mean that is your DSL router's ethernet port? that is, do you have a > different address for the DSL/ATM side of things? > > My own experience is you have to be careful about what Pac Bell says. > sometimes the terminology they use can be misleading to those of us in > Ciscoland. ;-> > > I would expect that you would be doing NAT between your inside ( 192.x.x.x ) > network and the public space you have been assigned. > > internet-----DSL_router---------firewall/router---------inside > > are you doing something different? > > Chuck > > ""Ole Drews Jensen"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > First of all John, I don't believe this is a very good way of doing this, > > because you are actually running two different networks on the same LAN: > > 192.168.0.0/24 and 250.100.100.238/8. > > > > Anyway, I believe the problem lies in that the DSL GATEWAY has a default > > gateway that points to PacBell, so when it receives a ping echo from your > > workstation on network 192.168.0.0/24, it see's that it's not on it's own > > network, and sends the ping reply to its default gateway, and your > > workstation never receives the reply. > > > > In order for ping to work, the traffic must be able to travel both > > directions. > > > > I don't know what kind of DSL gateway you have, but if you can tell it to > > route traffic destined for network 192.168.0.0/24 to the router > > (250.100.100.238), it should work, because the echo reply would then find > > its way back to the workstation you're pinging from. > > > > Hth, > > > > Ole > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Ole Drews Jensen > > Systems Network Manager > > CCNP, MCSE, MCP+I > > RWR Enterprises, Inc. > > [EMAIL PROTECTED] > > http://www.RouterChief.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > NEED A JOB ??? > > http://www.oledrews.com/job > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > -----Original Message----- > > From: John Mairs [mailto:[EMAIL PROTECTED]] > > Sent: Friday, December 28, 2001 4:27 PM > > To: Ole Drews Jensen > > Subject: RE: can't ping an address from anywhere but the router itself > > [7:30328] > > > > > > Im sorry, you're right, my explanation was not very > > clear. the inside network is 192.168.0.0/24 and all > > devices on that network are hosts. the addresses for > > the list you have below is. lets say > > > > 250.100.100.254/24 (DSL gateway) > > 250.100.100.238/24 (Static IP assigned to me from > > pacbell assigned to e0 to) > > 250.100.100.230/24 (for fun my printer) > > > > I can, from any host on the 192.168.0.0/24 (inside > > network [192.168.0.1 e0 secondary) successfully ping > > .238 and .230 but not .254 > > > > from the router I can successfully ping everything > > including the gateway (.254). > > > > if I can ping .238 and the printer .230 from the > > inside network (which means that the 2501 is resolving > > or routing those addresses on the outside network) I > > don't understand why .254 in unreachable (times out) > > > > here is the config > > > > Router3#show conf > > using 886 pit pf 32762 bytes > > ! > > version 11.2 > > no service password-encryption > > no service udp-small-servers > > no service udp-small-servers > > ! > > hostname Router3 > > ! > > enable secret 5 $1$llkfflkaiey.ddfakdjfadlkjrlll > > enable password cisco > > ! > > no ip domain-lookup > > ! > > interface ethernet0 > > ip address 192.168.0.1 255.255.255.0 secondary > > ip address 250.100.100.238 255.255.255.0 > > no mop enabled > > ! > > interface Serial0 > > no ip address > > ! > > interface Serial1 > > no ip address > > ! > > ip classless > > ip route 192.168.0.0 255.255.255.0 250.100.100.254 > > ! > > banner login ^C > > What in the hell do YOU want? > > > > ^C > > banner motd ^C > > By the way...how do you say "Elway" in pig latin? > > > > ^C > > ! > > line con 0 > > line aux 0 > > line vty 0 4 > > password cisco > > login > > ! > > end > > > > Router3# > > > > --- Ole Drews Jensen wrote: > > > Maybe it's just me, but I'm a little confused here. > > > > > > As far as I can read on your e-mail, you have the > > > following: > > > > > > On network 192.168.0.0 / 24 > > > > > > 192.168.0.230 Printer > > > 192.168.0.238 Router > > > 192.168.0.254 Gateway > > > > > > If you ping from the inside network to any of the > > > three devices (above), the > > > router should not route anything, because you're > > > pinging to the same network > > > you're on. > > > > > > I am not sure how exactly your whole setup is, but > > > you should check that the > > > subnet mask is / 24 (or 255.255.255.0) on all > > > devices on the 192.168.0.0 > > > network. > > > > > > Send the config from the router and gateway, plus a > > > description on how all > > > these things are connected. > > > > > > Hth, > > > > > > Ole > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > Ole Drews Jensen > > > Systems Network Manager > > > CCNP, MCSE, MCP+I > > > RWR Enterprises, Inc. > > > [EMAIL PROTECTED] > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > http://www.RouterChief.com > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > NEED A JOB ??? > > > http://www.oledrews.com/job > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > > -----Original Message----- > > > From: John Mairs [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, December 28, 2001 10:57 AM > > > To: [EMAIL PROTECTED] > > > Subject: can't ping an address from anywhere but the > > > router itself > > > [7:30316] > > > > > > > > > Hi, > > > > > > I have DSL with a static IP address/24. the gateway > > > address is x.x.x.254 and the static IP/24 address > > > that > > > I have assigned the router is x.x.x.238. for fun I > > > assigned x.x.x.230 to my printer. > > > > > > all addresses on the inside network are > > > 192.168.0.x/24. > > > > > > I can ping x.x.x.238 and x.x.x.230 but not x.x.x.254 > > > from the inside network. > > > > > > I can ping x.x.x.254 from the router (2501 with > > > secondary ethernet) > > > > > > I can't understand why the router will route to the > > > printer (x.x.x.230) but not the gateway (x.x.x.254) > > > > > > I am confused about my router's prejudicial ways. > > > > > > any thoughts > > > > > > ===== > > > John L. Mairs > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Send your FREE holiday greetings online! > > > http://greetings.yahoo.com > > [EMAIL PROTECTED] > > > > > > ===== > > John L. Mairs > > > > __________________________________________________ > > Do You Yahoo!? > > Send your FREE holiday greetings online! > > http://greetings.yahoo.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=30520&t=30520 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
