Re: 802.1p only?
"Xin Huang" <[email protected]> Fri, 14 Dec 2007 16:36:40 -0800
| Newsgroups | gmane.linux.drivers.vlan |
|---|---|
| Message-ID | <[email protected]> |
--===============0931075914== Content-Type: multipart/alternative; boundary="----=_Part_2985_1875561.1197679000132" ------=_Part_2985_1875561.1197679000132 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks again for the response. >> So this is the problem. And there is nothing Linux can do about this. >> I would investigate if the switch that you are using can indeed be used the way you want. I was thinking it's a problem on the switch too. But after spending some time to read the standard, it appears to me that the switch was doing everything right. If you think it's wrong, please clarify what should the "DHCP offer" packet look like. There was a similar discussion in this forum two years ago: http://www.candelatech.com/pipermail/vlan/2005-February/000241.html As Ben Greear said in the above page: "I don't think VLAN-0 is going to work, and at the very least, you cannot use .1p w/out using .1q as the headers are one and the same." Is the above conclusion still true? If yes, is there any plan to make 802.1pwork without using 802.1q on Linux? On Dec 14, 2007 2:11 PM, Peter Stuge <[email protected]> wrote: > On Thu, Dec 13, 2007 at 02:47:06PM -0800, Xin Huang wrote: > > Thanks for the answer. The switch is the DHCP server. > > Ok. > > > > But that's not the problem. > > Seems to me that it is. > > > > 1. "DHCP Request" is sent out from "eth0.0" of a Linux box. It's a > > VLAN tagged packet with VID set to 0. > > Fine so far. > > > > 2. "DHCP Offer" is sent back from the switch and received by Linux. > > It's a regular Ethernet packet without any VLAN tag. > > So this is the problem. And there is nothing Linux can do about this. > > > I would investigate if the switch that you are using can indeed be > used the way you want. > > > //Peter > _______________________________________________ > Vlan mailing list > [email protected] > http://www.candelatech.com/mailman/listinfo/vlan > ------=_Part_2985_1875561.1197679000132 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks again for the response.<br><br>>> So this is the problem. And there is nothing Linux can do about this.<br>>> I would investigate if the switch that you are using can indeed be<br>used the way you want.<br> <br>I was thinking it's a problem on the switch too. But after spending some time to read the standard, it appears to me that the switch was doing everything right. If you think it's wrong, please clarify what should the "DHCP offer" packet look like. <br><br>There was a similar discussion in this forum two years ago:<br><br><a href="http://www.candelatech.com/pipermail/vlan/2005-February/000241.html">http://www.candelatech.com/pipermail/vlan/2005-February/000241.html</a> <br><br>As Ben Greear said in the above page: "I don't think VLAN-0 is going to work, and at the very least, you cannot use .1p w/out using .1q as the headers are one and the same."<br><br>Is the above conclusion still true? If yes, is there any plan to make 802.1p work without using 802.1q on Linux?<br><br><div class="gmail_quote">On Dec 14, 2007 2:11 PM, Peter Stuge <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Thu, Dec 13, 2007 at 02:47:06PM -0800, Xin Huang wrote:<br>> Thanks for the answer. The switch is the DHCP server.<br><br></div>Ok.<br><div class="Ih2E3d"><br><br>> But that's not the problem. <br><br></div>Seems to me that it is.<br><div class="Ih2E3d"><br><br>> 1. "DHCP Request" is sent out from "eth0.0" of a Linux box. It's a<br>> VLAN tagged packet with VID set to 0.<br><br></div> Fine so far.<br><div class="Ih2E3d"><br><br>> 2. "DHCP Offer" is sent back from the switch and received by Linux.<br>> It's a regular Ethernet packet without any VLAN tag.<br><br></div>So this is the problem. And there is nothing Linux can do about this. <br><br><br>I would investigate if the switch that you are using can indeed be<br>used the way you want.<br><div><div></div><div class="Wj3C7c"><br><br>//Peter<br>_______________________________________________<br>Vlan mailing list <br><a href="mailto:[email protected]">[email protected]</a><br><a href="http://www.candelatech.com/mailman/listinfo/vlan" target="_blank">http://www.candelatech.com/mailman/listinfo/vlan</a><br></div></div></blockquote> </div><br> ------=_Part_2985_1875561.1197679000132-- --===============0931075914== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Vlan mailing list [email protected] http://www.candelatech.com/mailman/listinfo/vlan --===============0931075914==--