• 6.9.0 beta1 syslog messages when vm and docker on br0

    alturismo

    By alturismo

      • Minor

    hi, 2nd approach to test the 6.9 beta 1 here, reboot ok, looking ok but what i see, my syslog is fillimg up with messages like this ...

    i remember that on my first try i had the same, syslog was filled up 100 % after a while, but as my win10 vm was broken afterwards i reverted to 683.

     

    following is coming up over and over

      

    Mar 16 06:15:50 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:50 AlsServer kernel: tun: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                  
Mar 16 06:15:50 AlsServer kernel: tun: 20 20 5c 0a 20 20 77 69 6c 64 63 61 72 64 3d 79    \.  wildcard=y
Mar 16 06:15:50 AlsServer kernel: tun: 65 73 20 20 20 20 20 20 20 20 20 20 20 20 20 20  es              
Mar 16 06:15:50 AlsServer kernel: tun: 20 20 20 20 20 20                                      
Mar 16 06:15:52 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:52 AlsServer kernel: tun: 8d 00 00 00 00 00 00 00 00 04 06 02 00 00 00 00  ................
Mar 16 06:15:52 AlsServer kernel: tun: 30 53 b2 00 00 00 00 00 70 53 b2 00 00 00 00 00  0S......pS......
Mar 16 06:15:52 AlsServer kernel: tun: 60 53 b2 00 00 00 00 00 b0 76 98 00 00 00 00 00  `S.......v......
Mar 16 06:15:52 AlsServer kernel: tun: 70 53 b2 00 00 00                                pS....
Mar 16 06:15:52 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:52 AlsServer kernel: tun: 67 00 00 00 00 00 00 00 3f 06 06 02 00 00 00 00  g.......?.......
Mar 16 06:15:52 AlsServer kernel: tun: e8 8a ad 00 00 00 00 00 b0 8a ad 00 00 00 00 00  ................
Mar 16 06:15:52 AlsServer kernel: tun: d8 8a ad 00 00 00 00 00 c0 10 ac 00 00 00 00 00  ................
Mar 16 06:15:52 AlsServer kernel: tun: 68 8a ad 00 00 00                                h.....
Mar 16 06:15:52 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:52 AlsServer kernel: tun: 67 00 00 00 00 00 00 00 3f 06 06 02 00 00 00 00  g.......?.......
Mar 16 06:15:52 AlsServer kernel: tun: e8 8a ad 00 00 00 00 00 b0 8a ad 00 00 00 00 00  ................
Mar 16 06:15:52 AlsServer kernel: tun: d8 8a ad 00 00 00 00 00 c0 10 ac 00 00 00 00 00  ................
Mar 16 06:15:52 AlsServer kernel: tun: 68 8a ad 00 00 00                                h.....
Mar 16 06:15:52 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:52 AlsServer kernel: tun: 00 00 00 00 00 00 00 00 60 40 4d 91 cd 14 00 00  ........`@M.....
Mar 16 06:15:52 AlsServer kernel: tun: 59 00 00 00 00 00 00 00 09 06 02 00 00 00 00 00  Y...............
Mar 16 06:15:52 AlsServer kernel: tun: 28 88 ad 00 00 00 00 00 c0 10 ac 00 00 00 00 00  (...............
Mar 16 06:15:52 AlsServer kernel: tun: b8 87 ad 00 00 00                                ......
Mar 16 06:15:52 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:52 AlsServer kernel: tun: 00 00 00 00 00 00 00 00 60 40 4d 91 cd 14 00 00  ........`@M.....
Mar 16 06:15:52 AlsServer kernel: tun: 59 00 00 00 00 00 00 00 09 06 02 00 00 00 00 00  Y...............
Mar 16 06:15:52 AlsServer kernel: tun: 28 88 ad 00 00 00 00 00 c0 10 ac 00 00 00 00 00  (...............
Mar 16 06:15:52 AlsServer kernel: tun: b8 87 ad 00 00 00                                ......
Mar 16 06:15:52 AlsServer kernel: tun: unexpected GSO type: 0x0, gso_size 1460, hdr_len 54
Mar 16 06:15:52 AlsServer kernel: tun: 03 ef f0 86 54 08 08 00 00 40 76 d9 06 1e 4b e8  [email protected].
Mar 16 06:15:52 AlsServer kernel: tun: 74 49 5b 19 d9 2d 91 cc ad a6 15 79 03 11 d2 71  tI[..-.....y...q
Mar 16 06:15:52 AlsServer kernel: tun: 37 4f a5 7c a2 4e 01 3f 96 b8 8d 98 a8 b6 b7 f1  7O.|.N.?........
Mar 16 06:15:52 AlsServer kernel: tun: 69 18 dd 9f 6f fa                                i...o.

    diagnostics attached

     

    after some research i see that if i turn the VM´s off using br0 the logs stop, so its (again) the issue with dockers and VM using the same br0 setup.

     

    as almost all my dockers are using sep ip´s on br0 ... is there a workaround for now ?

     

    i tried starting a VM with br1 but this couldnt get a network connection then ...

     

    here a snap from the network settings routing table

    image.png.f828286d1cfa6127e4e8c9272d036ad9.png

    may while im on it, anything i can delete here ? my routing mask at home is 192.168.1.0/24 only ...

     

    alsserver-diagnostics-20200316-0624.zip

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    bonienl
    29 minutes ago, alturismo said:

    ok, thanks for the info, so no workaround to get the VM´s use another custom br ... to bypass this behaviour

    The workaround is docker containers and VMs don't share the same netwerk interface (VLAN), but use separated interfaces (VLANs) instead.

     

    As said, it is a workaround but not the solution.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.