Talk:Wildcard masks

From Internetworkpro

Jump to: navigation, search

This is an invaluable article! It was uncanny to read this line - it was as if I was being described: "I think it is in most people’s nature to correlate wildcard masks to subnet masks, which is a major pitfall. You cannot think of a wildcard mask as a subnet mask even if you were taught to just do the inverse of a subnet mask to get your wildcard bits."

I was under the mistaken impression that wildcard masks, being the inverse of subnet masks, had to have all 0's from the left until the 1st 1, then all 1's. Yuk!

Many new possibilities are now open to me. Thanks!'

Steve

[edit] Either there's a mistake here or I am missing something major

I am talking about the "If we entered this in the form of an ACL into a Cisco router then the router would automatically change the address matched against the wildcard to 192.168.10.0." part

We worked with 192.168.15.0 - 192.168.15.255 before, why would we suddenly start talking about 192.168.10.0?

I think it should be 192.168.15.0

Correct me if I am wrong

Personal tools
Namespaces
Variants
Actions
Navigation
Categories
Toolbox