What is going on everybody? It's Stas here. Welcome back some other videos. So in this video, we're going to be doing an overall market update looking at the Dow Jones, the S&P 500 and the NASDAQ. We're going to be talking about two trades that I made today on the 26th of March in 2019, as well as taking a look at some other stocks and ETFs that I'm personally looking to trade for the rest of this week and heading on to the beginning of April in 2019. We're also going to quickly take a look at what happened with Apple and Qualcomm. I have an article here on the Safari tab. We're going to quickly talk about that in this video as well. But before we do talk about all of these different things for everybody out there that enjoys these videos, you find value in these videos. And let's say you find value in this video, feel free to go down below and hit that like button, guys. It really does support the channel and support me in general. And if you're new to the channel and you want to join our two free communities linked down below the Discord and the Facebook, feel free to do so. I guarantee you guys you'll find a ton, a ton of valuable information in those communities. And without further ado, guys, let's talk about what the markets are looking like right now with about seven minutes left to the close of the market here on the 26th of March. So let's just hop over here to the S&P 500, the 500 largest publicly traded US companies. And it's looking like unless something crazy happens here in the next seven minutes, we're going to end up closing the day green, roughly up around 0.5%, up around give or take $15 at the close here. And we're going to come back towards the end of the video and see exactly where we did close. But as of now, that is what the SPX is looking like. The Dow Jones is up nearly 100 points right now, up about 0.4%. And the NASDAQ composite guys, not too great of a day, it's up about $6 right now, up about 0.08%. So let's just hop back over here to the S&P 500. And for those of you guys that have been following the videos for a while now, you've been following them, especially over these past couple of days, we've been talking about the critical support the S&P 500 was at yesterday, right? And that was on the 50 simple moving average as well as the 2790 to 2800 level of support here that we can see on this 180 day four hour chart. And we were talking about this in yesterday's video as well as Friday and Sunday's video. And we were talking about how, if we were to break below these levels, the S&P can end up selling off maybe down to 2736, which is the next support level, right? But let's say we popped above these levels, the continuation of the uptrend would probably happen, right? And that is what we ended up seeing today guys, and we can see that towards the end of the market here, is that we're continuing this push off of the bounce of the 50 simple moving average and that support that we were just talking about, right? And let's just take a look of the movement of the SPX here a little bit closer. We can see actually that we gapped up heavily in the morning, we were up about 1% in the SPX, and we were kind of hovering in this range between 2820 and 2830 really for the first two to two and a half hours of the market open. We can see three separate tops here, you know, roughly at that level of the 2825 to 2830, very strong level of resistance this morning. And then we actually saw a big sell off, not too big of a sell off, but about a 20 to 25 point sell off in the S&P 500, you know, from this level at about 1139 a.m. Eastern Standard all the way down to about 230 p.m. Eastern Standard. And now we can see we found a bottom we're reversing to the upside and we're breaking out of the 180 simple moving average resistance that's been a resistance and the 50 simple moving average resistance, both of these being resistances here over the past couple of hours, you know, in the S&P 500 and we're pushing up here looking to retest that resistance at about 2820. So let's just hop over here to the 20 day, actually let's go to the five day five minute chart very quickly to see something interesting, right? So we talked about this in yesterday's video how we can go either two ways, right? We were on this, you know, we saw this trend line here yesterday and I was telling you guys how if we were to gap out of this this morning, we were going to most likely see a green day, which is what ended up happening. And if we were to continue the downtrend, if we were to get rejected and push down, obviously more red, what was probably going to come in that situation. And we saw the break above here. And now we're actually maintaining the 180 simple moving average as a support here on the five day five minute chart, which is actually super, super important in my eyes for the continuation of this uptrend heading into tomorrow's trading session. So for tomorrow, keep an eye on these levels here of about 2820 and this 180 simple moving average support on the five day five minute. And you may be asking yourself, what is this 2820 level here represent? And if we go back to the 180, which is why I always preach to you guys, it's super important to look at multiple different timeframes, we can actually see that 2820 level if we just zoom in a bit was actually a resistance from back in the middle of October, back in the beginning of November, and really back towards, you know, the middle towards the end of February in 2019. And that is the level roughly where we are right now. So if we go back to that five minute five day five minute chart, we're going to need to break out of that level tomorrow and ultimately out of the 2825 level on the SPX for us to be continuing this uptrend pattern. So something like this needs to happen. Let's say we end up gapping up again tomorrow, we open up here and we slowly start to do something like this, that's going to be a good continuation of the uptrend here in the SPX. But let's say on the flip side, the second scenario, if we're going to be selling off tomorrow, let's say we end up getting rejected here tomorrow, we do something like this, right, and then we go to test that double bottom level that we were talking about yesterday, roughly at about 2785 to 2790, you know, this could issue more selling in the overall stock market, right? So that is what I'm looking at in the SPX and the different scenarios that can potentially play out tomorrow. As of right now, everything is pointing green and especially if we break out of this level of resistance tomorrow, I do see a lot of green potential for tomorrow as well. And just take a look at how quick this is running up right now, guys. We're seeing a nice little pop up here and it's looking like we're about to test that 2820 level right here at the close. So this is a pretty good sign, you know, in terms of the S&P 500. If we're hopping over here to the Dow Jones industrial average, same exact thing, right? We're seeing that nice pop. We saw the big sell-off, you know, from about 1130 Eastern Standard down to about 245 Eastern Standard, you know, the 50 and the 180 S&P is reacting as resistances. We got kind of a double bottom here, more like a higher low from the previous, a little, you know, uptrend reversal towards the end of the market. And at the close, we can see we just popped up very nicely here. So let's just look at the longer-term charts here in terms of the Dow Jones industrial average, just like we were talking about yesterday, guys.  We were talking about this level of support on the Dow Jones, roughly at about $25,500. This was a previous resistance from the beginning of February. We obviously broke out of that resistance, making it a new support. We retested the support back in the, towards the beginning of March here, about two, three weeks ago. And now we popped up, and now we're retesting it. We retested it, rather, today. And the fact that we bounced off of it is a very good sign that we're continuing to push up. We're trading now in this little horizontal pattern from about $25,500 up to about $25,800. And the next resistance in terms of the Dow we're going to be testing is going to be at around $25,800, roughly about 150 points above from where we are right now. And let's say tomorrow we have a strong green day, right? Very possible, right? Anything is possible in the stock market, especially in the current market we're currently in, right? Let's say we break out of this level. The next level we're going to be looking to test is going to be at around $26,000 flat, which was actually where we topped off back about 10 days ago here in the Dow Jones. And if we break that level, we're going to be testing $26,200. And then from there, guys, we're going to break out of that, which is actually, we'll potentially break out of that if we do test the $26,000 level. And if we break out of the $26,200 level, that's going to be what we need to see in order for the Dow Jones industrial average to eventually test this all-time high, which is close to $27,000. So let's just take a look quickly here at this five-day, five-minute chart. Very similar to the SPX, right? We talked about how on Friday and on Monday, we saw very, very strong resistance here in terms of the Dow Jones, right? We saw the resistance here at the top at $25,700, the next top at about $25,500. And then the close, we close at about $25,500 flat. This previous one was more like $25,600 actually. And then I was telling you guys how we were going to either pop out or get rejected and then continue to push down. We obviously popped out. And now we're holding the 180 simple moving average as a support just like the SPX. So this is a good sign that the Dow wants to continue this push into tomorrow and then retest the $25,800 level that I was talking about just a minute ago. So that is what I'm looking at in terms of the Dow Jones. Everything is looking pretty solid for another green day tomorrow, if those technical indicators stay in place into the open tomorrow. And of course, we're looking at the futures in the morning, what the large caps are doing, stuff like that, right? So that's what the Dow Jones is looking like right now. The NASDAQ here had that nice little pump towards the close. We can see, you know, when I started the video, we were up about 0.05%. I ended up closing roughly up about 0.3%, very, very solid closing move there in terms of the NASDAQ. So what were we talking about in yesterday's video, guys? We were talking about how the NASDAQ was trading between roughly $7,360 and the support of $7,360-ish and the resistance at about $7,415. And since it didn't have too crazy of a green day or too crazy of a red day today, we're still in between those two levels. So what am I going to be waiting for tomorrow, guys, for the continuation of the uptrend? I want to ultimately see a hold on this 50 SMA. If we did break that, you know, that could issue more selling. And eventually, you know, I want to see a break out of the $7,400 level and a retest at the $7,500 level where we ended up getting back roughly a week ago from now. So it's very simple, guys. You know, this, it's looking like it wants to continue to push up since A, it is holding the 50 SMA, and B, it is holding this level of support here really over the past couple of days. So if we're hopping back to the 5-day-5-minute, we can point out something interesting here, you know, in terms of the NASDAQ over the past two days of trading. What do you notice here? We're noticing a nice little uptrend pattern, right, over this, you know, one day or roughly the 5-day-5-minute. We're seeing a low at about $7,290, a higher low here, higher low here, and then this low here really signifies the continuation of the uptrend because it's a higher low from the previous. And we saw that big push towards the end of the market here today where we ended up breaking out of the 180 SMA resistance and the 50 SMA resistance as well. So this is all looking pretty, pretty dandy here in terms of the NASDAQ. And we can see here, actually, guys, we ended up opening up pretty, pretty heavy today actually, $74.50 sold off all the way to $73.50. So that's nearly 100% or not 100%. If it was 100%, that would be bad. 100 point drop in the NASDAQ. And then we recovered back up above that support. So now just keep an eye. Are we going to fill back up here? That is what I'm going to be watching for tomorrow in terms of the NASDAQ. So let's quickly talk about what I ended up trading today, guys. It wasn't too crazy of a trading day for me. I'm not going to lie. I barely took any trades in the middle of the day. I took a trade here about 15 minutes ago right before I ended up recording this video and also in the morning in Tesla stock. And I actually talked about Tesla stock this morning. And for those of you guys that watched my morning video, I upload morning videos every, not every day, but I try to do it every single day. So stay tuned for those. But in this morning's video, I was talking about Tesla stock. So we got news this morning that are about, not this morning, I think it was actually yesterday, about 15, 14 hours before this morning's video. So at this point, it's probably closer to 24 hours ago that the SEC and the lawsuit, the shareholder lawsuit against Tesla has been dismissed, right? So I talked about in this morning's video how this could be a catalyst for Tesla this morning. And what happened this morning, guys? Tesla ran from 264 all the way up to $270 off of that catalyst, in my opinion, that the lawsuit got dismissed. So I pretty much got in on this big green pump, this big green candlestick here. And I held it for a couple of, not a couple of hours, I was about to say a couple of hours, more like 30 minutes here in Tesla stock. It wasn't the biggest trade ever, but it was profit, guys. And again, profit is profit. So I ended up getting into Tesla roughly at about $265.39. And I held it for about 30 minutes, got my roughly about 1.1, 1.2% profit on the trade, nothing too crazy. And when I'm taking day trades, guys, I'm taking about 1 to 2% on my trades, right? I'm not trying to get the home run trade all the time, the 5%, 10%. I'm not trading penny stocks. I never really trade penny stocks and be completely honest with you guys. I'm not trading and chasing these 50%, 100% gains. I'm more into trading larger cap stocks on catalysts, positive catalysts, like we saw in Tesla stock today. And I'm all about taking that 1, 2, 3%. Sometimes I do get 5%, 6%. If I'm trading a leveraged ETF, you know, like UGAS, DGAS, DRIP, GUSH, if I'm trading TVIX, sometimes I do get more than 1%, 2%. But today, it wasn't the craziest day of profit. Got about 1% to 1.2% on Tesla. And that's pretty much it, guys. The catalyst on the dismissal of the lawsuit, pretty good in my opinion, because SEC and Elon Musk, those are two things that don't like going together, right? Because Elon Musk hates the SEC. The SEC hates Elon Musk. And now that this is dismissed, that's pretty positive in my eyes for Tesla stock. So the other position that I just took here a couple of minutes ago, now probably about 30 minutes ago at this point, was in Nvidia, guys, ticker symbol NVDA. And this is one that actually pumped up pretty heavily from yesterday. And I was kind of kicking myself, because if you guys recall in yesterday's video, I was saying how I was almost tempted to take an overnight swing in Nvidia. And if I did do that, I would have gained about $8 per share, literally, because I would have sold at the morning, because at this point, we were extremely overbought. I would have just took my profits, knowing myself and knowing how I trade. I would have been up about 4.4%. I obviously would have took my profits there. But the fact that we sold off all the way from 181 back down to 174, and then we had this little reversal pattern out of the 50 Simple Moving Average resistance, and out of the 180 Simple Moving Average resistance towards the close of the market.  You know, I took a position in Nvidia stock. I can't remember what exact price it was. I think it was roughly about 10 minutes before the market closed. It was roughly about $176.25, $176.50, something like that. Ended up buying about six shares of this company. And I'll put a screenshot right here for you guys so you can see because I forget off the top of my head what exactly I did buy in terms of shares, or the price rather. And I do plan on holding this one up to the previous resistance at about $185. And I'm in with a small amount, guys. You see on the screen, I've got like five or six shares, whatever. It's like $1,200. This is about 20% of my goal position, 15 to 20%. And you may be asking yourself, you know, why are you going in very light on Nvidia? Because when I take swing trades, guys, for the most part, I don't jump in with my goal position right away, right? So this Nvidia trade, I would like to get this up to, let's say, a $7,500, maybe a $10,000 position, right? So if I'm in right now with roughly $1,500, whatever it is, you know, and it goes down, you know, I'm not going to lose as much money if I do cut my losses as I would have if I jumped in 10K, $10,000 right away, right? So I'm hopping in right now with about 10%, 15% of my position. And I plan on adding more as the uptrend continues, right? And another thing I'm seeing here that I really do like is the fact that we bounced on this 50 SMA support heading into today. So let's say we end up pushing higher tomorrow into 180, I might add some more money into Nvidia there, maybe buy another 10 shares, maybe 15 shares go a little bit heavier up here. So let's see tomorrow what ends up happening. But the goal here, if we do end up breaking the 50 SMA, I'm probably going to end up cutting losses there in terms of Nvidia ticker symbol, NVDA. So that's the quick little trading update today, guys. You know, nothing crazy, honestly, it was a pretty slow day for me, but the markets, you know, they've been kind of funky over these past couple of days, they're swinging up, they're swinging down, they're not really picking a direction. And, you know, it's just difficult sometimes to pinpoint swing trades when this does happen. But I do feel comfortable, you know, with this Nvidia trade, you know, we're hanging above the 175-ish support, you know, the 173 support, which was a previous resistance. I do plan on selling at about 185, and if we break that, you know, $200 will be the next target there. So what ended up happening today with Apple and Qualcomm, guys? This was actually pretty, pretty big news that actually sent Apple stock tumbling here from the high of the day at about 192 down to about wherever we ended up closing, I think it was down about like one, we went down all the way to 184, guys. So take a look at that big dump in Apple's shares, down nearly 4% from the high of the day, and let's just hop into my safari very quickly, and we'll go over what's going on here. So Apple infringes Qualcomm patent, Judge recommends ban on some iPhones. So Apple, for those of you guys that don't know, Apple and Qualcomm, they've been at war here for some time, right? So Apple Inc. infringes a Qualcomm Inc. patent, and some imported iPhones should be blocked from the U.S. as a result. A U.S. trade judge said in one of two cases before the U.S. International Trade Commission. So Qualcomm actually jumped 1.6% as of 1.58 p.m. Eastern Standard Time here. And the whole thing about this, guys, is that they're planning on banning some imports from China for certain iPhones, right? So in this case, Qualcomm contends Apple iPhones with Intel Corp chips and infringed two patents related to ways to improve the speed and quality of data downloads, and one for a power saving feature. It's seeking an order that would ban imports of those iPhones, the judge finding of infringement related to the power saving feature. So this is pretty much why Apple stock ended up tumbling very quickly. And this kind of segments into what I'm looking to trade for tomorrow. And honestly, for the rest of this week heading into April in 2019. So we can see Qualcomm here popped, right? Like, you know, Apple dropped Qualcomm popped. We can see, we saw it in the article from 56 up to about 5830. Pretty sizable move there in terms of Qualcomm. And in general, guys, Qualcomm's patent right now is looking pretty beautiful, right? We're seeing the bottom at about $49, which was a support from about a couple of years ago, I think we did cover this stock in one of my videos recently. Yeah, it was from a couple of years ago, we can see a solid support at about $49 and 10 cents. Hopping back over here to the 184 hour, we can see the bullish reversal here, the bullish crossover of the 50 SMA above the 180 SMA here on the 184 hour chart. And this is something that I like to see whenever I'm taking a swing position, excuse me, in any particular stock, right? I wouldn't want to take a swing position when Qualcomm is at this point, right? Because at this point, we're still down trending. We're seeing a bearish cross, which is the 50 SMA below the 180 SMA. So why would anyone want to trade that on a swing basis, right? If anything, you'd want to play put options there or short the stock, right? But we saw the reversal to the upside, the bullish crossover, the 50 SMA above the 180 SMA, the candlesticks are holding the 50 SMAs of support. We dipped here, ended up bouncing at $56.25 with this good news for Qualcomm, the stock popped. So let's say tomorrow, we end up breaking this resistance at $58, I think Qualcomm can end up doing pretty well from there. And notice how we're at a point of resistance in Qualcomm stock that stems back to really the beginning of December of 2018. So take a look at this, guys. If we end up breaking this resistance, end up holding it as a new support, we could potentially run up to the early 60s here, let's say $61 in terms of Qualcomm stock, which does offer it a nice 4%, 5% margin of profit. So just keep an eye on Qualcomm. This is something that I'm watching very, very closely heading on to the rest of this week. So QCOM, I almost said CQM. QCOM, that's one that I'm watching here. Of course, NVIDIA is another one I'm watching. I pretty much did my analysis on NVIDIA, very similar to Qualcomm, right? We're seeing the bullish crossover here. We're seeing higher lows, higher highs, all that jazz for the continuation of the uptrend. We broke out of the 173 resistance, held it as a new support, opened up that margin. I'm planning on trading it up to 185. We already talked about that. Don't want to really repeat myself at this point. Another one that actually somebody talked about in the chat today was Spotify, or no, it was not Spotify. What was it? What was it now? Shopify, Spotify, Shopify, they sound the same. Actually, not that I think about it. I actually never thought about that. Shopify, Spotify, they actually sound exactly the same. But Shopify here, this was brought to my attention, and I told him that Shopify is already at all-time highs right here. There is some potential due to it holding the 50 SMA slowly starting to curl back up. There is maybe some margin for a little trade here. If we do end up testing 210 again, maybe from 204 where we ended up closing to 210, you can grab about 23% margin there. But if anything, Shopify could be a potential short play here. Let's say we end up double topping at this point. We end up breaking the 50 simple moving average, and we start to do something like this. This stock has nearly doubled in price over the past couple of months. This is an insane run in Shopify. Everything that goes up, not everything, but stocks that shoot up crazy like this for the most part, they do see a correction. Let's say we corrected down to the 170s. This is going to be a fantastic put option or a short play if we do end up double topping here. But for all we know, we could continue to run up guys. We could continue to run up, push up, maybe make a new all-time high. But in my opinion, Shopify right now is in the state of euphoria. You've heard this before, when the stock markets in a state of euphoria, oh my God, everything's so great. We're green after green after green. That usually is the best time to sell your stocks, right? So if people start selling off, we break the 50 SMA, we start to push down. This could be a short play here and I'm watching it for that particular play. So Shopify, that is what I'm talking about and watching in terms of this stock here. Tesla might as well talk about Tesla again here, guys. With this catalyst, who knows? We might be able to push up even more tomorrow. And what I'm watching for here, guys, is for the break of the 50 Simple Moving Average resistance here. If we were to break that level and we started to test maybe 280 again, this could be a runner back up to maybe 290, maybe 295, which would put us at that 180 Simple Moving Average resistance here because it seems like we are holding the 250 support from back over a couple of months ago. So this is a good sign that we could potentially reverse here. But until we break this 50 SMA and 280, we're still on that downtrend with the 50 SMA being a resistance. So keep an eye tomorrow on Tesla stock. Very, very interesting levels right now in terms of the stock. For all we know, we could potentially pop, but just keep an eye on this level. If we get rejected here, I'm not going to be really looking to trade Tesla stock. So I actually got some requests for NEO. And NEO right now, although it is on a downtrending pattern, very clear downtrend here, no signs of reversal whatsoever, this is a speculative stock that a lot of people are putting some speculative money in right now. Some people are buying some shares here hoping that this Chinese car manufacturing electric car company does well over the next couple of months so they could potentially double their money. This is something that is kind of out of my realm. I don't really trade quote unquote penny stocks because this is not really a penny stock, but I consider anything from one to $5 a penny stock kind of out of my realm here. But I might consider possibly putting maybe $500 into NEO stock for fun. Who knows? I might just do that, although I never do that and I don't advise you to do that. Don't do that. If you're watching, do not do that unless you understand the risk. Because this company, although it doesn't have or showing rather a sign of reversal to the upside, there is potential for this stock to double, there is. There is 100% potential for this to double because of the volatility of the company. Just take a look at this, from $7, although we have the $10, you would have made a killing of a return there if you put in a little bit of money right here. And the fact that it's gotten battered down so hard, I think it's worth watching as a speculative play here. Speculative, very, very speculative. This could definitely go bankrupt. Who knows? But if you're willing to put a little bit of money that you're willing to 100% lose, I say go for it. I'm willing to lose 100% of $500. And let's say I put in $500, I forget about it, and then we look at NEO stock in a couple of weeks. And let's say it's back up to $8, $10, I made double my money, I made a little $500 profit there. So this is something that I'm going to be watching. But again, this is out of my realm. I don't really trade stocks like this, especially penny stocks and especially stocks that are downtrending like this. But for fun, I might put some money in, I will let you guys know. So I hope you guys enjoyed this video. If you did, feel free to drop a like, leave a comment, subscribe, follow me on Instagram, as well as on Twitter, join our Discord group chat, as well as our Facebook group, 100% free, linked down below. I'll catch you all in the next video. Thanks for watching. Peace out.


