Results 1 to 7 of 7

Thread: SHOWEQ not working on this newwork

  1. #1
    Registered User
    Join Date
    Feb 2002
    Posts
    36

    SHOWEQ not working on this newwork

    I had my linux box on network 1 and it was decoding
    I switched the box over to my other DSL network and not its not working
    I did switch all the network info to match my second network

    Only difference is that on network 1 my nailed IP's were in seq order

    xxx.xxx.xxx.24
    xxx.xxx.xxx.25
    xxx.xxx.xxx.26

    extc....

    but on this network my address's jump from
    xxx.xxx.xxx.4 to
    xxx.xxx.xxx.29

    the hub is a stright 8 port with no switching
    and I can ping both machine from the net
    Any ideas

  2. #2
    Registered User
    Join Date
    Feb 2002
    Posts
    62
    Is the IP address to monitor in SEQ hard coded? If that's not the problem you can verify that your SEQ box is "seeing" all the network traffic by running the system monitor network option (at least that's what it's called on RH8). If the SEQ box is able to see the traffic (i.e. problem isn't a hub that's really a switch) you will see activity on the network monitor gauge while EQ is running, regardless of whether SEQ is running or not.

    mudtoe

  3. #3
    Registered User Lyroschen's Avatar
    Join Date
    Jan 2003
    Posts
    101
    Aye, there are a couple ways to test to see if you can see packets on the wire, in general. I've noticed that several (especially Linksys) hubs will do some level of switching, even though it's not listed as a switch. If it's possible borrow the hub from your functional configuration, and test it on your DSL connected network to see if it makes a difference.
    A lesson on time travel will be held yesterday.

  4. #4
    Registered User
    Join Date
    Oct 2002
    Posts
    235
    find / -type f -print0 | xargs -0 grep -l xxx.xxx.xxx.24

    Run this for .24, .25, and .26.

    Examine any files that appear.

    Also run "tcpdump -i eth0 -n" to make sure you see the IP addresses of the other machines appearing.

  5. #5
    Registered User
    Join Date
    Feb 2002
    Posts
    36
    running
    Also run "tcpdump -i eth0 -n" to make sure you see the IP addresses of the other machines appearing.

    does show packets with IP address's of xxx.xxx.xxx.4 thats
    tha machine that EQ is run on, xxx.xxx.xxx.29 is the linux box

  6. #6
    Registered User
    Join Date
    Feb 2002
    Posts
    36
    under Network Diagnostics
    under
    Network Client it indicates correct IP adress and there is packet activity.
    Only zone-client packets are updating
    odd ok its works now seesm I had to zone to get it to regester
    the map and data

  7. #7
    Registered User
    Join Date
    Dec 2001
    Posts
    152
    Yes, if you start SEQ while EQ is running, you WILL need to zone for it to get zone info, this is normal.

    SEQ does NOT pull it from memory, and it's sent when you zone into a zone, then updated as time goes.
    --------
    - Catt

    >SELECT * FROM users WHERE clue > 0;
    0 rows returned
    /em sigh

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 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