interesting question. without tearing up my pod to set up a QD, let me try
a little logic here.
when the router checks its FIB, and determines that the packet in question
is to go out a particular interface ( as opposed to a network ) what happens
then? does the router place that packet onto the
Chuck shaped electrons, photons, and little dot things to say:
interesting question. without tearing up my pod to set up a QD, let me try
a little logic here.
when the router checks its FIB, and determines that the packet in question
is to go out a particular interface ( as opposed to a network
Michael L. Williams wrote:
Paul Lalonde wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
but
routing out via an Ethernet interface will likely just *drop* the packet
onto that broadcast domain (subnet) without pointing it to a specific
next
hop.
This raises an
Marty Adkins wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
One might think that a static route to a broadcast interface type would be
ambiguous for layer 2, and it is. But what IOS does in that case is just
ARP for the destination IP and hope it gets an answer. It will work,
Wow Thank you all, I have definitely learned a lot from this. When I do sh
IP route I can see that I am getting a default route from the cable
provider. Earlier when I was trying to figure out this problem I was running
several debugs and I saw encapsulation failed errors which is in line with
Hi guys/gals,
I am using a 1605R with 2 ethernet interfaces as
gateway to my cable service provider. My dilemma is
that when I put a default route to outside NAT stops
working. I verified this by using a sniffer. Without
default route everything seems to work fine but it's
just bugging the hell
When you have ths default route in place, and do a 'show ip route' what does
your routing table show?
Mike W.
John Zaggat wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi guys/gals,
I am using a 1605R with 2 ethernet interfaces as
gateway to my cable service provider. My
Router#sh ip route
Codes: C - connected, S - static, I - IGRP, 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, E -
Here is sh ip routeRouter#sh ip route
Codes: C - connected, S - static, I - IGRP, 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
John,
Two things I can think of:
1. The cable provider is probably providing you with a default gateway
*anyways* in your DHCP request. Likely, you don't need that static route
after all.
2. As far as I can tell, your route wouldn't work in any event. Routing out
via a physical interface
Strange... it says gateway of last resort if 0.0.0.0 to network
0.0.0.0... appears it's trying to route everything to itself so to
speak.. in most examples and cases, I've seen something like this:
Gateway of last resort is 161.44.192.2 to network 198.10.1.0
Perhaps instead of using the
The interesting thing is that I see the packet on the outside wire trying to
reach it's destination. I used sniffer to test this. So basically
when I have this route in place I go to a workstation on the inside network
and ping a public address. I get the ICMP query being performed but
Correction I meant the ICMP request instead of DNS query. Sorry
JZ wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
The interesting thing is that I see the packet on the outside wire trying
to
reach it's destination. I used sniffer to test this. So basically
when I have this
Paul Lalonde wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
but
routing out via an Ethernet interface will likely just *drop* the packet
onto that broadcast domain (subnet) without pointing it to a specific next
hop.
This raises an interesting question: If you try to make a
14 matches
Mail list logo