Ladies, and gentlemen, the New Year is upon us. You are probably watching this on New Year's Eve. Let's just call it as it is. And guess what? Maybe you have not taken the opportunity, the chance to think about what am I going to do to be a better person in the New Year in 2018. It's a great opportunity. I didn't always make New Year's resolutions. I've started that tradition in the last couple of years and believe it or not, it's actually helped me to think, to stop, reflect about the last, remember I love looking to the past in order to prepare for the future and look back at the last 365 days in my life on this earth and think, wait a minute, how could I be a better person in the next 365 days? A more virtuous, there's a word, virtuous person in the next 365 days. Listen, I've got a lot of work to do before I feel like I am approaching the mantle of virtue on this earth as a human being. So I have some thoughts here to share with you to help keep me accountable here on the YouTube and also maybe hopefully inspire you in there, in there to maybe consider, maybe consider what you can do in the next year, 2018 to be a more, and this is the tip of the day for starting your New Year, write your New Year's resolution down, tear it out and tape it on your mirror in your bathroom or on your refrigerator so you don't forget. So in no particular order, broken down into four categories for 2018. The vlog, family, running and personally. All right, for the vlog, I want to be more transparent with you. That's right. I want to share more of my story with you. Fair. I'm just going to leave it at that and let it play its course in the next 365 days. Transparency might be a really important word for the next year, all right? Move the vlog's focus, the lens, the focus through which I communicate to you on this VLOG. Okay? I'll just leave it at that. Number three, under the vlog, meet some of you in person.  If we could meet for a pizza, meet for a coffee, whether you're in Denver or outside of Denver, let's make it happen. Number two, family. It's one thing, lead better, lead L-E-A-D as a father and husband. Capiche? Capiche? I want to lead better. There's a lot of issues within our culture. I believe most of those issues go directly back to the fact that we do not have fathers present in so many children's lives. I know that's a tough topic. I'm going to leave it at that, but that is one of my goals for 2018. Lead better, lead better as a father and husband. Number three, running. I want to win a race. Maybe I'm a little bitter after the race in Highlands Ranch where they didn't mark the course. Yes, I'm a little bitter. I want to win a race in 2018. I want to complete Nolan's 14 or run another long race. Fair? Number three, I want to start a local running group. Okay? Number four, whoa, it's a little crazy. I want to run 400,000 vertical feet. Number four for running. Okay. And lastly, personally for the goals for 2018, my new year's resolutions, I want to be healthier. And so there's different ways to go about being healthier physically, mentally. But one of the ways I'm not, this is crazy, I'm not going to drink any beer in 2018. No beer. So if I'm at a party, if I'm at a bar, I'm going to have, if somebody wants to buy me a beer or if I'm camping up in the mountains, somebody offers me a beer, I'm going to say, where's your wine? I will still drink some wine occasionally, drink a little bourbon, you know, I like my bourbon, but I'm going to give up beer completely in 2018. I want to be healthier and I think that's one way to do it. Capiche?  I want to get to know that person better in the present day. That's goal number two under personally. And then number three, which has always been a struggle for me, I want to trust more in the bigger picture, in divine providence. I want to trust more in 2018. That is my last goal for communicating to you on this YouTube channel. So, all right, that's it. Thank you for listening for three, the last 365 blogs. Holy smokes. Isn't that crazy to think about? But once again, question of the day, what are your New Year's resolutions? How do you want to be better in the New Year? And you know, it's at the stroke of midnight, it's going to happen. So I'm excited to seek beauty, work hard, love others in the New Year. And I hope you are as well. Thanks for coming along this journey and see you next year.


