sinkhole routing. While this may sound a lot like some Star Trek episode, it’s important for us to understand what each is, and more so how to implement them. Sinkholes are designed to attract traffic and keep it (for analysis or whatever reason). Blockhouse, on the other hand, are designed to attract traffic and never let it be seen again. In larger networks (and what we simulate in our CCIE labs) both of these techniques are typically done via BGP. So let’s start with the sinkhole idea. To create a sinkhole, we want to attract traffic. The first question we need to ask is Why? Whenever you advertise a network out, you inadvertently attract traffic to that IPs. That traffic may be good, or it may be bad. From a security perspective, I’m sure everyone has heard the term Honeypot used before. There is a specific purpose to attract traffic. So let’s say that you have a /24 network advertising to the Internet through various connections. Traffic can come in and wend its way through your network to the destination network segment. You notice a Dos attack, or some huge amount of traffic towards one of your web servers. Where do you secure against this? How do you secure against it? Are you still moving traffic all the way through your network to one final router before the segment? Are you tying up all your link’s bandwidth while doing this? Sinkholes spread throughout your network are a way to break apart and analyze the traffic, perhaps cleaning it and moving the good stuff on through. But multiple routers would need a focal point, or different way to route that traffic. You may simply change the destination for a single IP out of that /24. Most-specific routing always wins, so that’s an easy way. Maybe you have multiple analysis points in your network to segment the traffic and reduce load and bottlenecks in your topology. Either way, follow the lab instructions and you are creating a sinkhole. You may even be advertising extra networks just to attract traffic for analysis (like a Honeypot idea). Just watch what’s being asked, but that’s the concept of a sinkhole. Blackhole routing on the other hand wants to kill traffic. Simply enough, we could go to all of our routers and install some Null0 routes. In real life, this is not a scalable approach. Hence the term remotely-triggered blackhole routing, and we’ll use BGP. Killing a route via a routing protocol is not a simple concept. No matter how hard we try when advertising a route, Null0 is not a valid next-hop to pass along to someone else! So every router needs to have a seed route to Null0. Pick something that isn’t used. Ip route 1.1.1.1 255.255.255.255 null0 That goes on every single router now. Of course, we would also have BGP setup between all of our internal routers. Perhaps not really moving any “real” routing information, just used to kill things. Now we need the trigger. On a central router (wherever an admin is anyway) we’ll do our maintenance for what routes we want to kill. Ip route 192.0.0.0 255.0.0.0 null0 tag 86 ip route 100.100.100.0 255.255.255.0 null0 tag 86 ip route 200.200.200.0 255.255.255.0 null0 tag 86 Notice the tag on those static routes. This will be used for redistribution to help only get the “bad” routes from a router that may actually have many other static routes. Ok, not in the real lab, but we’re pretending that the skills we learn on our way to CCIE have some real-life intrinsic value, right? So once we have decided on our central router what routes we want to kill everywhere, then we pass them out through BGP. Route-map KillRoutes permit 10 Match tag 86 Router bgp 65000 Redistribute static route-map KillRoutes That all seems very simple, right? Well, yes it does, but it won’t help us. At this point, all of our iBGP routers would see the central router as the next hop for each of the routes. Ok, yes, that creates a blackhole. Because it pulls all of the packets into the middle of our network and then kills them locally with a Null0 next-hop. But we are wasting LOTS of bandwidth in doing this. Always filter as close to the source as possible. Good design rules! In order to do this, we need to change the next hop of the route from our central router’s IP address to that of the distributed Null0 route (1.1.1.1 in my example). Route-map NH-Change permit 10 Match tag 86 Set ip next-hop 1.1.1.1 Route-map NH-Change permit 20 Router bgp 65000 Neighbor x.x.x.x route-map NH-Change out (repeat for each of your neighbors unless you’re using peer groups!) The last permit statement of the route-map was to pass-through any other routes that you may want to run in BGP unchanged. Only make the next-hop change for those routes that are evil. You could also set this next-hop within the original redistribute route-map. I just split it out for pointing out the differences. At this point, all of your other routers have learned some routes via iBGP, with a next-hop of 1.1.1.1 and since they have a local static route to Null0 for that next hop, all routes learned this way will be killed. We have now used blackhole routing in a remotely-triggered manner. Kinda cool, huh? Not difficult either, just a matter of thinking about what we are trying to accomplish. As noted, these techniques have been listed more explicitly on both the Security (2.0) and Service Provider CCIE tracks. I don’t see any reason why they can’t be used in Routing & Switching as well, so it never hurts to think these things through! For some extra information, check out: scenario carefully. Makes notes and diagrams as necessary, but think like the router does. Think things through one step at a time and all of these complicated things suddenly become much easier. Cheers, Scott Scott Morris is IPexpert’s Vice President of Curriculum and Senior Technical Instructor. With over 20 years of technical training and consulting experience and a wealth of technical certifications, Scott Morris has proven to be among the elite in the technical training industry. Scott is one of the few people in the world who currently hold four separate CCIE certifications, but is one-of-a-kind by having added Juniper Network’s expert level certification. He is also actively preparing for the CCIE Voice. Scott has years of experience both writing and teaching CCIE lab preparation materials with an outstanding track record of success. Over the past seven years, Scott has also been involved in many aspects of training directly for Cisco’s internal staff on a variety of advanced technical topics. His knowledge and real-world experiences have been sought after for many projects. Scott has also participated in editing, writing and reviewing training books for Cisco Press, Wylie, Sybil, Que. Publishing and McGraw-Hill. His contributing author work includes Cisco Press’ Managing Cisco Network Security book ( ISBN: 1578701031) – Chapters on the PIX Firewall; and Cisco Press’ CCIE Practical Studies, Vol. 2 (ISBN: 1587050722) – Chapter on Multicast. Scott can be reached sinkhole routing. While this may sound a lot like some Star Trek episode, it’s important for us to understand what each is, and more so how to implement them. Sinkholes are designed to attract traffic and keep it (for analysis or whatever reason). Blockhouse, on the other hand, are designed to attract traffic and never let it be seen again. In larger networks (and what we simulate in our CCIE labs) both of these techniques are typically done via BGP. So let’s start with the sinkhole idea. To create a sinkhole, we want to attract traffic. The first question we need to ask is Why? Whenever you advertise a network out, you inadvertently attract traffic to that IPs. That traffic may be good, or it may be bad. From a security perspective, I’m sure everyone has heard the term Honeypot used before. There is a specific purpose to attract traffic. So let’s say that you have a /24 network advertising to the Internet through various connections. Traffic can come in and wend its way through your network to the destination network segment. You notice a Dos attack, or some huge amount of traffic towards one of your web servers. Where do you secure against this? How do you secure against it? Are you still moving traffic all the way through your network to one final router before the segment? Are you tying up all your link’s bandwidth while doing this? Sinkholes spread throughout your network are a way to break apart and analyze the traffic, perhaps cleaning it and moving the good stuff on through. But multiple routers would need a focal point, or different way to route that traffic. You may simply change the destination for a single IP out of that /24. Most-specific routing always wins, so that’s an easy way. Maybe you have multiple analysis points in your network to segment the traffic and reduce load and bottlenecks in your topology. Either way, follow the lab instructions and you are creating a sinkhole. You may even be advertising extra networks just to attract traffic for analysis (like a Honeypot idea). Just watch what’s being asked, but that’s the concept of a sinkhole. Blackhole routing on the other hand wants to kill traffic. Simply enough, we could go to all of our routers and install some Null0 routes. In real life, this is not a scalable approach. Hence the term remotely-triggered blackhole routing, and we’ll use BGP. Killing a route via a routing protocol is not a simple concept. No matter how hard we try when advertising a route, Null0 is not a valid next-hop to pass along to someone else! So every router needs to have a seed route to Null0. Pick something that isn’t used. Ip route 1.1.1.1 255.255.255.255 null0 That goes on every single router now. Of course, we would also have BGP setup between all of our internal routers. Perhaps not really moving any “real” routing information, just used to kill things. Now we need the trigger. On a central router (wherever an admin is anyway) we’ll do our maintenance for what routes we want to kill. Ip route 192.0.0.0 255.0.0.0 null0 tag 86 ip route 100.100.100.0 255.255.255.0 null0 tag 86 ip route 200.200.200.0 255.255.255.0 null0 tag 86 Notice the tag on those static routes. This will be used for redistribution to help only get the “bad” routes from a router that may actually have many other static routes. Ok, not in the real lab, but we’re pretending that the skills we learn on our way to CCIE have some real-life intrinsic value, right? So once we have decided on our central router what routes we want to kill everywhere, then we pass them out through BGP. Route-map KillRoutes permit 10 Match tag 86 Router bgp 65000 Redistribute static route-map KillRoutes That all seems very simple, right? Well, yes it does, but it won’t help us. At this point, all of our iBGP routers would see the central router as the next hop for each of the routes. Ok, yes, that creates a blackhole. Because it pulls all of the packets into the middle of our network and then kills them locally with a Null0 next-hop. But we are wasting LOTS of bandwidth in doing this. Always filter as close to the source as possible. Good design rules! In order to do this, we need to change the next hop of the route from our central router’s IP address to that of the distributed Null0 route (1.1.1.1 in my example). Route-map NH-Change permit 10 Match tag 86 Set ip next-hop 1.1.1.1 Route-map NH-Change permit 20 Router bgp 65000 Neighbor x.x.x.x route-map NH-Change out (repeat for each of your neighbors unless you’re using peer groups!) The last permit statement of the route-map was to pass-through any other routes that you may want to run in BGP unchanged. Only make the next-hop change for those routes that are evil. You could also set this next-hop within the original redistribute route-map. I just split it out for pointing out the differences. At this point, all of your other routers have learned some routes via iBGP, with a next-hop of 1.1.1.1 and since they have a local static route to Null0 for that next hop, all routes learned this way will be killed. We have now used blackhole routing in a remotely-triggered manner. Kinda cool, huh? Not difficult either, just a matter of thinking about what we are trying to accomplish. As noted, these techniques have been listed more explicitly on both the Security (2.0) and Service Provider CCIE tracks. I don’t see any reason why they can’t be used in Routing & Switching as well, so it never hurts to think these things through! For some extra information, check out: scenario carefully. Makes notes and diagrams as necessary, but think like the router does. Think things through one step at a time and all of these complicated things suddenly become much easier. Cheers, Scott Scott Morris is IPexpert’s Vice President of Curriculum and Senior Technical Instructor. With over 20 years of technical training and consulting experience and a wealth of technical certifications, Scott Morris has proven to be among the elite in the technical training industry. Scott is one of the few people in the world who currently hold four separate CCIE certifications, but is one-of-a-kind by having added Juniper Network’s expert level certification. He is also actively preparing for the CCIE Voice. Scott has years of experience both writing and teaching CCIE lab preparation materials with an outstanding track record of success. Over the past seven years, Scott has also been involved in many aspects of training directly for Cisco’s internal staff on a variety of advanced technical topics. His knowledge and real-world experiences have been sought after for many projects. Scott has also participated in editing, writing and reviewing training books for Cisco Press, Wylie, Sybil, Que. Publishing and McGraw-Hill. His contributing author work includes Cisco Press’ Managing Cisco Network Security book ( ISBN: 1578701031) – Chapters on the PIX Firewall; and Cisco Press’ CCIE Practical Studies, Vol. 2 (ISBN: 1587050722) – Chapter on Multicast. Scott can be reached

