i386/71045: DHCP-Request is sets other device's ip to null, when
using Realtek and Via-NICs
martin.piayda at udo.edu
Fri Aug 27 11:40:36 PDT 2004
>Synopsis: DHCP-Request is sets other device's ip to null, when using Realtek and Via-NICs
>Arrival-Date: Fri Aug 27 18:40:27 GMT 2004
>Originator: Martin Piayda
University of Dortmund
FreeBSD themis 5.2.1-RELEASE-p9 FreeBSD 5.2.1-RELEASE-p9
I noticed an annoying, but not serious matter, that occurs in combination with RealTek and Via Rhine based Network Interface Cards.
I own three NICs, a D-Link 530TX (Via Rhine), a D-Link 528TX (RealTek) and a SoHo-Ware-RealTek-Supermarket-Network-Card. :-)
So, let's come to the point:
When physically placing the cards in the order D-Link 530, D-Link 528, Cheap-RealTek and using the D-Link 530 as the DHCP-Hook for the Network-Gate the horror starts. The logical order, that ifconfig delivers is rl0 (D-Link 528), vr0 (D-Link 530) and rl1 (Cheapy).
The corresponding rc.conf sniplet is:
ifconfig_rl0="inet 10.0.0.1 netmask 255.255.255.0 broadcast 10.0.0.255"
ifconfig_rl1="inet 10.0.1.1 netmask 255.255.255.0 broadcast 10.0.1.255"
When booting, the vr0-card is DHCP-configured correctly, rl0 is left unconfigured (or overridden?) with the any-ip 0.0.0.0 and rl1 is set correctl (10.0.1.1).
After analysing and experimenting, I swapped the two D-Links physicalling and used rl0 as DHCP-Hook and vr0 for 10.0.0.1.
That fixed the Problem and all Network cards were happy including me.
Well, I can only assume, what the matter is, but at least it must be software-related.
I think the rl0-card, that was firstly configured get's confused by the "following" vr0 card in the ifconfig-row. I bet, if vr0 was first, it would be right.
This could be checked out, if some people were running similar scenarios where the first NIC, that ifconfig shows is statically configured and the second dynamically by DHCP.
I don't think it's me who caused the Problem and it's not really serious. I'm looking forward for the developer's analysis and explanation. :-)
More information about the freebsd-i386