OpenLLM-France/wikimedia huggingface dataset:
# Wireshark/IPv6 local

Wireshark is a free and open source packet analyzer used for network troubleshooting and analysis. These activities will show you how to use Wireshark to capture and analyze local IPv6 traffic.

## Readings

* Wikipedia: IPv6

## Preparation

To prepare for this activity:
* Start Windows.
* Log in if necessary.
* Install Wireshark.

## Activity 1 - Capture Local IPv6 Traffic

To capture local IPv6 traffic:
* Use ipconfig to display the default gateway address. Note the Default Gateway displayed. Be sure to select an IPv6 address. If you don't have an IPv6 default gateway, just review the following instructions for content understanding.
* Start a Wireshark capture.
* Use ping <default gateway address> to ping the default gateway IPv6 address.
* Stop the Wireshark capture.

## Activity 2 - Analyze Local IPv6 Outbound Traffic

To analyze local IPv6 outbound traffic:
* Observe the traffic captured in the top Wireshark packet list pane. Look for traffic with ICMPv6 listed as the protocol. To view only ICMPv6 traffic, type icmpv6 (lower case) in the Filter box and press Enter.
* Select the first ICMPv6 packet or scroll down if necessary to locate the first packet labeled Echo (ping) request.
* Observe the packet details in the middle Wireshark packet details pane. Notice that it is an Ethernet II / Internet Protocol Version 6 / Internet Control Message Protocol v6 frame.
* Expand Ethernet II to view Ethernet details.
* Observe the Destination field. This should contain the MAC address of your default gateway. You can use netsh interface ipv6 show neighbors to confirm.
* Observe the Source field. This should contain your MAC address. You can use ipconfig /all or getmac to confirm.
* Observe the Type field. Notice that the type is 0x86dd, indicating IPv6.
* Expand Internet Protocol Version 6 to view IPv6 details.
* Observe the Source address. Notice that the source address is your IPv6 address.
* Observe the Destination address. Notice that the destination address is the default gateway IPv6 address.

## Activity 3 - Analyze Local IPv6 Inbound Traffic

To analyze local IPv6 inbound traffic:
* In the top Wireshark packet list pane, select the next ICMPv6 packet, labeled Echo (ping) reply.
* Observe the packet details in the middle Wireshark packet details pane. Notice that it is an Ethernet II / Internet Protocol Version 6 / Internet Control Message Protocol v6 frame.
* Expand Ethernet II to view Ethernet details.
* Observe the Destination field. This should contain your MAC address.
* Observe the Source field. This should contain the MAC address of your default gateway.
* Observe the Type field. Notice that the type is 0x86dd, indicating IP.
* Expand Internet Protocol Version 6 to view IPv6 details.
* Observe the Source address. Notice that the source address is the default gateway IPv6 address.
* Observe the Destination address. Notice that the destination address is your IPv6 address.
* Close Wireshark to complete this activity. Quit without Saving to discard the captured traffic.
# Wireshark/IPv4 remote

Wireshark is a free and open source packet analyzer used for network troubleshooting and analysis. These activities will show you how to use Wireshark to capture and analyze remote IPv4 traffic.

## Readings

* Wikipedia: IPv4

## Preparation

To prepare for this activity:
* Start Windows.
* Log in if necessary.
* Install Wireshark.

## Activity 1 - Capture Remote IPv4 Traffic

To capture remote IPv4 traffic:
* Start a Wireshark capture.
* Use ping 8.8.8.8 to ping an Internet host by IP address.
* Stop the Wireshark capture.

## Activity 2 - Analyze Remote IPv4 Outbound Traffic

To analyze remote IPv4 outbound traffic:
* Observe the traffic captured in the top Wireshark packet list pane. Look for traffic with ICMP listed as the protocol. To view only ICMP traffic, type icmp (lower case) in the Filter box and press Enter.
* Select the first ICMP packet, labeled Echo (ping) request.
* Observe the packet details in the middle Wireshark packet details pane. Notice that it is an Ethernet II / Internet Protocol Version 4 / Internet Control Message Protocol frame.
* Expand Ethernet II to view Ethernet details.
* Observe the Destination field. This should contain the MAC address of your default gateway. You can use arp -a to confirm. Notice that remote Internet layer traffic is processed as local Link layer traffic. The default gateway will route the packet to the Internet.
* Observe the Source field. This should contain your MAC address. You can use ipconfig /all or getmac to confirm.
* Observe the Type field. Notice that the type is 0x0800, indicating IP.
* Expand Internet Protocol Version 4 to view IP details.
* Observe the Source address. Notice that the source address is your IP address.
* Observe the Destination address. Notice that the destination address is the Internet host IP address.