A protocol, a set of rules for two or more entities to communicate with each other, so they follow those rules so that effectively they both speak the same language, they can understand each other. For communication systems we don't use just one protocol, we use a set of protocols and we organize them in a way such that we can think of them as layered, one on top of each other. So we have one protocol which we say is part of the physical layer that has the role of sending signals across links, electrical signals, radio signals, and then another protocol that uses that physical layer protocol to do some extra tasks. And then another protocol, a network layer to do additional tasks and so on such that when we combine all these protocols we can achieve what we want to do when we want to communicate across a network or across the internet. So very broad coverage of protocol architectures last week. Another classification of these five layers is that we say the bottom two layers, data link and physical, their responsibility together is about getting data across one link. I connect my laptop to that PC via a single cable. The physical and data link layer protocols have responsibility of getting the data across that link. They don't care about the next link, for example if there's a link onto another device, we just focus or the scope is one link for those protocols. But of course in large communication systems to communicate from one entity to another we may have multiple links. We go via intermediate devices and we get a network and it's the role of the network layer protocol to get the data across a set of links, across a network. And the main network layer protocol in the TCP IP architecture is called IP or the internet protocol. There are some other supporting protocols as well, but IP is the core of the internet. It's the most important part. The top two layers are about getting data between really applications. So the application on my computer for web browsing, that is Firefox web browser, needs to get data to some web server in the US and data comes back. Then the application layer protocols are specific to applications like one is for web browsing, one is for file transfer, another for email. But some of those protocols have common requirements and therefore they'll use a single transport protocol. They'll all use or many will use the same one. So these two layers are more about getting data between the end user computers, between laptop and server. Not so much about getting data between intermediate devices like wireless access points, routers, switches from the end devices. So that's a rough overview of what we covered last week or at least we got to last week. We gave this example with two end computers, a source host and a destination host. Let's say a PC in the laptop, but connected via two links and one intermediate device, this intermediate computing device here called a router. So one link to the router and then another link from the router to the destination. So it's a very simple network, a network with two links. Maybe the important thing to note here is that not all devices need to implement all layers. As you see here, normally the end hosts, PCs, laptops, the end user computers implement all five layers. Because they are running applications and they need the support of application and transport layer. Intermediate devices, depending upon where they are in the network, may not implement all five layers. In this example, the router implements physical data link layer and network layer. It doesn't care about what application is being used between the hosts. When I send from my laptop wirelessly to this access point, and you can see it has a cable going up to another device and out into the internet. This access point, an intermediate device, doesn't care about whether I'm web browsing, sending an email, instant message, whatever. It doesn't know anything about the application. It's just getting data received on one link and sending it across the next link until it gets to the destination. Through the course we'll see some names and what is a router, what is a switch, what is an access point. There's a few more things that we want to talk about with protocol architectures. A protocol set of rules for entities to follow, to communicate, implemented in hardware and software. I'll show some examples soon for the implementation. A standard is an important thing. A standard is an agreed upon set of rules or an agreed upon protocol, normally agreed by multiple companies or organizations. Some organizations either get together or people get together and they agree. When we implement the communications or wireless communications for laptops, let's all use this one protocol. To ensure everyone uses it and uses it correctly and implements it correctly, they create a standard. If everyone follows that same standard, then my laptop will be able to communicate with a laptop from a different manufacturer. Standards are documents that describe a set of protocols or rules to use and are usually created by some organization, whether it's government organization or a commercial entity. From last week, some of the old devices we can have a look at. Here's an old LAN card that normally you plug into your PC, into a PCI slot I guess, and nowadays on the motherboard, you don't have to buy a separate LAN card. Here's a switch and they both have those sockets so that you connect a LAN cable from this one into this one and they communicate with each other. Don't worry about what the switch does at the moment. This one's made by PCI, made in China. This is made by or the chip is made by Compex, in fact made in Singapore. Different companies made them. They're made by different companies, but they can still talk to each other. The reason why is that they both implement the same standard for communications. In fact, the standard usually has it, they have a name. This one would be generally called Ethernet or IEEE 802.3 is the standard that this one implements and that this one implements. When I go and buy a device, so long as it implements the same standard, it will be able to communicate with any of these two. This use of standards allows or helps create an open market and a competitive market in that a consumer or a business, when they want to buy products, they don't have to buy a product from a particular manufacturer. They just need to buy a product from a manufacturer that implements that standard that everyone else uses. Or you have choice of who do you buy your products from and there becomes competition in the market. So you've seen standards, not just in communications, you see them in many other aspects of ICT and other fields. Another thing standards allow us is to allow to communicate across borders. For example, there's a worldwide standard for telephone numbers. That is, we have a sequence of numbers to represent some telephone. In different countries, there may be a different length of the numbers, but they still follow some structure. So telephone numbers for normal telephones have some follow some standard. And in fact, the telephones that we use, think of your mobile phone, they implement one or several standards. So old telephones, mobile phones use GSM. GSM referred to the name of a standard. And everyone who had a phone that implemented that standard could call, in theory could call someone else who has a phone using that GSM technology and the standard behind it. Nowadays, we have 3G and fourth generation technologies. And if your phone implements the same standard as other phones, and the same standard used in the network, then you should be able to use it in any country. So it allows interoperability between devices and networks in different nations, in different countries. We're not going to spend too much time about standards in this course, but let's just mention some of the organizations that create them, because you'll see them throughout this course, and you've probably seen some of them, or most of them already, or heard of their names. So this is a list of five main organizations that create standards relevant for us, relevant for data communications and computer network. First one, the International Organization for Standardization, ISO. So an organization with representatives from every or most countries in the world, usually say from some government agencies in each country, get together, and agree upon ways to do things, not just communications, but many different things. Procedures for management, for quality control, communications, electrical standards, standards for building, standards for how to manufacture different devices, so not just about communications. You may have seen on signs ISO 9001, it's about a standard for quality control in how to manage an organization. ISO creates standards also for communications.  Maybe the main one that comes up is we're looking at the TCPIP protocol architecture. It has five layers. There's another old one that we mentioned last week, which is called the OSI protocol architecture, a seven layer architecture. ISO created the OSI model. Another one which focuses mainly on or just on telecommunications. So think of landline telephone systems connecting the normal home telephone network across countries, mobile phones. ITU, the International Telecommunication Union, standardizes the technologies that we use for telecoms, for mobile phones, for internet in some cases and for home landline telephones. So they create standards. IEEE, this is an organization that is made up mainly of engineers, electrical, electronic engineers from universities and from companies. And they've created a large organization that does many things, but in terms of standards, they create standards for products, electronics, radio, electrical engineering, including communications. So that's one you would have seen or possibly seen in product literature, manuals for devices. Anyone tell me the name or the number for an IEEE standard? Use it every day. What's an IEEE standard that you may know of? Any idea? You may have seen it. You may even seen it on your mobile device, on your tablet, on your phone. It usually comes with a different name, but the real name. Anyone use Wi-Fi before? OK, Wi-Fi is think of this as a marketing name or a brand name. The general technology is called a wireless LAN, a local area network, but we connect wirelessly. So when you connect to the SIT wireless network, you're connecting to a wireless LAN. We often call it by its marketing name Wi-Fi. What is the standard used for Wi-Fi or wireless LAN? Well, it was created by IEEE, the organization, and they gave it a number, 802.11. That's just the number of the standard. You can look up and find the document, or in fact, a set of documents that describe how does my laptop send to that access point? What signals does it send? What type of data does it send? So IEEE 802.11 is a standard. Wi-Fi is just think of that as the marketing or the brand name. So this is the technical name. When you use wired LAN, you plug the cable in, also created by IEEE. They create many standards regarding local area networks. And the number is 802.3. In fact, there are many 802s, up to 20-something. Some of you may have heard of Wi-Max. That's an IEEE standard. Wi-Max, and there are other wireless and wired protocols created by this organization, or standardized by this organization called IEEE. And they create other things, not just communications. This one, I think it's correct. Remember yesterday, anyone know what that is? The common name or the brand name for that? You may not use it so much as an alternative for USB. Maybe connect video cameras. Apple Mac had them for a while, Firewire. So in the past, that was a standard for connecting devices together via cables. Again, standardized by IEEE. And there are hundreds, if not thousands, of different standards in electrical, radio, and electronic engineering. Another one. So the next one, the fourth one, creates standards mainly about Internet and the protocols used in the Internet. The Internet Engineering Task Force, IETF. So the IETF is responsible for things like TCP, IP, UDP, originally HTTP, and many of the other protocols. Do we list some up here? Many of these protocols here, in the top three layers, standardized by the IETF, some of them. They have hundreds, if not... Hundreds of protocols described. I'll not try to list them all. All of these, standardized by IETF, all of these above. So they create protocols for Internet communications. Last one, where do we get to? The World Wide Web Consortium, W3C, develops web-based standards. Think of languages we used in web applications. HTML, all the variants, XHTML, HTML5, XML. And the many things that are used for web applications created by W3C. So they're the main five that are related to data communications and networking. Be aware of them, so when you're reading something and you see IEEE something, then you know, this is an organization that creates standards. You may not remember what these numbers mean, but you know this is some standard for data communications. There are others, so there are others. Sometimes companies get together to create forums and create standards. And the other aspect is there's usually government agencies that also standardize how we use communications inside a country usually. A good example is in Thailand is how we use the different wireless or radio frequencies for communications. When we use wireless communications, we send some signal through the air, some radio signal. At a particular frequency or range of frequencies. And we'll cover it more in transmission media, but there's only a certain range of frequencies that we're allowed to use. Who sets that range of frequencies? Anyone know in Thailand, the name of the organization, that manages the different frequencies that we can use for AM and FM radio, for wireless LAN, for 3G mobile communications. Who's the organization that controls those frequencies? You would have heard of them at least in the news if you follow the news for the last maybe two years, especially related to 3G. There were some options for 3G licenses where the government wanted to auction off access to frequencies and the companies like AIS, True and so on wanted to license those frequencies, pay some money to use them for 3G communications. The organization, the government organization is NBTC, the National Broadcasting and Telecommunications Commission. They are an agency that says, who can use what frequencies? Of course, in fact, they form from two agencies that come together, one the broadcasting, one telecommunications and they were joined together one or two years ago. So if you want to start your own AM radio station in Thailand, you need to get a license from them to use a particular set of frequencies. And each country usually has a similar organization that controls or regulates the frequencies available and other communications systems. Enough about standards, that was very quick and we won't see much more about them. What we want to do today is, the rest of today is cover most of these two topics about addresses. When we want to communicate with another entity, we normally need to know who that other entity is. So we give it an address. And in fact, we're going to skip, well, we're going to switch between these two a little bit. We'll go through some concepts from both and then we'll go through an example that demonstrates those concepts. And tomorrow we'll start on the last part about performance. So I'm going to skip through some slides and come back as needed. This just shows some more example protocols, not many more than what we saw on a previous slide. And it only shows for the network layer back from this side. You can make your own notes. This is the network layer, the middle layer. This is the transport layer and above we think of the application layer. So it's just some example protocols at those three layers. It doesn't show the data link or physical layer at the bottom. The important thing is that in the network layer, the main protocol is IP. Everything is based around the internet protocol. There are some supporting ones, but the main one is IP. Everything uses that. There are a few more at the transport layer and there's many more at the application layer. So just some quick examples. What do we go through? Sorry, this one. Before we go back to some of those addressing slides. Where are all these protocols in our computer? Where are they implemented? This shows the rough categories of where the five different layers are implemented in a device. You can think of the physical layer protocols and data link layer, which are about getting data across a link. The implementation of these protocols is normally in the hardware. What we call a network interface card. In some piece of hardware that connects our device, our computer, to the network. Did I pass them around last time? I can't remember. If not, have a look. It's an old network interface cards. So this is what I call a network interface card. You plug the cable in here and it gives us the computer and interface to some network. Of course nowadays they're not separate cards, they're just small chips on board or motherboard. So in a PC or most computer devices. We've got some more. These are the wireless access points but also have, if you look at the back, some sockets for wired access and some antennas provide wireless access. Not very exciting, but just to, again, it has the five sockets and here in this case, this has some chips to implement the network interface. So some of the hardware implements the physical layer protocol and the data link layer protocols. And a wireless USB device. Again, inside here, if you open it up and I'm not going to, don't open it up. There's some hardware in there that implement the wireless LAN, physical layer and data link layer protocols. Not much to see, I'm sure you've seen them before. It's not always a clean cut in that some parts that may be in the operating system but roughly we can think of these two as the network interface card. The next two layers, network and transport, are usually implemented in your OS in your operating system. If you go and look at the source code for your Linux operating system, you'll find some C source code in there that implements IP and TCP and other protocols in these two layers. So think of the transport and network layers part of the OS. Windows implements IP and TCP, so does the Mac OS and so does iOS on your iPhone and so on. So any device with internet access, normally the OS implements these layers. Application layer by applications. You find the source code for Firefox and you see some code that implements HTTP. So that's the rough separation of where would you find the hardware and software for those protocols. I go through this entire topic reasonably quick because we wanna move into the details in the next topic as soon as possible to give you some more concrete examples. We're mainly looking at concepts at the moment. Let's go back. Don't take these home with you. You could take these that are only worth, they're not worth anything. This is addresses. We wanna introduce the concept of the different types of addresses and then we'll give some examples to finish off this lecture today. Now, imagine our computers in a network. Each computer has a network interface card. Interface to a network. So we attach, our computer attaches to a network using the network interface card or generally a network interface. Each device, each network interface normally has an address on that network. We give it an address so that when we want to communicate with some other device, we can use that address to say which other device we wanna communicate with. And the name of the address that the network interface gets is one of them is called the hardware address because usually it's associated with a piece of hardware, the LAN card, for example. Maybe it's a physical, another name is a physical address, a data link address or a MAC address, but we'll use a hardware address and see that in some examples. So I take my wireless router here. I've got four sockets. There are five here. I wanna use just four sockets in the back. I plug a cable in here into the laptop, another cable into this PC and maybe two more into other computers, other laptops. So we can think we have four end user devices, a laptop and three PCs, for example, connected to this intermediate device. Each of those four computers have a network interface card and they all have an address associated with that network interface card. And what's what we call a hardware address. So my laptop has a hardware address, so does this PC because if I send data, then normally I need to indicate which of the other computers needs to receive that data. How do I do that? I set a destination address and I say, okay, my message needs to go to this destination. My message may go to here and then this one looks at the destination and then sends it to the correct computer. So we use addresses to identify where the data is gonna go to. Let's try and draw a picture to illustrate the role of addresses, starting with a simple example. I'm gonna try and draw my pictures on the screen. My drawing skills are still developing, so you will draw it much neater than I draw, okay? Let's start. We have some computers that might, well, let's draw four computers, we'll need them eventually. And let's start, we're gonna connect those two computers together in one small network, in a LAN, for example, and the other two computers in a separate network, completely separate to start with. And then we'll see what happens if you wanna join them. So they could be connected, these two computers via a cable, just directly together. And the other two maybe wireless or a different technology. And often we draw a network, instead of drawing the cables, especially when there are many computers, have to draw many lines, we draw a cloud. Let's see, something like this. Some cloud, and we say that this one connects to the cloud, so does this one. And same for the other network. That's just a concept, the cloud, a concept to say that these two are connected by some cables or some wireless connections, there may be some intermediate devices in here. The cloud's just used to represent that, in fact, we don't care about the details of how they're connected, we're just saying that they are connected somehow, okay? Inside here maybe just, it may be just one cable, or it may be tens of different devices in a very complex connection here. The cloud just means some connection. We won't worry about the details at this stage. And let's say they use different technologies. So if we treat these as two local area networks, wireless LANs, this could be using IEEE 802.11 for wireless LAN, or maybe it's using 802.3 for wired LAN or ethernet. And this one may be using something different, Bluetooth, for example, or some other old LAN technology, Token Ring or many other old technologies. So they're different technologies, different devices. Let's draw one more computer, just to say on this one. There can be many more, and it's connected. So focusing on the bottom LAN, these three computers, they're all attached to the same small network, the same LAN, to communicate with each other, they must all use the same protocol, at least the same physical layer and data link layer protocol, okay? Because think of them, they're all directly connected to each other. If you're in the same LAN here, you use the same protocol, because if this one uses a different protocol to this one, at the physical layer at least, then they will not be able to communicate. So let's assume that they use the same physical and data link layer protocols for these three computers. These two use the same as each other, but let's assume that they're different from over here. If this computer wants to send to this one, because there are two options for where the data can be delivered, we'll use some addressing scheme to say that, okay, let's give each computer an address, and when I want to send a message to one computer, I will say this message is destined to a particular address. And let's choose an addressing scheme and to keep it simple. In reality, it's more complex. To keep it simple, I'll say, the addresses are these ones, let's give them letters. Sorry, and A, B, and C. Three computers, they've got addresses A, B, and C. We'd call these, these are the hardware addresses. The addresses associated with the LAN card or the network interface card in each of those computers, a hardware address. The scheme I'm using for these computers is a lowercase letter in purple. Let's say that's part of the protocol. The address must be a lowercase letter. In reality, the addresses are structured much longer and may not just be letters, but for simplicity in this example. And similar in this other LAN, those two computers have addresses, hardware addresses, but using a different scheme or a different format are incompatible with the purple ones. Let's make them uppercase letters, B and C. This case, that one, that's a uppercase green C and B. They are the hardware addresses for these two computers. They can talk to each other, they have the same address format, but they cannot talk to these three because they're on a different network and use, importantly, a different address format. The other reason they can't talk to these three is because there's no connection yet. We'll connect them in a moment. So in different LANs and also wide-area networks across the globe, different technologies are used. In SIT, we use 802.11 wireless LAN. In some other university may use something completely different, not compatible with ours. It's up to the choice of who builds that network. So there are many different technologies with different address formats across the world. In the internet, what we want to do is allow any computer, no matter what technology they use in the LAN, allow any computer to communicate with any other computer. So two things we need at least for that. We need to physically connect the networks. So let's connect them. Let's put in another device, a special device in the middle that connects these two. So we've got a physical connection, some cables that connect. This special device in the middle has the role of getting data from this network to this one. Even with this connection, we have a problem in that if uppercase B wants to send a data to this computer, it doesn't understand the address format of this computer. It knows nothing about these lowercase addresses. It implements only this protocol with the green uppercase addresses. So what we do in the internet is, in fact, for all the computers that we want to allow to communicate, we give them a second address, a network address or a logical address, where the second address all follows a common format. Let's give them a second address and then explain. So each computer now has what we call a hardware address, the one shown, and we give them a second address. Let's just give them numbers. And I've used a different address format here. Now, if this computer wants to send a here, it says, okay, the destination is computer 3, not computer lowercase a, but computer 3. It would send the data to this intermediate device, which would then deliver it to computer 3. The hardware addresses are used locally on this network. To communicate from this computer to here, it goes from C to B. Similar from this device to here goes to computer A. But across different networks, we use a logical or a network address. The numbers in this simplistic example. What are these common addresses in the real world? We'll come back to that picture. We have two types of addresses now. Every network interface normally has a hardware address, which is specific to the local network it's on. But to connect to the internet, those network interfaces may also have a second address called a logical address, maybe easier an IP address in real life. In the internet, the logical addresses are internet protocol addresses, an IP address. IP addresses and hardware addresses are not letters and numbers like I drew on the example. They're in fact long sequences of bits. We'll see some examples shortly. So in most cases in the internet, our devices have two addresses, hardware address. But since across the world, there are many different technologies to allow them to communicate, we also have a second address, an IP address. The numbers in this simple example. To communicate across the internet to another computer on the internet, that other one needs an IP address. It normally will also have a hardware address. To demonstrate these concepts of addresses and a few more addresses, I've got some examples to go through. What are we going to do? We have about 30 minutes remaining. Do you want to break or we keep going? Option one is that we stop now for our normal break and then start again and go for another 30 minutes, maybe 35 minutes. Option two is we just keep going now and finish by 3 p.m. and then finish for the day. Option one, stop, have a break, hands up. Option two, keep going now. Anyone know hands up? Option three, go to 4 p.m. No, okay, let's keep going. We'll see if we can finish. We should finish by 3 p.m. There's no option four, stop. That's all right. Because the CS section we've had election they're a bit ahead of here, so we need to catch up with them. So, summarise so far on addresses. In the internet, normally each network interface has two addresses. It has a hardware address that identifies that piece of hardware on the computer and a second, sometimes optionally second address that identifies that interface in the entire internet called an IP address. So we'll see two types of addresses. It turns out we don't always have to have an IP address. Most devices have a hardware address. Only when we say we're connected to the internet do we get an IP address. Two types of addresses are common. What's the IP address of your phone? Don't know. Do you know how to find it? Okay. All right. Simple one then. What's the IP address of the web server that you access for this course? I call it the ICT server. When you access and do the quiz, what's the IP address? I see someone's getting close. 10.10. Others are blank faces. What's the domain name of the ICT server? ICT.sit.tu.acd.th, okay? Most people can remember the domain name. Not many people can remember the IP address. They are the same. They identify the same computer in the network. That is, our computers really on the internet are identified by IP addresses. The ICT server has an IP address. My laptop, when I access the internet, has an IP address. All computers have an IP address when they're accessing the internet. But some of those computers, when we need to remember their name or how to contact them, they have a third address, a domain name. It's not listed here, but an example, a domain name. Google.com or ICT.sit.tu, so on. So what are we now? Computers have IP addresses and some computers have what we say is human-friendly addresses, domain names. I call them human-friendly because us humans can remember them. We can write them down easier. IP addresses are what's actually used to communicate between computers, but for us humans to not have to remember IP addresses, we use domain names. And there's a mapping that is a domain name maps to some IP address in the simple terms. That is, some domain name and some IP address can represent the same computer. So normally in the internet, all computers have an IP address. Some of them may also have a domain name as a simpler name. So that's a third type of address. Hardware address, IP address, domain names or user-friendly addresses. And related to them are some specific applications like some email address, some user at a domain name, where the domain name actually corresponds to an IP address. So we see different types of addresses not just IP and hardware. And another type we'll just mention here and cover in a later topic, port numbers. Hardware addresses identify a network interface on a particular or on a specific network. IP addresses identify a network interface on the internet. Port numbers identify applications on a computer because on my computer I can run many applications at the same time. Web browser, email client, instant messaging, web server all on the same computer. To identify them we use another type of address called a port number. In simple terms, port numbers identify applications or software processes representing applications. So far four types of addresses hardware, IP port numbers and the user friendly addresses like domain names. I want to show an example that illustrates all these addresses, or most of them and also some protocols. The example is going to be web browsing. But just before we go through the example let's just say, well what is web browsing? You know, you web browse all the time but what type of messages do we send when we're web browsing? What are the entities involved? Web browsing uses a protocol called the hypertext transfer protocol HTTP. There are two entities involved normally. A web browser running on one computer an application called a web browser and on another computer an application called a web server. So this diagram is showing this is one computer we're going to see the messages sent between these two computers when we're web browsing. First what happens is the user opens their web browser they type in a URL in the address bar type in a URL maybe click on a link but let's say we type in a URL and we press enter. That's step one. When we press enter on our web browser after typing in that URL the web browser goes to work using HTTP sorry that we've started early but we'll catch up with you later because we had a class cancel before but there's plenty of chances to catch up don't worry. There may be a few other students as well that missed out on this early start but I'll deal with them separately. What does our web browser do? Using HTTP it sends a message to the web server so my web browser on my laptop maybe the web server in the US sends a message saying I want to get this web page that's the meaning of the message where the web page is identified in the URL in this example I say the web page is in the test directory it's called index.html just as an example we send a message from web browser to server saying I want to get this page when the web server receives this request the web server looks checks do I have this page on my hard drive does this page exist if so is this web browser allowed to access if so then the web server looks at this file on its hard drive reads it in and sends back a response the response gives some status message saying everything is okay don't worry about the details here just go through the general concept of we send back a response saying your request was okay I have the web page and the server takes the contents of this requested page and puts it in the response in this case some HTML you've all seen some HTML sends this in a message back from the server to the browser the browser receives this response the browser reads the contents of the message and uses that to display something on the screen for example the title of the page and the browser his test and some contents whatever is on that web page the very basics of HTTP browser sends a request to the server for a page the server sends back the web page that they requested let's now look at an example you can see some addresses and web browsing work on in real life first let's look at some address details of my computer I run a Linux operating system you know in Windows you can look at your network connections in the control panel or wherever you look at network connections and you can look and find the properties of your LAN or your wireless LAN so I'm going to do that on my computer there are different ways to do it on the command line I have here a program called IFconfig IFconfig shows me the configuration of my different network interfaces IF is sure for interfaces so to configure my interfaces so it shows me a summary of my I3 available network interfaces just fix this screen can we see everything yeah I have 3 network interfaces currently on my laptop available one's called EDH0 one's called LO and the third one's called WLAN0 you should better guess what 2 of them represent the bottom one what is that my wireless LAN interface on my laptop and the network interfaces it has it doesn't have one of these cards it's got a smaller chip on the motherboard and a socket for my wired LAN which is called Ethernet there's an EDH interface which I know means the wired LAN interface I also have wireless LAN in the laptop so the name of that given by my operating system is WLAN0 and Ethernet is EDH0 my wired LAN interface some statistics and details my wireless LAN interface we'll look at the details in a moment what's the third one local host, local loopback or LO here it's a very special one it's not a real network interface it's a virtual one it's only used if I want to send something to myself it doesn't make much sense for what we're dealing with just for testing purposes so for now ignore the middle one we won't even try to explain it yet imagine there's just two interfaces my wired LAN Ethernet and my wireless LAN my laptop has Bluetooth but I've turned it off so we don't see anything about Bluetooth here and normally we will not currently or before I connected to the SIT wireless LAN for internet access let's look first at the details of my WLAN interface just some of the information this is the hardware address for my wireless LAN interface hardware address here that's fixed for my wireless LAN chip inside my laptop this address is not letters, lowercase or uppercase letters it's in fact a sequence of hexadecimal numbers 12 hexadecimal digits they look random in fact there's some structure in them but it's an address that identifies my wireless LAN interface on my laptop we can see my wired LAN interface has a similar structure address hardware address different value but same structure in fact wired and wireless LAN use the same type of address 12 hexadecimal digits how many bits back to the wireless LAN 12 hexadecimal digits ignore the colon here just 12 hexadecimal digits how many bits remember hexadecimal hexadecimal how many bits in one hexadecimal digit what do we need alright you're too advanced one hexadecimal digit we can have 16 possible values from 0 up to f where f in decimal is 15 how many bits do we need to represent 16 possible values 4 with 4 bits from 0 0 0 0 that is 0 in decimal up to 1 1 1 1 which is 15 in decimal to represent 1 hexadecimal digit we need 4 bits for binary digits so this is 12 hexadecimal digits if we convert it to binary it's in fact 48 bits when our computers communicate they in fact using binary for everything they send it's just that this software and it's very common instead of writing 48 bits here it's very hard to write and remember 48 bits they convert it to hexadecimal it's just a convenient way for humans to write down addresses it's actually a 48 bit number but we write it usually with hexadecimal digits most all wireless LAN and LAN cards have a hardware address and in most cases they are unique globally unique the hardware address of this device was programmed into it when the manufacturer made it and in this device made by the same company has a different hardware address and it's different from my wireless LAN made by a different company and different from my wired LAN so in theory all wireless and wired LAN devices have unique addresses in practice there are some exceptions but for now they are unique so both of my interfaces have a hardware address my wireless LAN interface has also an internet an iNet address or an IP address <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS> really binary values, IP addresses use decimal in this structure of four decimal numbers separated by dots called dotted decimal notation. It's actually again, a binary value. It's 32 bits. We're not going to explain how to convert between this <IP_ADDRESS>.1.2.17 to binary. We'll do that in a later topic. Although it looks like decimal numbers here, that's just to make it easier for us to look at, it's actually a 32-bit binary address. There are some other addresses which are also IP addresses which are associated or connected with this main one. This is the main one here. In the internet protocol there are two main versions available, IP version 4 and IP version 6. IP version 6 is the new one. It's not as common as IP version 4 at the moment, most of us use IPv4. My computer also has an IPv6, an INET6 address, this long one here. We will not cover the structure of this, it's actually 128 bits long, but in hexadecimal. IPv4, 32 bits, IPv6, 128 bit addresses. In a course next semester you'll cover IPv6 in details. So the main thing to take away at the moment, hardware address, IP address. My ethernet interface has a hardware address but no IP address. I'm not currently connected to the internet via my wired LAN, I don't have a cable plugged in. In practice we only get an IP address when we need one on demand. So my wireless LAN has one, if I turn off my wireless LAN it will eventually disappear. If I plug in a LAN cable I may get an IP address up here as well. The rest are some statistics and information about the network interface. Not important at this stage. Okay, let's browse the web and I want to give a demo. I'm going to open, where do we go? First I need to start some software. What I'm going to do is visit a website. And I want to record everything that happens when I visit that website. Specifically when I visit a website my computer sends messages out and it receives some messages. Those messages we often call packets. It sends packets and receives packets. I want to see what packets my computer sends and receives. So for this demo I'm going to start some other software that will record everything that I send and receive. It's called some packet capture software. The name is Wireshark. Let's start. When I start this Wireshark software it's going to record everything that my computer sends and receives. And then we'll be able to look at the details. We'll start it in a moment. Just so I can delete the cache. Let's set things up. What I'm going to do, I've typed in a URL which indicates I'm using the protocol HTTP. I'm going to access some domain called sandylands.info. And specifically I want to access a file called IT1 in the test directory, IT1.html. I'm going to press enter in a moment which will trigger my browser to send a request to this web server identified by sandylands.info. And request this web page. And hopefully the web page will come back and be displayed on the browser. Before I do that I want to tell this Wireshark software to record everything that I send and receive. Let's do that. Let's capture everything I send and receive. Everything I send and receive over the wireless LAN interface. You don't have to know the details of this software at the moment. And it's capturing. It looks a bit strange at the moment. But we see many things changing colour. We'll come back to that. My computer is always sending packets out and receiving packets in. And this is listing them here. So we're going to have a look at the moment. My computer does things in the background like the operating system does updates, instant messaging does updates and so on. We'll come back to that. Now, I'm going to visit this web page, press enter. It connected to the server and the server was sent back a web page saying test IT1 is the title and something on the page here. Now let's go back to the capture and see the packets which went out. So I have to stop this. There are hundreds, thousands, 2,000 packets captured then. My computer sent and received 2,000 packets during that one minute or so when I captured. I want to look at just some of them, the ones that were sent directly by my computer. First, let's go back. Let's record. What's my IP address? My IP address is <IP_ADDRESS>. That's my computer. Who did I send to? Anyone know? What IP address did my computer send to when I accessed the web server? Or what other address? Sandylands.info. That is, that's the domain name. This is the address that identifies my laptop in the internet. The address that identifies the web server, well, I typed in the domain name sandylands.info, but what IP address? Well, we can check in fact. There's a mapping that tells us for some domain name, what is its IP address and we can look up this mapping and say if I have the domain name sandylands.info, this program NSLookup tells us the name sandylands.info actually has the IP address <IP_ADDRESS> so my computer 1010 and I'll write it down before I forget, 1010 102 .17, my laptop sent to the server which has IP address <IP_ADDRESS> sandylands.info is just a human friendly name for <IP_ADDRESS> It's something I can remember. I can't remember the IP address Now let's see what we sent between those two There are 2,000 packets here. I want just five or six so I need to filter out it's filter You'll see the details of this software maybe in an assignment in a lab next semester, but that's just quickly goes through in the next 10 minutes Everything sent to <IP_ADDRESS> I'm creating a filter that says show me all the packets with IP address equal to that of my server and at least them here. Now let's explain what we see This software shows us all the messages sent and received by my computer and at the top these green and black ones Each row represents one message or one packet. We can see Sorry, you cannot see it's 39 here the time at which this packet was recorded From when I recorded the first packet at time zero This packet was recorded 39 seconds later from when I started Not so important for this demo What's important is that these two columns show me for this packet the source computer was 1010.217 my laptop The destination computer was <IP_ADDRESS> so This information is in fact recorded in the messages sent So this software sees this information. It sees that one computer sent to another one Info gives us a summary of what's inside this message We won't look at them all. We'll see the first one here is sent by my laptop to the server Second one is from the server back to my laptop We see the source and destination are reversed This one we may recognize something especially in the info field Who sent it? The highlighted orange one who sent that who sent the orange highlighted packet laptop sent it to the server easy and Note the info field says get slash test slash IT1.html. This is the request from my browser going to the server That's this message Okay This is my browser It's the HTTP request going from browser to the server Can anyone see the response? We know with HTTP we send a request to the server The server sends back a response. Hopefully with the web page Can anyone see the response? What does the response say in the info field? Is this the response? No Here's the response. All right. You may not have you The only way we can identify at this stage is that it has this 200 ok saying It's coming from the server 106 Going to my laptop it's coming back and We saw briefly before what HTTP does is we send a request to the server the server sends back If everything's okay, it sends back a an okay message and it should include the web page in that response So these are the two main messages in this exchange There are others that happen also if I just look at those two to finish up when I select a message in this second Part of the the interface here it shows the details of that one selected message So this one message from my laptop to server here are the details of that message or that packet It gives me some information that it says well what protocols were used for this message HTTP was used. We know this is part of web browsing. We expect it to be a HTTP message HTTP is part of the application layer What's the next layer? going down Application at the top. What's the next layer? transport, okay In this software think of it upside down This represents the application layer protocol HTTP Then The name of the transport layer protocol is shown here TCP and The network layer protocol you see it's in birth here is IP and then the data link layer And that's all it shows is ethernet or a land protocol. So if we drew our stack application transport network data link physical The actual protocol is used in this one packet at the application layer HTTP At the transport layer. So we're going up there TCP network layer IP is used and In fact, this software only captures a little bit about the bottom two layers and it simply calls it ethernet in this case the actual signals which are sent are not recorded. It's just the information from the operating system So it gives us a little bit of a summary about what protocols were used in this one message From a layered perspective. It gives us the addresses For the those protocols in particular a source and destination When I sent the Message, what was the source hardware address and destination hardware address they listed here What was the source IP address? 10 10 1 0 2 17 destination IP address We mentioned that there's another type of address called a port number and they are listed here So this software will tell us information about who was communicating with who and in fact we can expand and see many more details This is the response message Going from server to laptop. We see the same protocols HTTP TCP IP ethernet this response Also contains the web page I'll expand this this packet Sent from server to my laptop when my computer recorded it it sees the actual HTML Which was sent from the server? using HTTP using web browser protocol so this is the exact HTML which is Shown on my web browser. I can check I can view the page source and see You can check that this web page is in fact carried in that one packet that one message from server to Server to laptop There's a lot of information here and especially the first time you see this this capture using wireshark There's a lot of information. It's very hard to take in so we will not try and go through all the any more details here Main point is we've seen an example with web browsing and I've seen two important messages one from Laptop to server and the second one this one is the response coming back in HTTP we send a request for a web page the server sends back that web page The contents of the page the file in the response message Also shown Each pro or many of the protocols use different types of addresses Usually a source and destination address Who did it come from who is it going to? We see port numbers IP addresses and hardware addresses When we look at those individual protocols later, we'll see the roles of those addresses and The exact structure of them port number 80 for example You may have seen is a common is commonly used for web service every web server uses port 80 Other is a random number for my web browser Questions I'm going to stop there for this this part. It's a lot of information for today Any questions You've got one hour for questions easy No, what's hard? What is hard try and pick up some main concepts from each lecture Today we've talked about We've introduced different types of IP address of addresses hardware IP addresses briefly with mentioned port numbers and User-friendly addresses like domain names so different types of addresses were used We've seen web browsing a very simple example of web browsing. What does it involve HTTP? We send a request for a web page server sends back the web page very simple protocol What else have we seen today? Seen some standard organizations IEEE ISO IETF and others and There's some common standards And we've seen finally in this example. Well Here is an example of the actual protocols in use From a lab perspective HTTP TCP IP ethernet We don't see the physical layer But an example of most of the protocols If you go through and look at the two thousand other packets You'll see many other protocols in use not just this for you'll see others in use Let's stop there for today What we've got remaining Mainly on the performance will do that tomorrow morning. Okay, we'll try and finish this topic tomorrow morning


