Bonding and Network Configuration | Into the Terminal 44

Поделиться
HTML-код
  • Опубликовано: 15 янв 2025

Комментарии • 10

  • @rohith19861
    @rohith19861 2 года назад

    Thank you Eric, missing you this week Scott. all the sessions are very informative.

    • @scottmcbrien6535
      @scottmcbrien6535 2 года назад +1

      Thanks so much Rohith! I was speaking to my local Red Hat Users Group and Eric did a great job. Though I could tell by his face he was really lonely without me. 😂

    • @RedHatEnterpriseLinux
      @RedHatEnterpriseLinux  2 года назад

      You are very welcome!

    • @itguyeric
      @itguyeric 2 года назад

      @@scottmcbrien6535 I very much missed having you!

  • @hangoutbuddy
    @hangoutbuddy 2 года назад

    Nice explanation. Will help me in my preparation for ex358 exam 👍🏻

  • @dewaynebranch776
    @dewaynebranch776 2 года назад +1

    awesome, i will go do the labs

  • @seedney
    @seedney 4 месяца назад

    Can we make some kind of firewall VM and tell hypervisor to only connect to outside world through it?

    • @scottmcbrien6535
      @scottmcbrien6535 4 месяца назад

      Maybe? But is it really the Hypervisor you're looking to restrict in this scenario or is it the other VMs running on it? If you're looking to route all your traffic through a specific VM, I'd suggest something more like connecting your VMs to a KVM specific defined network, then having one of the VMs act as the router for that network, configured with an additional connection to the hypervisor.

    • @seedney
      @seedney 4 месяца назад

      @@scottmcbrien6535 Yes, I'm looking to restrick my entire machine - including hypervisor. I know, that better solution will be hardware way - buy better network gear, but I need a budget for that ;-)