VENET device is explicitly NOARP, so this can't be fixed.
pls use VETH
Regards,
Den
On Wed, 2009-02-04 at 18:22 +0300, Vitaliy Gusev wrote:
> Hi!
> On 30 January 2009 12:29:29 Dariush Pietrzak wrote:
> > Hi,
> > the problem with DHCP and venet, is that dhcp packets are adressed to
> > 255.255.255.255, and you can't route packets destined for 255.255.255.255
> > with routing tables.
> > But, you sure can direct them towards venet-connected node using other
> > means,
> > here's the one:
>
> I wonder. Why don't you use veth interface for this purpose?
>
> >
> > host: # iptables -t mangle -A PREROUTING -d 255.255.255.255 -j ROUTE --gw
> > 192.168.190.250
> >
> > host: # iptables -nvL -t mangle:
> > 12394 4069K ROUTE 0 -- * * 0.0.0.0/0
> > 255.255.255.255 ROUTE gw:192.168.190.250
> >
> > then inside vz guest:
> >
> >
> > tcpdump -n -i venet0:0
> >
> > 02:31:34.337137 IP 192.168.190.138.68 > 192.168.190.250.67: BOOTP/DHCP,
> > Request from 00:a1:3d:1d:b9:a5, length 548
> >
> > 08:31:35.188004 IP 192.168.190.138.68 > 192.168.190.250.67: BOOTP/DHCP,
> > Request from 00:a1:3b:1d:b9:a5, length 548
> > 08:31:35.188040 IP 192.168.190.250 > 192.168.190.138: ICMP 192.168.190.250
> > udp port 67 unreachable, length 556
>
> Was a dhcpd server run in VE (on 192.168.190.250) ? What say netstat?
>
> >
> > the other would be using dhcp-relay on the HN
> >
>
>
>
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