The GitLab security configuration makes it easier for you to add security scans to your GitLab projects. Other than adding templates to the GitLab YAML file, you can configure security scans in a visual way. We can access the security configuration by going to the Security and Compliance tab and clicking on Configuration. Here we have the Security Configuration UI page. It lists the name, description, documentation link, whether it is available or not, as well as the Configuration button or link to a configuration guide for several security testing and compliance tools. You can configure SAST, also known as Static Application Security Testing, infrastructure as code scanning, IAC. DAST, Dynamic Application Security Testing, Dependency Scanning, Container Scanning, Cluster Image Scanning, Secret Detection, API Fuzzing, as well as Coverage Fuzzing. We're going to go ahead and enable SAST on our project. To do this, we just click on the Enable SAST button and then we are taken to a configuration screen. Here we can change configurations depending on the different scanners available. You can see that there are several different SAST scanners for different languages that have additional configurations. Note that each configuration is unique per scanner. Now let's click on Create Merge Request. This creates a merge request that adds SAST to our pipeline in the way we configured it. Let's take a look at the changes. We can see that SAST has been added to the test stage and our YAML has been altered. Now click on Create Merge Request. Let's make sure that it is merged when the pipeline succeeds. So that way we're always scanning each time a merge request is created. Now if I take a look at the pipeline, I'll see that there is a newly added test stage which is running the SAST configuration I created via the configuration UI. The configuration UI makes it easy to add and configure security scans in your project.