sinkhole routing.

While this may sound a lot

like some Star Trek episode, it’s important for us to understand what each is,

and more so how to implement them. Sinkholes are designed to attract traffic

and keep it (for analysis or whatever reason). Blockhouse, on the other hand,

are designed to attract traffic and never let it be seen again.

In larger networks (and

what we simulate in our CCIE labs) both of these techniques are typically done

via BGP. So let’s start with the sinkhole idea. To create a sinkhole, we want

to attract traffic. The first question we need to ask is Why?

Whenever you advertise a

network out, you inadvertently attract traffic to that IPs. That traffic may

be good, or it may be bad. From a security perspective, I’m sure everyone has

heard the term Honeypot used before. There is a specific purpose to attract

traffic.

So let’s say that you have

a /24 network advertising to the Internet through various connections. Traffic

can come in and wend its way through your network to the destination network

segment. You notice a Dos attack, or some huge amount of traffic towards one of

your web servers. Where do you secure against this? How do you secure against

it? Are you still moving traffic all the way through your network to one final

router before the segment? Are you tying up all your link’s bandwidth while

doing this?

Sinkholes spread

throughout your network are a way to break apart and analyze the traffic,

perhaps cleaning it and moving the good stuff on through. But multiple routers

would need a focal point, or different way to route that traffic. You may

