It is August 2015. Unfortunately it is still not possible to manually specify the MTU to be used on non-Ethernet NetworkManager connections (eg. VPN connections but also PPP).
Not that is has not been requested years ago. Choose one of the many bug reports:
Safe for the fact that they’re partially redundant reports, just imagine what would have happened if the devs had simply provided a MTU field for every connection type, empty by default but allowing to explicitly configure one. But no, that would have confused users *rolleyes*
Enough ranting, for VPN connections the workaround remains. Create a script /etc/NetworkManager/dispatcher.d/vpn-up:
if [ "$2" = "vpn-up" ]; then
/sbin/ifconfig "$1" mtu 1392
Still thinking that it’s sufficient to backup /home before your next distribution upgrade/reinstall? Good luck…
On recent SUSE-based distributions such as openSUSE Tumbleweed (and potentially also 13.2), executing iw reg get to check your WiFi device’s regulatory setup will likely get you an output such as this:
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 40), (N/A, 20), (N/A), NO-IR
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, NO-IR
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, NO-IR
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, NO-IR
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR
(5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
Continue reading “Fixing wireless regulatory support (crda, wireless-regdb) on openSUSE Tumbleweed”
Like many current devices with HDMI output, my Latitude E7450 offers multiple sound cards but configures the HDMI output as sound card 0 (the default). And xfce’s default sound mixer doesn’t offer switching the default output…
To correct the soundcard order, add this to your /etc/modprobe.d/50-sound.conf (valid for openSUSE 13.2, probably other distros as well):
options snd-hda-intel id=PCH index=0
options snd-hda-intel id=HDMI index=1
This post is about getting the LTE card to work that gets built into current Dell Notebooks such as the Latitude E5450/E7450:
Continue reading “Dell Wireless 5809e support in openSUSE 13.2”
Quite simple actually:
# sudo zypper ar -f http://download.opensuse.org/repositories/X11:/xfce/openSUSE_13.2/ XFCE_13.2
# sudo zypper dup --from XFCE_13.2
python-netsnmpagent version 0.5.1 has just been released.
This release has no substantial new features but a number of fixes of which the following three are important enough to warrant an update from 0.5.0:
- netsnmpagent: Make Table’s value() method regard string lengths
- netsnmpagent: Drop special string handling in Table’s init()/setRowCell()
- netsnmpagent: Fix Table’s value() cutting off ASN_COUNTER64 table values
Other changes include:
- Usage of MIB files is now completely optional
- threading_agent got a small fix so it works on Python 2.6, too
- __version__ got removed, use pkg_resources in your agent yourself to express version dependencies as outlined in 5715e77f’s commit message.
See the included ChangeLog for a detailed list of all changes
Ways to get the software:
- As usual, the source is available at the GitHub repo.
- The source distribution .tar.gz for this release can be downloaded from the PyPI page.
- You can either build binary RPMs for your local distribution yourself (download and make rpms) or pick them up from my Open Build service project — just click on the Repositories tab and one of the Go to download repository links.
I have just pushed two fixes that should be of interest to all python-netsnmpagent users:
These changes fix the issue with trailing dots in table strings. I’ve so far only pushed them to master. I’d like to get some feedback before pushing these to the 0.5 stable branch, so please check them out :)
libvirt supports the concept of so-called channels that represent private communication channels between a libvirt guest and its host.
Continue reading “Enabling libvirt channels by adding virtio_console to the openSUSE installation”
Recently I’ve been working a lot with the SilverStripe CMS/framework written in PHP (as one could undoubtedly deduce from my earlier post). The context involved porting a custom application from SilverStripe 2.4 to 3.1. Naturally this also involved dealing with the formerly used DataObjectManager module and 3.x’s new ORM and GridField components.
Continue reading “Moving from DataObjectManager – GridFieldRecordEditor, GridFieldRelationEditor and usability issues”