On Monday 16 August 2010 16:23, Roman Mashak wrote: > > Hello, > > Searching in mailing list and bugtrack unfirtunately didn't help to find any > useful information on the topic. > > I have an embedded platform running Linux 2.6 and busybox-1.7, where I > enabled DHCP relay feature, > recompiled and installed successfully. But the relay seems not to work as > expected; > below is the network map and interfaces: > > PC-----[vlan1 embedded device vlan2]-----DHCP-server-- > > Embedded device with two interfaces: > vlan1 192.168.2.10 LAN > vlan2 192.168.1.1 > DHCP server (192.168.1.150) is located on vlan2 segment. No dhcp daemon, > only DHCP relay on the device is being run as: > > # /usr/sbin/dhcprelay vlan1 vlan2 192.168.1.150 > > Windows PC runs DHCP client, sends query, and I capture traffic on vlan2, > but see no DHCP activity (though I believe the box should aat least send > one unicast with source IP 192.168.1.1 to destination 192.168.1.150).
Can you also capture traffic on vlan1? - # tcpdump -xX -s0 -nl -ivlan1 port 67 or port 68 2>&1 | tee LOG_vlan1 Can you strace dhcprelay so that we see what it does? - # strace -oLOG_strace -tt -s99 /usr/sbin/dhcprelay vlan1 vlan2 192.168.1.150 and post LOG_vlan1 and LOG_strace? ( If you don't have strace tool for your embedded device, you might fetch one here: http://impactlinux.com/fwl/downloads/binaries/old/0.9.11/ ) > Am I doing something wrong, or the relay daemon in this particular > busybox version is faulty? dhcprelay isn't a particularly heavy tested piece of code. It might have bugs. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
