All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jacob Lear" <jlear@brammo.com>
To: 'Mail List - Netfilter' <netfilter@vger.kernel.org>
Subject: RE: Network Communication Issues
Date: Thu, 13 Dec 2007 10:41:41 -0800	[thread overview]
Message-ID: <004001c83db7$cd376bd0$fe02a8c0@brammo.main> (raw)
In-Reply-To: <47617846.5090101@riverviewtech.net>

 
> All references I see to "wrong data byte #30 should be 0x1e but was" 
> suggest wrong drivers for the NIC.  Any thoughts?

That's entirely possible. That NIC isn't one of the onboard NICs and was
just one that I had laying around. I don't even remember what it is. The
server is Red Hat EL4 x64 and the driver it is using is the one that it
picked: "ADMtek NC100 Network Everywhere Fast Ethernet 10/100". I have a
bunch of spare Linksys LNE100TX... I think it might be one of those. Is
there a Linux driver for that and is that the correct driver for it,
assuming that there is and that is what the card is?

> Ok...
> I'm not entirely sure that the blank gateway on the second NIC is not a
problem, though I don't think it is your current 
> problem.  I've had mixed results not putting a gateway in on all interface
config panels in Windows before.

I don't think that's the problem... based on what I've read online, Windows
doesn't like having more than 1 Default Gateway -- it confuses it (big
shocker there huh?). I tried it that way at first and it was complaining
when I tried to save the TCP/IP properties. I don't think the routing was
working right either... I seem to recall some issues.

 
Jacob Lear
IT Systems Support Engineer


  reply	other threads:[~2007-12-13 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 17:28 Network Communication Issues Jacob Lear
2007-12-13  0:42 ` Grant Taylor
2007-12-13 17:54   ` Jacob Lear
2007-12-13 18:21     ` Grant Taylor
2007-12-13 18:41       ` Jacob Lear [this message]
2007-12-14  8:23         ` Покотиленко Костик
2007-12-14  9:12           ` Eljas Alakulppi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004001c83db7$cd376bd0$fe02a8c0@brammo.main' \
    --to=jlear@brammo.com \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.