Results 1 to 2 of 2

Thread: SEQ not listening?

  1. #1
    Registered User
    Join Date
    Jun 2024
    Posts
    4

    Question SEQ not listening?

    So I got it working a while ago on VMware, thanks to y'all...but the hypervisor layer added a lot of lag on the UI. I've since moved to a new setup, which I'm having issues with:

    • OpenWRT w/port-mirroring
    • Raspberry-Pi 5 running SEQ


    I'm trying to debug the port-mirroring, I think I have it setup right, now I suspect that SEQ is not listening:

    Code:
    root@eyes:~# netstat -pant | grep LISTEN
    tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      782/cupsd
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      889/sshd: /usr/sbin
    tcp        0      0 127.0.0.1:6011          0.0.0.0:*               LISTEN      12093/sshd: root@pt
    tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      11062/sshd: root@pt
    tcp6       0      0 ::1:631                 :::*                    LISTEN      782/cupsd
    tcp6       0      0 ::1:6011                :::*                    LISTEN      12093/sshd: root@pt
    tcp6       0      0 ::1:6010                :::*                    LISTEN      11062/sshd: root@pt
    tcp6       0      0 :::22                   :::*                    LISTEN      889/sshd: /usr/sbin
    I would expect SEQ proc to list there, with the port (5555?)?

    Startup looks clean to me:
    Code:
    root@eyes:~# showeq -i eth0 --ip-address=192.168.1.122
    ShowEQ 6.3.15, released under the GPL.
      SINS 0.5, released under the GPL.
    All ShowEQ source code is Copyright (C) 2000-2019 by the respective ShowEQ Developers
    ShowEQ comes with NO WARRANTY.
    
    You may redistribute copies of ShowEQ under the terms of
    The GNU General Public License.
    See: http://www.gnu.org/copyleft/gpl.html for more details...
    
    For updates and information, please visit http://seq.sourceforge.net/
    ShowEQ 6.3.15, Built from 'main.cpp' on Jul 11 2024 at 01:06:17
            CVS: @(#) $Id: main.cpp 1279 2022-10-20 00:33:52Z cn187 $ $Name$
                    Using GCC version: 12.2.0
                    Using glibc version: 2.36
                    Using Qt version: 5.15.8
            Running on Linux release 6.6.31+rpt-rpi-v8 for processor aarch64
    
    Using config file '/root/.showeq/showeq.xml'
    Loaded preferences file: /usr/local/share/showeq/seqdef.xml!
    Unable to open file: /root/.showeq/showeq.xml!
    Info: Listening for client: 192.168.1.122
    Info: Initializing Packet Capture Thread:
    Info: Filtering packets on device eth0, IP host 192.168.1.122
    Warning: Spells: Failed to open: '/usr/local/share/showeq/spells_us.txt'
    Warning: GuildMgr: Could not load guildsfile, /root/.showeq/tmp/guilds3.dat
    Info: Loading Filters from ''
    QFSFileEngine::open: No file name specified
    Info: Loading Zone Filter File:
    QFSFileEngine::open: No file name specified
    Info: Loading Zone Filter File:
    QFSFileEngine::open: No file name specified
    Info: Categories Reloaded
    Info: No Map found for zone 'unknown'!
    Info:     Checked for all variants of 'unknown.map', 'unknown.txt', and 'unknown_1.txt'
    Info:     in directories '/root/.showeq/maps' and '/usr/local/share/showeq/maps'!
    Warning: Could not restore dock/window geometry.  Rearrange windows as desired and then re-save preferences
    Warning: Could not restore dock/window state.  Rearrange windows as desired and then re-save prefrences
    Warning: EQStr: Failed to open '/usr/local/share/showeq/eqstr_us.txt'
    Last edited by n2099; 07-11-2024 at 09:35 AM.

  2. #2
    Administrator
    Join Date
    Oct 2019
    Posts
    548

    Re: SEQ not listening?

    Quote Originally Posted by n2099 View Post
    I would expect SEQ proc to list there, with the port (5555?)?
    Nope, SEQ works differently than MySEQ - there's no socket involved. SEQ captures the packets directly from the ethernet interface (in your case, eth0).

    As long as you're getting EQ traffic on eth0 (via port mirroring or otherwise) then that's all you need.

Thread Information

Users Browsing this Thread

There are currently 3 users browsing this thread. (0 members and 3 guests)

Posting Permissions

You may post new threads
You may post replies
You may post attachments
You may edit your posts
HTML code is Off
vB code is On
Smilies are On
[IMG] code is On