## Activity 3 - Analyze Remote IPv4 Inbound Traffic

To analyze remote IPv4 inbound traffic:
* In the top Wireshark packet list pane, select the second ICMP packet, labeled Echo (ping) reply.
* Observe the packet details in the middle Wireshark packet details pane. Notice that it is an Ethernet II / Internet Protocol Version 4 / Internet Control Message Protocol frame.
* Expand Ethernet II to view Ethernet details.
* Observe the Destination field. This should contain your MAC address.
* Observe the Source field. This should contain the MAC address of your default gateway. Notice that the remote Internet layer traffic is returned as local Link layer traffic. The routers between the Internet host and your network routed the packet back to your router so that it could forward the packet back to your computer.
* Observe the Type field. Notice that the type is 0x0800, indicating IP.
* Expand Internet Protocol Version 4 to view IP details.
* Observe the Source address. Notice that the source address is the Internet host IP address.
* Observe the Destination address. Notice that the destination address is your IP address.
* Close Wireshark to complete this activity. Quit without Saving to discard the captured traffic.
# Wireshark/IPv4 multicast

Wireshark is a free and open source packet analyzer used for network troubleshooting and analysis. These activities will show you how to use Wireshark to capture and analyze IPv4 multicast traffic.

## Readings

* Wikipedia: Multicast
* Wikipedia: Multicast Address
* Wikipedia: Simple Service Discovery Protocol (SSDP)
* Wikipedia: Web Services Dynamic Discovery (WS-Discovery)

## Preparation

To prepare for this activity:
* Start Windows.
* Log in if necessary.
* Install Wireshark.

## Activity 1 - Capture IPv4 Multicast Traffic

To capture IPv4 multicast traffic:
* Start a Wireshark capture.
* In Windows, select Start and then type Network and Sharing Center in the Run box. Press Enter.
* Select Change advanced sharing settings.
* Note the current status of Network discovery. If it is already on, select Turn off network discovery and Save changes.
* Select Turn on network discovery and Save changes.
* Wait a few seconds for network discovery to generate multicast traffic.
* If Network discovery was initially off, select Turn off network discovery and Save changes to return the status to the original setting. If network discovery was initially on, leave it on.
* Stop the Wireshark capture.

## Activity 2 - Analyze IPv4 Multicast Traffic

To analyze IPv4 multicast traffic:
* Observe the traffic captured in the top Wireshark packet list pane. To view only IPv4 multicast traffic, type ip.addr >= 224.0.0.0 (lower case) in the Filter box and press Enter.
* The traffic you are most likely to see is Simple Service Discovery Protocol (SSDP) traffic. You may also see Web Services Dynamic Discovery (WS-Discovery) traffic or other multicast traffic. Whatever you find, select the first frame.
* Observe the packet details in the middle Wireshark packet details pane. Notice that it is an Ethernet II / Internet Protocol Version 4 frame.
* Expand Ethernet II to view the Ethernet details.
* Observe the Destination address. Notice that it starts with 01:00:5e, the Ethernet multicast address for IPv4.
* Expand Internet Protocol Version 4 to view IPv4 details.
* Observe the Destination address. Notice that it is in the 224.0.0.0 - 239.255.255.255 IPv4 multicast range. If it is SSDP or WS-Discovery traffic, it will be addressed to 239.255.255.250.
* Select additional frames and observe the Ethernet and IPv4 details for multicast traffic.
* Close Wireshark to complete this activity. Quit without Saving to discard the captured traffic.
# Wireshark/IPv6 multicast

Wireshark is a free and open source packet analyzer used for network troubleshooting and analysis. These activities will show you how to use Wireshark to capture and analyze IPv6 multicast traffic.

## Readings

* Wikipedia: Multicast
* Wikipedia: Multicast Address
* Wikipedia: Simple Service Discovery Protocol (SSDP)
* Wikipedia: Web Services Dynamic Discovery (WS-Discovery)

## Preparation

To prepare for this activity:
* Start Windows.
* Log in if necessary.
* Install Wireshark.

## Activity 1 - Capture IPv6 Multicast Traffic

To capture IPv6 multicast traffic:
* Start a Wireshark capture.
* In Windows, select Start and then type Network and Sharing Center in the Run box. Press Enter.
* Select Change advanced sharing settings.
* Note the current status of Network discovery. If it is already on, select Turn off network discovery and Save changes.
* Select Turn on network discovery and Save changes.
* Wait a few seconds for network discovery to generate multicast traffic.
* If Network discovery was initially off, select Turn off network discovery and Save changes to return the status to the original setting. If network discovery was initially on, leave it on.
* Stop the Wireshark capture.