simply change the destination for a single IP out of that /24. Most-specific

routing always wins, so that’s an easy way. Maybe you have multiple analysis

points in your network to segment the traffic and reduce load and bottlenecks in

your topology.

Either way, follow the lab

instructions and you are creating a sinkhole. You may even be advertising extra

networks just to attract traffic for analysis (like a Honeypot idea). Just

watch what’s being asked, but that’s the concept of a sinkhole.

Blackhole routing on the

other hand wants to kill traffic. Simply enough, we could go to all of our

routers and install some Null0 routes. In real life, this is not a scalable

approach. Hence the term remotely-triggered blackhole routing, and we’ll use

BGP. Killing a route via a routing protocol is not a simple concept. No matter

how hard we try when advertising a route, Null0 is not a valid next-hop to pass

along to someone else!

So every router needs to

have a seed route to Null0. Pick something that isn’t used.

Ip route 1.1.1.1

255.255.255.255 null0

That goes on every single

router now. Of course, we would also have BGP setup between all of our internal

routers. Perhaps not really moving any “real” routing information, just used to

kill things. Now we need the trigger. On a central router (wherever an admin

is anyway) we’ll do our maintenance for what routes we want to kill.

Ip route 192.0.0.0

255.0.0.0 null0 tag 86

ip route 100.100.100.0 255.255.255.0 null0 tag 86

