To my experience, if a DHCP client tries to renew its lease, but the DHCP server is down, and after the lease time is over, there are two possible scenarios:
I've seen the two scenarios before with different vendors.
I can't find exactly which one is according to the standard. Can someone help? Thanks!
If I go inside the file /etc/ssh/ssh_config, I can see "$OpenBSD" at the top of file. However, if I change the default port to a different value, it doesn't seem to work. A colleague informed me that's because Dropbear is the software server here, not OpenSSH.
Is there a way to be sure? I can't find an answer googling that.
I work in a relatively small company that develops and produces switches/routers. Our devices support BootP and DHCP servers/clients. We have a few bugs in the BootP and I'm thinking about suggesting the complete removal of this feature.
I've been dealing with other companies for 10 years now and I've never met a customer that deploys BootP on their devices. Only DHCP. So I think it's not worth the effort to fix BootP and just simply remove this non-used feature.
Question: Is BootP still being used out there? Didn't the DHCP replace it (completely) already?
We are in the planning/brainstorming phase of considering migrating to Cloud.
We came to an initial conclusion that we don't want a full-cloud solution. We think "initially" it's in our best interest to use Exchange, Lync and SharePoint as SaaS applications while keeping "all or most" of our user data on-premise.
Question: Is this option even possible? If so, recommended in terms of maintenance for example?
Edit: By searching on the Internet, all what we can find is either Only-Cloud or Hybrid authentication. But no one talks about user data on-premise.
Just recently I came to know that the payload of Ethernet is max 1500 bytes (mtu).
The first thing that came to my mind was that we can ping with much more size than that. So I thought maybe the ping packet is being fragemented in someway. So I checked on wireshark and I saw that it's only one packet, even when I ping with size of 10,000 bytes.
What is the explanation behind this?
Update:
Even if Jumbo Ethernet frames are used, which supports till 9000 bytes, I can still ping with like 17,000 bytes which is still larger than 9000.
Out of curiosity, I'm checking the Wireshark DNS packets. I can see that there's a DNS query from the host, and then DNS response from the DNS server. Everything is just as expected.
However, if you further check in the query, you can see that the server also sends the NS (authoritative name server). My question is: why?
As a host, I only care about the IP. That's the main point of DNS, to resolve a name into an IP address.
Why, as a host, would I need the NS info?