User Tools

Site Tools


software:linux:opensuse

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
software:linux:opensuse [2020/12/26 19:21] – [Bridging networks] superwizardsoftware:linux:opensuse [2021/03/05 18:26] – [OpenSuse] superwizard
Line 1: Line 1:
 +====== OpenSuse ======
 +
 +------------------------------------------------------------------------------------------------------------------------------------------------\\
 +\====== Configuring firewall ports ======
 +
 +
 +<WRAP center round box >
 +**Command line open ports in firewall**
 +
 +sudo firewall-cmd --zone=public --add-port=5000/tcp 
 +
 +
 +https://forums.opensuse.org/showthread.php/533831-Opening-ports-in-the-new-YaST2-Firewall
 +</WRAP>
 +
 +
 +<WRAP center round box >
 +**Use Yast to configure open ports in firewall or turn firewall off**
 + 
 +    * what ports are open using vsftpd
 +      * firewall-cmd --permanent --service=vsftpd --get-ports
 +        * 21/tcp 30000-30100/tcp
 +    * what ports are open using Samba
 +      * firewall-cmd --permanent --service=samba --get-ports
 +        * 137/udp 138/udp 139/tcp 445/tcp
 +    * Reference: man firewall-cmd
 +</WRAP>
 +
 +====== Hyper-v Video Resolution ======
 +
 +<WRAP center round box >
 +2021-01-23
 +
 +Works on grub
 +
 +Set resolution
 +
 +Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT (line is highlight on image) and add video=hyperv_fb:[the resolution you need]
 +ex:- video=hyperv_fb:1200×700
 +you may need to change the above value several time to achieve better screen size. 1200×700 is the value which is worked on my 1366×768 resolution windows server.
 +
 +[[https://www.tectut.com/wp-content/uploads/2015/02/1.png]]
 +
 +
 +[[https://www.tectut.com/2015/02/changing-linux-screen-resolution-in-hyper-v-virtual-machine/]]
 +
 +</WRAP>
 +
 +====== Hyper-V Synthetic Video Frame Buffer Driver ======
 +
 +
 +<WRAP center round box >
 +This is the driver for the Hyper-V Synthetic Video, which supports
 + * screen resolution up to Full HD 1920x1080 with 32 bit color on Windows
 + * Server 2012, and 1600x1200 with 16 bit color on Windows Server 2008 R2
 + * or earlier.
 +
 +[[https://github.com/torvalds/linux/blob/master/drivers/video/fbdev/hyperv_fb.c]]
 +
 +</WRAP>
 +
 +
 +====== Configures video settings for virtual machines PowerShell ======
 +
 +
 +Set-VMVideo
 +
 +Module: 
 +    Hyper-V
 +
 +Configures video settings for virtual machines.
 +Syntax
 +PowerShell
 +
 +Set-VMVideo
 +   [-CimSession <CimSession[]>]
 +   [-ComputerName <String[]>]
 +   [-Credential <PSCredential[]>]
 +   [-VMName] <String[]>
 +   [[-ResolutionType] <ResolutionType>]
 +   [[-HorizontalResolution] <UInt16>]
 +   [[-VerticalResolution] <UInt16>]
 +   [-Passthru]
 +   [-WhatIf]
 +   [-Confirm]
 +   [<CommonParameters>]
 ====== Resilio Sync ====== ====== Resilio Sync ======
  
Line 48: Line 134:
     echo 0 > /sys/devices/virtual/net/br0/bridge/multicast_snooping     echo 0 > /sys/devices/virtual/net/br0/bridge/multicast_snooping
  
-</WRAP> 
  
 From <https://unix.stackexchange.com/questions/272146/packets-not-moving-through-linux-ethernet-bridge>  From <https://unix.stackexchange.com/questions/272146/packets-not-moving-through-linux-ethernet-bridge> 
  
 From <https://unix.stackexchange.com/questions/272146/packets-not-moving-through-linux-ethernet-bridge>  From <https://unix.stackexchange.com/questions/272146/packets-not-moving-through-linux-ethernet-bridge> 
 +</WRAP>
  
 <WRAP center round box > <WRAP center round box >
Line 65: Line 151:
   post-up ( echo 0 > /sys/class/net/$IFACE/bridge/multicast_snooping )   post-up ( echo 0 > /sys/class/net/$IFACE/bridge/multicast_snooping )
  
-</WRAP> 
  
 From <https://pve.proxmox.com/wiki/Multicast_notes>  From <https://pve.proxmox.com/wiki/Multicast_notes> 
 +</WRAP>
  
 <WRAP center round box > <WRAP center round box >
Line 81: Line 167:
  
  
-</WRAP> 
  
 From <http://www.microhowto.info/howto/bridge_traffic_between_two_or_more_ethernet_interfaces_on_linux.html>  From <http://www.microhowto.info/howto/bridge_traffic_between_two_or_more_ethernet_interfaces_on_linux.html> 
 +</WRAP>
  
 <WRAP center round box > <WRAP center round box >
Line 95: Line 181:
     ip link set dev eth0 down     ip link set dev eth0 down
  
-</WRAP> 
  
 From <https://tldp.org/HOWTO/Linux+IPv6-HOWTO/ch05s02.html>  From <https://tldp.org/HOWTO/Linux+IPv6-HOWTO/ch05s02.html> 
 +</WRAP>
  
 <WRAP center round box > <WRAP center round box >
Line 105: Line 191:
    ip link set [interface] promisc on    ip link set [interface] promisc on
  
-</WRAP> 
  
 From: https://www.thegeekdiary.com/how-to-configure-interface-in-promiscuous-mode-in-centos-rhel/ From: https://www.thegeekdiary.com/how-to-configure-interface-in-promiscuous-mode-in-centos-rhel/
 +</WRAP>
  
 <WRAP center round box > <WRAP center round box >
 +
 +{{ :software:linux:tcpdump.pdf |tcpdump Cheat Sheet}}
 +
 **D.3. tcpdump: Capturing with “tcpdump” for viewing with Wireshark**\\  **D.3. tcpdump: Capturing with “tcpdump” for viewing with Wireshark**\\ 
 It’s often more useful to capture packets using tcpdump rather than wireshark. For example, you might want to do a remote capture and either don’t have GUI access or don’t have Wireshark installed on the remote machine. It’s often more useful to capture packets using tcpdump rather than wireshark. For example, you might want to do a remote capture and either don’t have GUI access or don’t have Wireshark installed on the remote machine.
Line 135: Line 224:
  
  
 +<WRAP center round box >
 http://www.rsyslog.com/ http://www.rsyslog.com/
  
Line 141: Line 231:
 http://en.wikipedia.org/wiki/Rsyslog http://en.wikipedia.org/wiki/Rsyslog
  
 +
 +</WRAP>
 === Properties === === Properties ===
  
 +<WRAP center round box >
 http://www.rsyslog.com/doc/property_replacer.html http://www.rsyslog.com/doc/property_replacer.html
 +
 +</WRAP>
  
 === Changes to setup a log for mediatrix === === Changes to setup a log for mediatrix ===
Line 529: Line 624:
 [[fedoraproject.org wiki Systemd>>http://fedoraproject.org/wiki/Systemd]] [[fedoraproject.org wiki Systemd>>http://fedoraproject.org/wiki/Systemd]]
  
-Systemd_Cheatsheet =+**Systemd_Cheatsheet** 
 + 
  
 From: http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet From: http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
Line 559: Line 655:
  
 From <https://opensource.com/article/20/7/systemd-timers?utm_medium=Email&utm_campaign=weekly&sc_cid=7013a000002glehAAA>  From <https://opensource.com/article/20/7/systemd-timers?utm_medium=Email&utm_campaign=weekly&sc_cid=7013a000002glehAAA> 
 +</WRAP>
  
  
 +
 +====== Graphic Cards ======
 +
 +
 +<WRAP center round box >
 +2019-01-27
 +
 +openSUSE Graphic Card Practical Theory Guide for Users
 +
 +Look for occurrences of:
 +(==) NOUVEAU(0):
 +which would indicate open source NOUVEAU driver in use.The following command may work (note syntax/spaces) to confirm this driver:
 +Code:
 +cat /var/log/Xorg.0.log | grep '('II')'' 'NOUVEAU
 +
 +From: <https://forums.opensuse.org/showthread.php/430150-openSUSE-Graphic-Card-Practical-Theory-Guide-for-Users?p=2157771#post2157771> 
 +
 +</WRAP>
  
software/linux/opensuse.txt · Last modified: 2021/03/05 18:28 by superwizard