mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Teodor Iacob <theo@astral.kappa.ro>
To: <linux-kernel@vger.kernel.org>
Subject: Problem? 802.1q kernel 2.4.18-rc1-rmap12f
Date: Fri, 22 Feb 2002 18:24:33 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.31.0202221815590.28962-100000@linux.kappa.ro> (raw)

Hello,

I shall describe the hardware involved and the layout first:
A PC router i815 Motherboard, 3 Intel Etherexpress PRO 100 82557
Allied Telesyn AT-8224XL 802.1q capable.

Software: Slackware 8.0, kernel 2.4.18-rc1-rmap12f.

I want to use the eth0 as 2 subinterfaces with 802.1q with vlan IDs 3 and
5, so this is how I set the whole thing up:

/sbin/ifconfig eth0 up # This to make the link of the interface up
vconfig add eth0 5
vconfig add eth0 3

/sbin/ifconfig eth0.5 inet ..etc..
/sbin/ifconfig eth0.3 inet ...etc..

and I have also the default gateway through the eth0.5 vlan.

Now after a fresh start, I can ping whatever I want, but I cannot start a
file transfer, it just locks up after first 1024 bytes ( as seen with tick
in simple ftp command ).

If I change the startup scripts and ofc the aty switch to not use tagging
on the interface and use simple eth0 the transfer is ok. Now I get the
vlan back and the transfer works, but if I restore the configurations and
reboot the machine I cannot make transfers. I was able to ping -s 1400
stations through this 802.1q, but I didn't test further up (1467
or more ..etc.).

Does anybody can help me track this thing? Could this be kernel related?


Respectfully,
Teodor Iacob




             reply	other threads:[~2002-02-22 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 16:24 Teodor Iacob [this message]
2002-02-22 16:43 ` Miquel van Smoorenburg
2002-02-22 22:05   ` Teodor Iacob
2002-02-23 21:41     ` endre

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=Pine.LNX.4.31.0202221815590.28962-100000@linux.kappa.ro \
    --to=theo@astral.kappa.ro \
    --cc=Teodor.Iacob@astral.kappa.ro \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®