## Activity 2 - Analyze IPv6 Multicast Traffic

To analyze IPv6 multicast traffic:
* Observe the traffic captured in the top Wireshark packet list pane. To view only IPv6 multicast traffic, type ipv6.addr >= ff00:: (lower case) in the Filter box and press Enter.
* The traffic you are most likely to see is ICMPv6 and Simple Service Discovery Protocol (SSDP) traffic. You may also see Web Services Dynamic Discovery (WS-Discovery) traffic or other multicast traffic. Whatever you find, select the first frame.
* Observe the packet details in the middle Wireshark packet details pane. Notice that it is an Ethernet II / Internet Protocol Version 6 frame.
* Expand Ethernet II to view the Ethernet details.
* Observe the Destination address. Notice that it starts with 33:33, the Ethernet multicast address for IPv6.
* Expand Internet Protocol Version 6 to view IPv6 details.
* Observe the Destination address. Notice that it begins with ff (ff00::/8), the IPv6 multicast range. If it is SSDP or WS-Discovery traffic, it will be addressed to ff02::c.
* Select additional frames and observe the Ethernet and IPv6 details for multicast traffic.
* Close Wireshark to complete this activity. Quit without Saving to discard the captured traffic.
# Web Science/Part1: Foundations of the web/Web content/Motivating separation of content and layout/script

We have now learned about HTML document structures and also about HTML options for formatting. But, what do we now need style sheets for and why do we distinguish between document structure and document layout? Isn't this much more practical, right to the point and easier to handle both together? Yes, to some very limited extent it is, but there are some issues that arise quickly:
* Consistency of Layout: It is very difficult to remember and maintain consistency of layout (e.g. always use italics for emphasis instead of bold face) over a longer time of working. When you collaborate on a text, it is practically speaking even infeasible. It is much simpler to provide structure (emphasize) and factor out the decision how to convey the corresponding notion through layout (e.g. italics)
* Expertise: The content expert is typically not an expert for layout and vice versa. Even if one person does both, the person may learn over time about content vs layout at different speeds leading to the next issue of
* Change of Layout: Layout and content tend to develop in different cycles. You may decide for a new text and maintain existing layout. Or you may change your layout, but maintain existing content. Hence, it is good practice to separate the two.
* Adaptability: Some users have a big screen, others have only a tiny device. What a heading is, is not altered by a different device, but how to display it may change. Knowing about a certain font size, however, does not identify a heading.
* Personalizability: Some users have perfect eye sight, others may be color blind or their eye sight may be even more challenged. Determining colors to be red and green may prevent color-blind people from understanding the content. But, they might decide to go for certain color options in their browser.
* Repurposing: Even a single user may have varying requirements, for instance depending on whether he wants to print content or view it on screen.
Rule of thumb: People who are serious about publishing use style sheets.
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/2

During Galileo life, cannons were being invented and tested as well as used. To remember the answer just think about how cannons and Galileo came around the same era. Which is the reason he named his telescope the Optical Cannon. BAhrns15 (discuss • contribs) 18:48, 22 January 2016 (UTC)
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/9

Which two? It is useless to know that two of them are correct if you don't know which two. -Nathankr42
The answer should include which two of the answers are correct that way we can learn and know which one it is. -Xlynn89x
Instead of saying these two, it should have options to the answers that are correct. Nal2020 (discuss • contribs) 03:30, 27 January 2016 (UTC)Nal2020
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/10

Template:EduV/tip

## Contributions by mikeu

There's a typo in No. 10 "When the German astronomy Marius" --mikeu 20:58, 2 January 2016 (UTC)
    Way to go mikeu! But everybody, there is still much to do: Can you write a short essay that makes this an interesting fact? Can you find a reference for this fact? (How do we know its actually true). Can you write a similar question with different wording so that the testbank becomes so large that very few students could read it in a semester?--Guy vandegrift (discuss • contribs) 21:10, 2 January 2016 (UTC)
       Here's the reference. It is behind a paywall, but all the facts cited at wp are freely available in the abstract. --mikeu 23:23, 2 January 2016 (UTC)
       Pasachoff, Jay M. (May 2015). "Simon Marius’s Mundus Iovialis: 400th Anniversary in Galileo’s Shadow". Journal for the History of Astronomy 46 (2): 218-234. doi:10.1177/0021828615585493. http://jha.sagepub.com/content/46/2/218. Retrieved 2016-01-02.
          Here's more detail. --mikeu 23:45, 2 January 2016 (UTC)
          Van Helden, Albert. "Simon Marius". The Galileo Project. Rice University. Retrieved 2016-01-02.
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/3

