[Dnsmasq-discuss] Problem with VM and dnsmasq

[mario]

Dear Albert,

On 10/13/2015 11:49 AM, Albert ARIBAUD wrote:
> Actually not all of them: I believe you have not tested my suggestion 
> that you set a fixed IP in the VM instead of using DHCP, connect the 
> host through wlan, boot up the VM and then test connectivity between 
> the VM and gateway ([ar]ping, netcat...) so that you can determine 
> whether your issue is DHCP-related or "just" network-related. 
> Amicalement, 

it works perfectly, see the attached file. Sequence of ops:

1. Disconnect host from ethernet; put it on wifi;
2. configure VM to connect thru the host wlan0 interface, bridge adapter.
3. start VM; in VM... (see attached file!)
4. stop network-manager;
5. check that VM's ethernet interface has not received an IP address 
from gateway;
6. Configure VM's eth0 manually;
7. Ping remote site.

On 10/13/2015 11:49 AM, Albert ARIBAUD wrote:
> Actually, The reply is lost somewhere between the gateway (where the
> reply is seen to be sent) and the host (where it is not seen to be
> received). It is unsure whether it could leave the gateway or not. It
> could have left the gateway been lost by the AP (which, IIUC, is
> another machine as the gateway).

Nope, there is a slight confusion: the tcpdump capture on the gateway 
includes two distinct conversations, one with a normal Intel pc with MAC 
address c4:85:08:7d:79:40 which DOES receive
two replies, and another connection with the typical (for VirtualBox 
VMs) CADMUS pc with MAC address
08:00:27:03:6a:3e, which is the VM I am talking about, which never 
receives a reply, even though the
daemon.log displays the fact that dnsmasq has offered it a perfectly 
good IP address.

In other words, dnsmasq's reply is lost somewhere between dnsmasq itself 
and tcpdump on the same gateway.

I might add, to add insult to injury, that during the week-end I tried 
this in my home, and my dd-wrt dnsmasq worked flawlessly where my Debian 
gateway fails.

Cheers,

Mario
-------------- next part --------------
root at debbie:/# service network-manager stop
root at debbie:/# killall -9 dhclient
dhclient: no process found
root at debbie:/# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:fd:7b:a0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fefd:7ba0/64 scope link 
       valid_lft forever preferred_lft forever
root at debbie:/# ip link set dev eth0 down
root at debbie:/# ip addr flush dev eth0
root at debbie:/# ip addr add 192.168.73.213/24 dev eth0
root at debbie:/# ip link set dev eth0 up
root at debbie:/# ip route add default via 192.168.73.1
root at debbie:/# echo nameserver 192.168.73.1 >> /etc/resolv.conf
root at debbie:/# ping -c1 www.repubblica.it
PING www.repubblica.it (213.92.16.191) 56(84) bytes of data.
64 bytes from www.repubblica.it (213.92.16.191): icmp_seq=1 ttl=53 time=14.2 ms

--- www.repubblica.it ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 14.202/14.202/14.202/0.000 ms