ip route 200.200.200.0 255.255.255.0 null0 tag 86

Notice the tag on those

static routes. This will be used for redistribution to help only get the “bad”

routes from a router that may actually have many other static routes. Ok, not

in the real lab, but we’re pretending that the skills we learn on our way to

CCIE have some real-life intrinsic value, right?

So once we have decided on

our central router what routes we want to kill everywhere, then we pass them out

through BGP.

Route-map KillRoutes

permit 10

Match tag 86

Router bgp 65000

Redistribute static route-map KillRoutes

That all seems very

simple, right? Well, yes it does, but it won’t help us. At this point, all of

our iBGP routers would see the central router as the next hop for each of the

routes. Ok, yes, that creates a blackhole. Because it pulls all of the packets

into the middle of our network and then kills them locally with a Null0

next-hop. But we are wasting LOTS of bandwidth in doing this. Always filter as

close to the source as possible. Good design rules!

In order to do this, we

need to change the next hop of the route from our central router’s IP address to

that of the distributed Null0 route (1.1.1.1 in my example).

Route-map NH-Change permit

10

Match tag 86

Set ip next-hop 1.1.1.1

Route-map NH-Change permit 20

Router bgp 65000

Neighbor x.x.x.x route-map NH-Change out

(repeat for each of your neighbors unless you’re using peer groups!)

The last permit statement

of the route-map was to pass-through any other routes that you may want to run

in BGP unchanged. Only make the next-hop change for those routes that are

evil. You could also set this next-hop within the original redistribute

route-map. I just split it out for pointing out the differences.

At this point, all of your

other routers have learned some routes via iBGP, with a next-hop of 1.1.1.1 and

since they have a local static route to Null0 for that next hop, all routes

learned this way will be killed.

We have now used blackhole

routing in a remotely-triggered manner. Kinda cool, huh? Not difficult either,

just a matter of thinking about what we are trying to accomplish.

As noted, these techniques

have been listed more explicitly on both the Security (2.0) and Service Provider

CCIE tracks. I don’t see any reason why they can’t be used in Routing &

Switching as well, so it never hurts to think these things through!

For some extra

information, check out:

scenario carefully. Makes notes and diagrams as necessary, but think like the

router does. Think things through one step at a time and all of these

complicated things suddenly become much easier.

Cheers,

Scott

Scott Morris is

IPexpert’s Vice President of Curriculum and Senior Technical Instructor.

With over 20 years of technical training and consulting experience and

a wealth of technical certifications, Scott Morris has proven to be among the

elite in the technical training industry. Scott is one of the few people in the

world who currently hold four separate CCIE certifications, but is one-of-a-kind

by having added Juniper Network’s expert level certification. He is also

actively preparing for the CCIE Voice. Scott has years of experience both

writing and teaching CCIE lab preparation materials with an outstanding track

record of success.

Over the past seven years, Scott has also been involved in many aspects of

training directly for Cisco’s internal staff on a variety of advanced technical

topics. His knowledge and real-world experiences have been sought after for many

projects.

Scott has also participated in editing, writing and reviewing training books for

Cisco Press, Wylie, Sybil, Que. Publishing and McGraw-Hill. His contributing

author work includes Cisco Press’ Managing Cisco Network Security book ( ISBN:

1578701031) – Chapters on the PIX Firewall; and Cisco Press’ CCIE Practical

Studies, Vol. 2 (ISBN: 1587050722) – Chapter on Multicast. Scott can be reached