Today, Thursday, December 17, 2020, the Ministry of Health and Wellness received confirmation of one new case of COVID-19. This is from a total of 145 samples tested with one positive and 144 negatives. This brings a total number of cases diagnosed in country to date to 279. Case number 279 is a 39-year-old male from the Grozile district, who is also recording acid blusher's 5th COVID-19 related death. Yesterday, Wednesday, December 16, 2020, case number 279 came into the respiratory facility as a critical patient with other severe underlying medical conditions. At the time of admission, the individual was assessed and also tested for COVID-19. The individual passed away while in care. An epidemiological link has not yet been established for this case. Investigations are ongoing by the contact tracing team to determine any possible existence of a link with this case. The Ministry of Health and Wellness, we express condolences to the family and loved ones of this individual. The Ministry simplifies this with the family during this time of loss. It is important that we continue practicing the infection prevention and control guidelines to minimize the spread of the virus. Wash your hands during the day using soap and flowing water, wear a mask in public places and ensure it covers the mouth, chin and nose. Maintain a distance of 6 feet from others. Use a bleed solution to sanitize frequently touched surfaces and frequently handled objects. Also avoid contacts with other persons who have flu-like symptoms. If you are experiencing flu-like symptoms, keep away from others and seek medical care at the closest community respiratory clinic. The Ministry of Health and Wellness will continue providing updates as new information becomes available.


People see it and they go, oh my gosh, this is gorgeous. Tell us about how you made it and then how you construct these beautiful cascading arrangements to honor our Lord and our Lady through the year around it. It is a really fun process. It actually uses, I use chicken wire for that because we have lots of chickens, so we have chicken wire and I went and I cut all kinds of chicken wire and I used three M strips because, you know, I didn't want to mess up the wall, so the three M strips of the hooks and I hooked them all around. Actually, this is something I haven't said to anybody before but this is my second, that was my second attempt. The first attempt, I guess I was too hasty when I put on the three M hooks. It all crashed right after I had put it up. But God and His Providence, I took all those flowers and I made a long table, a range of clusters of flowers and laid blooms and that ended up making the book as well. So it just goes to show that God has better plans than I do.