From: Brian Hescock (bhescock@xxxxxxxxx)
Date: Sat Oct 20 2001 - 20:58:39 GMT-3
I hadn't seen this on the list before, my apologies if it's been around
before. I was doing some ipx filtering and came across something
interesting when doing some debugs to figure out why my access-list
wasn't blocking between a specific source and destination netork:
- typical ipx router eigrp only config: ipx pings sourced off ipx
outgoing network number
- ipx router nslp: ipx internal network is required and pings are
sourced off that internal ipx network number
- ipx router nslp and ipx router eigrp with ipx eigrp on outbound
interface only: uses ipx internal network number, not the outbound
interface (surprised me)
- only ipx router eigrp with ipx internal network number: uses the
internal network number, not the outbound ipx interface. I typically
haven't used ipx internal network number unless using nlsp so I hadn't
discovered this behavior before and it how you do need to think about it
when setting up filtering for ipx pings.
anyway, thought it was interesting and passing it on to everyone. cheers,
Brian
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:22 GMT-3