Ladies and gents,
please go easy on me, this is my first post. I have just come in to contact with Puppy for the first time last week and I can only describe myself as a Linux novice.
So far I have successfully managed to get my NIC's working and ethereal up and running. I know this question is extremely biased towards networking (unfortunately I'm a network engineer). Ethereal is working as expected, but I am unable to see 802.1q tag information within ethereal. Does anyone know how puppy treats the network stack, does it strip the 802.1q header out of the L2 headers prior to passing the frame on, or is the issue down to the NIC. Any assistance would be appreciated. Apologies for the non-specific puppy question
regards
Unable to see 802.1q tags in Ethereal
Flash, thanks for that, not actually used wireshark yet, but I do know of it's existance.
Béèm, of course you are right, I'll try and explain here.
The problem was nothing to do with the way Puppy handled the TCP stack or stripping of information in software. It was actually a hardware related issue. Some NIC's strip the 802.1q header and place it in registers which drivers can then access (should they have the ability) as opposed to letting the driver deal with the header directly (my understanding). This can, on some cards, be circumvented with alterations to drivers (or regsitry in windows).
If you do experience this problem, firstly try a different card, to ensure your NIC isn't preforming as aforementioned. If this isn't an option, occassionally special drivers can be located, possibly on your NIC manufacturers website.
Not a great solution but hopefully of some use
Béèm, of course you are right, I'll try and explain here.
The problem was nothing to do with the way Puppy handled the TCP stack or stripping of information in software. It was actually a hardware related issue. Some NIC's strip the 802.1q header and place it in registers which drivers can then access (should they have the ability) as opposed to letting the driver deal with the header directly (my understanding). This can, on some cards, be circumvented with alterations to drivers (or regsitry in windows).
If you do experience this problem, firstly try a different card, to ensure your NIC isn't preforming as aforementioned. If this isn't an option, occassionally special drivers can be located, possibly on your NIC manufacturers website.
Not a great solution but hopefully of some use