Network Troubleshooting(no client detected)

[jerenn]

Running latest version of debian - everything updated

fresh CVS of newest release of showeq

using Linksys BEFW11S4 Wireless B router

to that I have hooked up a netgear EN 104TP hub (it has worked for me in the past with mandrake 9.1)

port setup is as follows:

port 1 from router to port 1 of hub (uplink button is not pressed in)

showeq box is on port 2 of hub

machine running eq on port 3 of hub

laptop that sometimes runs eq on port 4 of hub

or: (for those that like a diagram) (if this comes out crappy - i appologize)

internet---[Linksys BEFW11S4 router]---[netgear EN104tp]|-----1.cable from router---2.Linuxbox---3.everquest---4.Laptop

With showeq fired up, I logon a toon - does not detect a client. Filtering by IP obviously no help either *shrug*

I have ruled out cabling as I've replaced all cables involved.

Router has been reset to default a million times - there is no port forwarding except for 6999 - 7001 for irc and 60001 to 60002 for bittorrent.

I've replaced the nic in the linux box a few times with no avail (swapped a d-link for a d-link, now I have an older nic that I forgot who made it) again , *should* be irrelevent since I've had showeq running before with this configuration.


I have also changed positions of all machines on the hub (ie linux box on port 3, etc)

I've also played with nic speeds (ie changing from full duplex to half - yadda) since some thread on here said that might be a factor - no avail there. (I think it was determined that that really matters squat later on)

I scour these boards each time I get the gumption to try to get showeq running again - its frustrating not seeing it pickup when I know I've had it working in the past. Any ideas as to what I might have missed would be greatly appreciated.

[purple]

That's pretty close to my setup, except I have my uplink button pressed and I have my seq box into the hub and a switch into the hub, then the switch has various computers on it, any of which I can run eq on and seq will pick it up.

What are the speeds on your nics? Are they all 10 or 100 or 1000, is it a mix of each? The hub may separate by speed.

[tanner]

I scour these boards each time I get the gumption to try to get showeq running again - its frustrating not seeing it pickup when I know I've had it working in the past. Any ideas as to what I might have missed would be greatly appreciated.

Can any of the machine running EQ ping the Linux system?

Can the linux system ping any of the machine playing EQ?

Can you apt-get install mii-diag, as root post the output of mii-diag here?

# mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #24: 3000 782d 0041 6800 05e1 0021 0004 2001.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner is generating 10baseT link beat (no autonegotiation).
End of basic transceiver information.

You are running showeq on the linux box as root?

[jerenn]

Can any of the machine running EQ ping the Linux system?

Can the linux system ping any of the machine playing EQ?

Can you apt-get install mii-diag, as root post the output of mii-diag here?

You are running showeq on the linux box as root?
1. linux box is 192.168.1.104 via DHCP able to ping it ok from the machine I'm typing on (192.168.1.101) linuxbox can ping out to all windows machines ok as well.

2. this is what I get when using mii-tool"

linuxnode:~# mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #32: 0100 780d 0000 0000 01e1 0000 0000 0000.
Basic mode control register 0x0100: Auto-negotiation disabled, with
Speed fixed at 10 mbps, full-duplex.
You have link beat, and everything is working OK.
Link partner information is not exchanged when in fixed speed mode.
End of basic transceiver information.


I changed the windows machine to 10 base full as well - rebooted with still no luck. I also used ethtool to change eth0 from 10 full to half and back again with no success.

3. As root, correct.

[Freakyuno]

Is there more than one nic in the linux box? When I used debian, I had to start SEQ with the --eth0 switch to force it to listen on the correct interface.

[Cryonic]

Uh... it is full duplex...
you can't do that on a true hub
You have a switch...

[jerenn]

No, there is only 1 nic on the linuxbox.

I have every machine set to 10 base half duplex with still, no luck.


Uh... it is full duplex...
you can't do that on a true hub
You have a switch... eh? I forced the nic to be full duplex and disabled autodetect too. This ole netgear has worked for me before... dunno how it could if it was a switch..

*keeps plugging away*

[purple]

Hit the uplink button? I don't know what it does, but I have it on on my NetGear DS104.

[jerenn]

yeah the uplink button got a workout, still nothing.

I saw some references to making a gateway out of the linux box - it's a bit outside my expertise. how easy / hard would it be ?


1. slap in extra nic..

what would be next ? *scours search some more*

[purple]

You really shouldn't need to though. It really sounds like what you have should work.

Is there pppoe or something going on? I don't use wireless at all. Is there any encapsulation that happens because of it? Are all your machines on the same subnet, pointing to the right gateway, and the netmask of your linux box is set correctly? Wht does the output of "route" show? If you just do tcpdump from the command line on your linux box, do you see traffic from you other machine(s)?

[jerenn]

Quick snippet of what tcpdump picks up:


21:15:15.101791 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 110
21:15:15.290615 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 148
21:15:15.454997 IP 192.168.1.100.1533 > eqzone-158-09.everquest.com.1421: UDP, length: 7
21:15:15.669429 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 131
21:15:15.858200 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 47
21:15:16.121996 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 127
21:15:16.295908 IP 192.168.1.100.1533 > eqzone-158-09.everquest.com.1421: UDP, length: 7
21:15:16.353433 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 110
21:15:16.598271 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 89
21:15:16.817048 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 68
21:15:17.131806 IP eqzone-158-09.everquest.com.1421 > 192.168.1.100.1533: UDP, length: 89

3812 packets captured
3812 packets received by filter
0 packets dropped by kernel
so its seeing everything going on, it just won't pickup.


route shows:



linuxnode:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
linksys router ip addresse is 192.168.1.1 router is set to obtain ip from cable modem automatically. all of the other machines are setup via DHCP for addresssing.

now with route.. shouldn't it be gunning for 192.168.1.1 and not 192.168.1.0 ? tho I think 1.0 is the beginning of that whole subnet so it should be fine. weeeeeird

[purple]

All that looks fine to me. Seq should work.

192.168.1.0 is just the network. It's ok.

[jerenn]

Hmm.. been playing with cables and order of machines on the hub for the past 2 hours with no luck :( wow this is sucking big time heh.

I've experimented with the different options when running showeq, also to no avail

showeq -i --net-interface=eth0 192.168.1.100 works, but again picks up no client.

[purple]

Just do showeq. Don't specify anything at all. Go to Network->Monitor Next EQ Client seen, then zone with your everquest client.

[jerenn]

still nothing.

I'm currently trying to apt-get install showeq from the links that tanner provides on his site. Unable to connect to real-time.com - happen to know if they dissallow foreign ip addresses? currently residing overseas.

[I<3EQ]

What version of ShowEQ are you running? One that works against current eqlive?

EDIT: I just read you're living overseas, are you playing on an Ubisoft server? Also, you have zoned after starting ShowEQ, correct?

[jerenn]

playing on a regular US server - have zoned repeatedly (between qeynos and Plane of Knowledge) with seq running the whole time - no dice - tcpdump detects the packets - showeq just won't pick 'em up.

[purple]

Cut and paste what it says when you run showeq then hit Network->Monitor Next EQ Client Seen then zone with your EQ client.

[jerenn]

this is what I get:




linuxnode:~# showeq
Using config file '/usr/local/share/showeq/showeq.xml'
Loaded preferences file: /usr/local/share/showeq/seqdef.xml!
Unable to open file: /usr/local/share/showeq/showeq.xml!
ShowEQ 4.3.22, released under the GPL.
SINS 0.5, released under the GPL.
All ShowEQ source code is Copyright (C) 2000-2003 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 4.3.22, Built from 'main.cpp' on Apr 19 2005 at 02:06:28
CVS: $Id: main.cpp,v 1.33 2003/10/25 00:20:59 dohpaz Exp $
Using GCC version: 3.3.5
Using glibc version: 2.3
Using Qt version: 3.3.4
Using headers from linux version: 2.6.0-test7
Using EQItemDB: @(#) $Id: itemdb.cpp,v 1.10 2003/10/25 00:20:59 dohpaz Exp $
Using GDBM: GDBM version 1.8.3. 10/15/2002 (built Sep 9 2003 00:02:26)
Running on Linux release 2.4.27-2-386 for processor i686

Spells::Spells(): Failed to open: '/usr/local/share/showeq/spells_us.txt'
Listening for first client seen.
Initializing Packet Capture Thread:
Filtering packets on device eth0, searching for EQ client...
Loading filters from '/usr/local/share/showeq/filters.conf'
Loading Filter File: /usr/local/share/showeq/filters_unknown.conf
GuildMgr: WARNING - could not load guildsfile, /usr/local/share/showeq/guilds2.dat
Categories Reloaded
Error opening map file '/usr/local/share/showeq/unknown.map'!
EQInterface::loadFormatStrings(): Failed to open '/usr/local/share/showeq/eqstr_us.txt'
Listening for next client seen. (you must zone for this to work!)
Filtering packets on device eth0, searching for EQ client...
just waiting for something it looks like.

Someone mentioned this could be firewall related, but I don't think debian sets anything up by default. I checked iptables and when I tried to remove any rules that might have been there it said there were nothing. is iptables a requirement in running seq ? could uninstall it and see what happens if it isn't.. *shrug*

[purple]

ShowEQ 4.3.22, released under the GPL.

Current version is 5.0.0.20. Your version from 2003 doesn't work. I'm shocked!

[jerenn]

well damn, how long has cvs not worked ? I appologize for wasting your guys' time - thought cvs was constantly updated with the new stuff. guess not.


again, my appologies.

[purple]

It is, but on the pre_5_0_beta branch and not the trunk. Users shouldn't really use cvs unless they have to in order for things to work. Download the 5.0.0.20 tarball or get one of the package that Zaphod, Tanner, or CeleSEQ put together for whatever distribution you use.