Did you find this article useful?  For more useful tips and   hints, points to ponder and keep in mind, techniques, and insights pertaining to Internet Business, do please browse for more information at our websites. <a rel=”nofollow” onclick=”javascript:_gaq.push(['_trackPageview', '/outgoing/article_exit_link']);” href=”http://www.adsence-dollar-factory.com”>http://www.adsence-dollar-factory.com</a> <a rel=”nofollow” onclick=”javascript:_gaq.push(['_trackPageview', '/outgoing/article_exit_link']);” href=”http://www.100earningtips.com”>http://www.100earningtips.com</a>

The donkey is mentioned in the Bible 142 times and in the Quran four times, i.e., the Bible cites the donkey 35 times more than the Quran does.

Furthermore, the total words of the Bible are 788,280 while the total words of the Quran are 77,473. It follows that, the Bible has the likely of more than 10 times than the Quran word-wise to talk about The donkey. In addition, the Bible has the prospective of more than 35 times than the Quran topic-wise to utter about the donkey.

The Donkey in the Bible:

Kill every living. Do not spare any:

• They destroyed with the sword every living thing in it—men and women, young and old, donkeys, etc…

• Go and totally destroy everything. Do not spare them; put to death men and women, children and infants, donkeys, etc…

• Kill men and women, children and infants, and donkeys, etc…

Joshua 6:21

“They devoted the city to the LORD and destroyed with the sword every living thing in it—men and women, young and old, cattle, sheep and donkeys.”

1 Samuel 15:3

“Now go, attack the Amalekites and totally destroy everything that belongs to them. Do not spare them; put to death men and women, children and infants, cattle and sheep, camels and donkeys.’ “

1 Samuel 22:19

“He also put to the sword Nob, the town of the priests, with its men and women, its children and infants, and its cattle, donkeys and sheep.”

1 Samuel 27:9

“Whenever David attacked an area, he did not leave a man or woman alive, but took sheep and cattle, donkeys and camels, and clothes. Then he returned to Achish”.

The Bible says that “Ishmael” will be a wild donkey of a man and sets on the root of Arabs-Jews conflict and intolerance.

Genesis 16:12

“He (Ishmael) will be a wild donkey of a man; his hand will be against everyone and everyone’s hand against him, and he will live in hostility toward all his brothers.”

One may think about why Moses wrote in Genesis that His Uncle “Ishmael” will be a wild donkey of a man? Is not it a race-discrimination?

Either Redeem or Kill the firstborn donkey.

One has to redeem every firstborn donkey with a lamb; but if he does not, he has to break its neck. Either way, there should be blood of the lamb or the donkey!

Exodus 13:13

“Redeem with a lamb every firstborn donkey, but if you do not redeem it, break its neck.”

Exodus 34:20

“Redeem the firstborn donkey with a lamb, but if you do not redeem it, break its neck.”

And there is also a prophecy about the ox and donkey:

Deuteronomy 28:31

“Your ox will be slaughtered before your eyes, but you will eat none of it. Your donkey will be forcibly taken from you and will not be returned. Your sheep will be given to your enemies, and no one will rescue them.”

Do not “covet” your neighbor’s wife or donkey.

Exodus 20:17

“You shall not covet your neighbor’s house. You shall not covet your neighbor’s wife, or his manservant or maidservant, his ox or donkey, or anything that belongs to your neighbor.”

Deuteronomy 5:21

“You shall not covet your neighbor’s wife. You shall not set your desire on your neighbor’s house or land, his manservant or maidservant, his ox or donkey, or anything that belongs to your neighbor.”

The Donkey and the Sabbath:

You and your Donkey have to keep the Sabbath.

Exodus 23:12

“Six days do your work, but on the seventh day do not work, so that your ox and your donkey may rest and the slave born in your household, and the alien as well, may be refreshed.”

Deuteronomy 5:14

“but the seventh day is a Sabbath to the LORD your God. On it you shall not do any work, neither you, nor your son or daughter, nor your manservant or maidservant, nor your ox, your donkey or any of your animals, nor the alien within your gates, so that your manservant and maidservant may rest, as you do.”

How do you deal with the donkey, and the fools? With a halter and a rod

Proverbs 26:3

“A whip for the horse, a halter for the donkey, and a rod for the backs of fools!”

The donkey knows his owner’s manger, but “Israel” does not know

Isaiah 1:3

“The ox knows his master, the donkey his owner’s manger, but Israel does not know, my people do not understand.”

The donkeys will eat fodder and mash, spread out with fork and shovel.

Isaiah 30:24

“The oxen and donkeys that work the soil will eat fodder and mash, spread out with fork and shovel.”

The policy of burial of a donkey

How do you burry your donkey? Drag away and throw outside.

Jeremiah 22:19

“He will have the burial of a donkey— dragged away and thrown outside the gates of Jerusalem.”

Wow!

The Egyptian’s genitals are like those of donkeys and their emission (semen) is like that of horses.

Being an Egyptian, I do not know if I should be proud or insulted because of this anatomical and biological verse!

Ezekiel 23:20

“There she lusted after her lovers, whose genitals were like those of donkeys and whose emission was like that of horses.”

This following verse talks about a man who will eat grass like cattle.

However, the man’s stomach is not like that of cattle.

Man can not utilize and metabolize grass

Daniel 5:21

“He was driven away from people and given the mind of an animal; he lived with the wild donkeys and ate grass like cattle; and his body was drenched with the dew of heaven, until he acknowledged that the Most High God is sovereign over the kingdoms of men and sets over them anyone he wishes.”

Believe it or Not!

1) Samson killed a thousand men with a jawbone of a donkey!

Judges 15:15

“Finding a fresh jawbone of a donkey, he grabbed it and struck down a thousand men.”

Judges 15:16

“Then Samson said, “With a donkey’s jawbone I have made donkeys of them. With a donkey’s jawbone I have killed a thousand men.”

2) A donkey spoke with a man’s voice!

2Peter 2:16

“But he was rebuked for his wrongdoing by a donkey—a beast without speech—who spoke with a man’s voice and restrained the prophet’s madness”.

The Donkey in the Quran:

The story of how Allah made revival of a dead man and donkey.

Surah 2:259

“Or the like of him who, passing by a township which had fallen down upon its roofs and fallen into utter ruin, he exclaimed saying: how shall Allah give this township life after its death? So Allah made him die for a hundred years, and then brought him back to life. He said: how long hast thou tarried? (the man) said: I have tarried a day or part of a day. (He) said: nay, but thou hast tarried for a hundred years. Just look at thy food and drink which – years have not passed over it -and have not rotted! and look at thy donkey: and that we may make of thee a sign unto the people, look further at the bones, how we bring them together and clothe them with flesh.” when this was shown clearly to him, he said: “I know that Allah hath power over all things (is able to do all things).”

This story is not mentioned in the Bible.

This story gave a proof to the Jews who denied the revival after death and the afterlife.

The story talks about of preservation of foods for 100 years!

Those who claim they worship Allah but not follow His Law are like donkeys that carry books and not understand what they carry.

Surah 62:5

“The likeness of those who were charged with the (obligations of the) mosaic law (Torah), but who subsequently failed in those (obligations), is as the likeness of the donkey which carries books (but understands them not). evil is the likeness of the people who falsify the signs of Allah (reject the communications of Allah): and Allah guides not the unjust people who do wrong.”

This verse is general for any man not only for the Jews.

One can say that:

The likeness of Christians who were charged with the Gospel but who subsequently failed in is as the likeness of the donkey which carries books; and, the likeness of Muslims who were charged with the Quran but who subsequently failed in is as the likeness of the donkey which carries books.

The harshest of all voices is the voice of the donkeys.

Surah 31:19

“And pursue the right course in your going about and lower your voice; surely the harshest of all voices is the voice of the donkeys.”

This verse gives two important connotations one is social and the other is scientific.

The social one is to be well-mannered when you pursue your right and to talk to the others in a civil and polite way not with a harsh voice.

The scientific meaning needs some acoustic researches to categorize the voices of the creatures and then we will grant the Quranic fact that the harshest of all voices is that of the donkeys.

Allah Creates what you do not know:

Surah 16:8

“And (HE Has Created) horses and mules and donkeys that you might ride upon them and as an ornament; and HE Creates what you do not know.”

This prospective scientific law is applicable and valid for any time.

The Arabs at the time of revelation of the Quran had no idea about most of the creatures. Nevertheless, we also up till now have no idea about many of Allah’s creatures. If we follow the everyday discovery of a new virus, bacteria, fungus, etc. we then should acknowledge this prospective Quranic scientific law that is applicable for any time.

Back to our main issue; this is my question to you smart readers: Is the Quran quoted from the Bible? And which book preceded the sciences? The book which says: Go and totally destroy everything, either Redeem or Kill the firstborn donkey, the Egyptian’s genitals are like those of donkeys, Samson killed a thousand men with a jawbone of a donkey, a donkey spoke with a man’s voice etc. or the book which put a prospective scientific law by saying: ” Allah Creates what we do not know”.