SEQ Not showing anything

[Mil]

It compiled fine (RH 7.2), runs fine, just isn't showing anything. tcpdump shows the packets. Anyone have any ideas?

TIA

[high_jeeves]

There are many other threads about this... You need to give us ALOT more information before we can fully help you..

Here are a few of the more likely causes:

1) Switched/Mutli-Speed environment
2) PPOE
3) Incorrect Network Topology
4) Not running as root

--Jeeves

[Mil]

Will be happy to supply any info you ask for :)

1) Plain hub (3Com OfficeConnect)
2) PPOE??
3) Network topology is fine, and simple(multiple machines connected to hub, router connected to hub, no NAT, etc)
4) I am running as root :)


TIA

[high_jeeves]

PP-Over-Ethernet... Some DSL service requires it... do you have to install any special software on your Windows Machines in order to access your service? It changes the structure of the packets, so ShowEQ wont work.. Same goes for VPN/Tunneling software, etc...

Do you have the IP address set corectly?
Is the packet counter in the lower right of the SEQ window incrementing?
Are you sure the traffic you are seeing in tcpdump is the EQ traffic, and not just broadcast ARP traffic?

--Jeeves

[Mil]

Nope, no special software. Straight TCP/IP stacks. Also no VPN, no tunneling.

Here is a short tcp dump excerpt(grep'ed for relevant packets):


14:34:45.158476 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 22
14:34:45.163713 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 135
14:34:45.209478 ws1.tknetworks.com.1923 > eqzone-75-10.989studios.com.3409: udp 10
14:34:45.320142 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 23
14:34:45.719033 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:45.774382 ws1.tknetworks.com.1923 > eqzone-75-10.989studios.com.3409: udp 10
14:34:46.018063 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:46.020776 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:46.175762 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:46.178677 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:46.252844 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 30
14:34:46.330990 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:46.410279 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 23
14:34:46.414241 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 23
14:34:46.415684 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 20
14:34:46.469119 ws1.tknetworks.com.1923 > eqzone-75-10.989studios.com.3409: udp 10
14:34:46.485935 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:47.280767 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 22
14:34:47.283687 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:47.334088 ws1.tknetworks.com.1923 > eqzone-75-10.989studios.com.3409: udp 10
14:34:47.349996 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 90
14:34:47.893036 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:48.442962 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 150
14:34:48.596137 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26
14:34:48.673966 eqzone-75-10.989studios.com.3409 > ws1.tknetworks.com.1923: udp 26

[high_jeeves]

Looks like you are getting packets... this is probably either a configuration problem on your SEQ install, or something is mucking up your packets... you running any sort of proxy, or caching server?

--Jeeves

[Mil]

Nope, no proxy, no caching server. This same setup worked fine with the older version of SEQ until I was forced to upgrade because of the last patch.

I have noticed a couple of interesting things though. If I use -N or open the Network diagnostics window in SEQ, it doesn't seem to be getting the proper IP address from the command line. It initially shows 127.0.0.1 under Nework Client, and eth0 as the device. It does show the packets total incrementing though. If I go to Network/IP Address and set the IP manually, the packets total stops incrementing.

Really strange for it to be showing packets on a loopback address.

EDIT: My goof, it's showing 127.0.0.0 initially under Network Client

[Mil]

In fact, even if I change the IP back to 127.0.0.0 via the menus, the Total Packets doesn't continue incrementing. Could it possibly be not getting the IP on the command line, and the in-program change freezes the capture thread?

[lane]

I think you're refering to PPPoE. Point-to-Point Protocol over Ethernet.

DSL and sometimes cable providers use it so they can authenticate the customers (ask them a password), since there is no inherent authentication in either of those technologies.

-Lane

[high_jeeves]

PPOE = PPPOE, depends on which vendor you use... :)

The command like has changed for setting the IP address recently.. try:

./showeq eth0 --ip-address=<whatever>

see if that helps..

--Jeeves

[Mil]

That worked like a charm. Thanks much :)