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
In article <[email protected]>,
Teodor Iacob <[email protected]> wrote:
>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 ).
Did you patch the ethernet driver so that it supports the bigger
MTUs needed for VLAN support ? It's all described in the VLAN patch docs.
Mike.
--
Computers are useless, they only give answers. --Pablo Picasso
On Fri, 22 Feb 2002, Miquel van Smoorenburg wrote:
> In article <[email protected]>,
> Teodor Iacob <[email protected]> wrote:
> >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 ).
>
> Did you patch the ethernet driver so that it supports the bigger
> MTUs needed for VLAN support ? It's all described in the VLAN patch docs.
Is there any drawback to use this patch? :
In const char i82557_config_cmd[22] = {
- 0x68, 0, 0x40, 0xf2, 0xBD, /* 0xBD->0xFD=Force
full-duplex */
+ 0x68, 0, 0x40, 0xfa, 0xBD, /* 0xBD->0xFD=Force
full-duplex */
I use the other 2 interfaces in normal mode and they are eepro100 too,
only one uses 2 tagged subinterfaces.
Btw, I was able to reconfigure the whole thing and it does work fine now,
but I can't really make a test now with the other two interfaces since I
did all this remotely.
>
> Mike.
> --
> Computers are useless, they only give answers. --Pablo Picasso
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Sat, 23 Feb 2002, Teodor Iacob wrote:
> > Did you patch the ethernet driver so that it supports the bigger
> > MTUs needed for VLAN support ? It's all described in the VLAN patch docs.
>
> Is there any drawback to use this patch? :
> In const char i82557_config_cmd[22] = {
> - 0x68, 0, 0x40, 0xf2, 0xBD, /* 0xBD->0xFD=Force
> full-duplex */
> + 0x68, 0, 0x40, 0xfa, 0xBD, /* 0xBD->0xFD=Force
> full-duplex */
>
AFAIK you have to change 2 values in this section: the second and third
occurences of 0xf2 to 0xfa.
endre