Re: 802.1p only?
"Xin Huang" <[email protected]> Thu, 13 Dec 2007 14:47:06 -0800
| Newsgroups | gmane.linux.drivers.vlan |
|---|---|
| Message-ID | <[email protected]> |
--===============0965605628== Content-Type: multipart/alternative; boundary="----=_Part_25619_30332453.1197586026140" ------=_Part_25619_30332453.1197586026140 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks for the answer. The switch is the DHCP server. But that's not the problem. The packet sniffer trace shows: 1. "DHCP Request" is sent out from "eth0.0" of a Linux box. It's a VLAN tagged packet with VID set to 0. 2. "DHCP Offer" is sent back from the switch and received by Linux. It's a regular Ethernet packet without any VLAN tag. Since not tagged, it is sent to interface "eth0" instead of "eth0.0". Then the packet gets dropped by "eth0" because the DHCP client is started on "eth0.0". I don't think it's a configuration problem on the switch or DHCP server. Please correct me if my assumption is wrong. But if it's a configuration problem on Linux, I'd be happy to know what I should do. On Dec 13, 2007 12:00 PM, <[email protected]> wrote: > > Date: Thu, 13 Dec 2007 01:58:45 +0100 > From: Peter Stuge <[email protected]> > Subject: Re: [VLAN] 802.1p only? > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > On Wed, Dec 12, 2007 at 02:37:16PM -0800, Xin Huang wrote: > > Here is the problem: when a DHCP request is sent out of eth0.0, the > > switch sends back a DHCP offer packet without any VLAN header. > > So your switch is the DHCP server? > > This all seems like a configuration issue. > > > > But is there a simple way to make DHCP client work on eth0.0? > > You wrote above that your DHCP client is already communicating over > eth0.0. If in fact it is not, this would be rather simple, depending > on your client software: > > dhcpcd eth0.0 > dhclient eth0.0 > pump -i eth0.0 > > etc. > > > //Peter > > > ------------------------------ > > _______________________________________________ > Vlan mailing list > [email protected] > http://www.candelatech.com/mailman/listinfo/vlan > > > End of Vlan Digest, Vol 34, Issue 1 > *********************************** > ------=_Part_25619_30332453.1197586026140 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks for the answer. The switch is the DHCP server. But that's not the problem. The packet sniffer trace shows:<br><br>1. "DHCP Request" is sent out from "eth0.0" of a Linux box. It's a VLAN tagged packet with VID set to 0. <br>2. "DHCP Offer" is sent back from the switch and received by Linux. It's a regular Ethernet packet without any VLAN tag. Since not tagged, it is sent to interface "eth0" instead of "eth0.0 ". Then the packet gets dropped by "eth0" because the DHCP client is started on "eth0.0".<br><br>I don't think it's a configuration problem on the switch or DHCP server. Please correct me if my assumption is wrong. <br><br>But if it's a configuration problem on Linux, I'd be happy to know what I should do.<br><br><div class="gmail_quote">On Dec 13, 2007 12:00 PM, <<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;"><br>Date: Thu, 13 Dec 2007 01:58:45 +0100<br>From: Peter Stuge <<a href="mailto:[email protected]"> [email protected]</a>><br>Subject: Re: [VLAN] 802.1p only?<br>To: <a href="mailto:[email protected]">[email protected]</a><br>Message-ID: <<a href="mailto:[email protected]">[email protected] </a>><br>Content-Type: text/plain; charset=us-ascii<br><br>On Wed, Dec 12, 2007 at 02:37:16PM -0800, Xin Huang wrote:<br>> Here is the problem: when a DHCP request is sent out of eth0.0, the<br>> switch sends back a DHCP offer packet without any VLAN header. <br><br>So your switch is the DHCP server?<br><br>This all seems like a configuration issue.<br><br><br>> But is there a simple way to make DHCP client work on eth0.0?<br><br>You wrote above that your DHCP client is already communicating over <br>eth0.0. If in fact it is not, this would be rather simple, depending<br>on your client software:<br><br>dhcpcd eth0.0<br>dhclient eth0.0<br>pump -i eth0.0<br><br>etc.<br><br><br>//Peter<br><br><br>------------------------------ <br><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><br><br>End of Vlan Digest, Vol 34, Issue 1<br>***********************************<br></blockquote></div><br> ------=_Part_25619_30332453.1197586026140-- --===============0965605628== 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 --===============0965605628==--