This question just brings up a curiosity on why did Galileo call sunrises and sunsets terminators. I feel as though that would be a more important question than what did he call terminators. -Nathankr42
Also, one other way to remember this question is referring it to Arnold Schwarzenegger 's movie, The Terminatior. Arenee994 (discuss • contribs) 17:14, 13 April 2016 (UTC) Arenee994
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/7

You can remember this question by thinking of a note or message about the stars.Arenee994 (discuss • contribs) 17:17, 13 April 2016 (UTC) Arenee994
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/4

The same question is being asked for both question 4 and question 5. The questions are a bit confusing because they asking the same thing but the answers are different. The questions should either be combined or worded differently to discard any confusion. Ah2559 (discuss • contribs) 02:57, 26 January 2016 (UTC)
# Astronomy college course/Wikipedia Sidereus Nuncius/Quiz01/5

This question should be reworded so that the answer has the actual two answers of c and d.
It should be like 1. correlate dark and light regions with terrain 2. measure the height of mountains 3. both 1 and 2 4. to classify stars 5. to terminate his enemies
The answer is 3.
This question is very confusing and doesn't seem to make sense. I feel there is a better way to word this.
What two are the answers? We don't know.
# BCP/Helleborus foetidus/Logs

This page contains recent bloom logs for the plant Helleborus foetidus (Stinking Hellebore). If you saw this plant blooming today (or sometime within the last 3 days), you can help improve the bloom clock by logging it. Just click on "edit" next to the Recent Logs heading, add *~~~~ (an asterisk followed by four tildes) on a new line just below the last signature, and then click "save page". This will add your signature and the date to log the plant.
Please make sure you've signed up on the contributors' page so that we can know the location of the plant you saw blooming and use your contribution to create a flora for your region! When you're done, you can go back to one of the main pages and find logs of other flowers you might have seen today.

##### Recent Logs

* SB Johnny-LM 20:52, 18 February 2008 (UTC)
* --SB_Johnny | 14:54, 3 March 2008 (UTC)
* SB Johnny-LM 08:39, 22 March 2008 (UTC)
* HortMan 11:00, 25 April 2008 (UTC)

##### Archived Logs

(If there are more than 5 signatures under the recent logs heading, move the oldest logs to under this heading (generally leave the 3 most recent).
* --SB_Johnny | 14:17, 15 January 2007 (UTC)
* --SB_Johnny | 18:06, 27 March 2007 (UTC)
* --SB_Johnny | 10:31, 12 April 2007 (UTC)
* --SB_Johnny | 10:28, 9 February 2008 (UTC)
# BCP/Helleborus x hybridus

Helleborus x hybridus
| Red flowers (flowers range from whie through purple) Wikipedia • Commons • Wikibooks (horticulture) • Wikibooks (subject) • Wikispecies • Fruit and seed clock | Profile for Helleborus x hybridus (Hybrid Hellebore) Identifying Characteristics Habit:Low herbaceous plantFoliage:Primarily basal, palmately lobed, evergreenFruit:Dry capsulesLife Cycle: Perennial Recent Logs Anna reg 18:41, 24 March 2011 (UTC) SB Johnny-LM 10:59, 4 April 2008 (UTC) --SB_Johnny | 19:13, 13 April 2008 (UTC) SB Johnny-LM 00:24, 17 April 2008 (UTC) (view all logs) |
Global data: Temperate zone season(s): Mid Winter, Early Spring, Mid Spring
Regional data: Southeastern Pennsylvania: (cultivated) January, March, April
Additional images:
# BCP/Hemerocallis 'Stella d'Oro'

Hemerocallis 'Stella d'Oro'
| Flower Wikipedia • Commons • Wikibooks (horticulture) • Wikibooks (subject) • Wikispecies • Fruit and seed clock | Profile for Hemerocallis 'Stella d'Oro' ("Stella d'Oro" Daylily) Identifying Characteristics Foliage:Strap-likeSimilar Plants:Easily confused with other daylily varieties Recent Logs SB Johnny-LM 09:09, 6 June 2007 (UTC) SBJ 16:16, 7 June 2007 (UTC) SB Johnny-LM 19:59, 8 June 2007 (UTC) --SB_Johnny | 10:46, 4 July 2007 (UTC) --SB_Johnny | 15:42, 23 July 2007 (UTC) (second set of blooms now starting) (view all logs) |
Global data:
Regional data: Southeastern Pennsylvania: (cultivated) June, July
Additional images:
# BCP/Helleborus foetidus

Helleborus foetidus
| Closeup of flower, note that the anthers are present while in bloom Wikipedia • Commons • Wikibooks (horticulture) • Wikibooks (subject) • Wikispecies • Fruit and seed clock | Profile for Helleborus foetidus (Stinking Hellebore) Identifying Characteristics Foliage:evergreen, palmately dividedLife Cycle: perennial Recent Logs SB Johnny-LM 20:52, 18 February 2008 (UTC) --SB_Johnny | 14:54, 3 March 2008 (UTC) SB Johnny-LM 08:39, 22 March 2008 (UTC) HortMan 11:00, 25 April 2008 (UTC) (view all logs) |
Global data: Temperate zone season(s): Mid Winter, Late Winter, Early Spring, Mid Spring
Regional data: Southeastern Pennsylvania: (cultivated) January, February, March, April
Additional images:
# BCP/Helleborus niger

Helleborus niger
| Flowers in winter Wikipedia • Commons • Wikibooks (horticulture) • Wikibooks (subject) • Wikispecies • Fruit and seed clock | Profile for Helleborus niger (Christmas Rose) Identifying Characteristics Habit:low herb or subshrubLife Cycle: perennial Recent Logs SB Johnny-LM 11:40, 15 January 2007 (UTC) SB Johnny-LM 10:36, 11 February 2008 (UTC) SB Johnny-LM 20:51, 18 February 2008 (UTC) SB Johnny-LM 11:38, 7 March 2008 (UTC) SB Johnny-LM 08:40, 22 March 2008 (UTC) (most flowers fading to pink) (view all logs) |
Global data: Temperate zone season(s): Mid Winter, Late Winter, Early Spring
Regional data: Southeastern Pennsylvania: (cultivated) January, February, March
Additional images:
# BCP/Helleborus x hybridus/Logs

This page contains recent bloom logs for the plant Helleborus x hybridus (Hybrid Hellebore). If you saw this plant blooming today (or sometime within the last 3 days), you can help improve the bloom clock by logging it. Just click on "edit" next to the Recent Logs heading, add *~~~~ (an asterisk followed by four tildes) on a new line just below the last signature, and then click "save page". This will add your signature and the date to log the plant.
Please make sure you've signed up on the contributors' page so that we can know the location of the plant you saw blooming and use your contribution to create a flora for your region! When you're done, you can go back to one of the main pages and find logs of other flowers you might have seen today.

##### Recent Logs

* Anna reg 18:41, 24 March 2011 (UTC)
* SB Johnny-LM 10:59, 4 April 2008 (UTC)
* --SB_Johnny | 19:13, 13 April 2008 (UTC)
* SB Johnny-LM 00:24, 17 April 2008 (UTC)

##### Archived Logs

(If there are more than 5 signatures under the recent logs heading, move the oldest logs to under this heading (generally leave the 3 most recent).
* --SB_Johnny | 11:40, 15 January 2007 (UTC)
* SB Johnny-LM 11:13, 13 March 2007 (UTC)
* --SB_Johnny | 18:06, 27 March 2007 (UTC)
* SB Johnny-LM 13:22, 31 March 2007 (UTC)
* --SB_Johnny | 10:31, 12 April 2007 (UTC)
* --SB_Johnny | 11:33, 26 April 2007 (UTC)
* SB Johnny-LM 11:37, 7 March 2008 (UTC)
* SB Johnny-LM 08:40, 22 March 2008 (UTC)
# BCP/Hemerocallis

Hemerocallis
| Flower of H. fulva, one of the most commonly encountered daylilies Wikipedia • Commons • Wikibooks (horticulture) • Wikibooks (subject) • Wikispecies • Fruit and seed clock | Profile for Hemerocallis (Daylily) Identifying Characteristics Habit:clumping herbaceous plantFlowers:3 petals and 3 sepals nearly equal. Each flower lasts only one day.Foliage:Basal, straplikeLife Cycle: Perennial Recent Logs Jomegat 04:43, 6 June 2009 (UTC) Jomegat 00:48, 22 July 2009 (UTC) (view all logs) |
Global data: Temperate zone season(s): Early Summer, Mid Summer, Late Summer, Early Fall
Regional data: Southeastern Pennsylvania: (cultivated) June, July, August, September New Hampshire: June, July, August Central Pennsylvania: August , October
Additional images: