Hi, it’s my first post here so sorry if done here something improperly. I’m trying to build on my R2, interface-based manageable router device (part of university project) and one of the concepts which I was trying to implement was individually managable interfaces. Basicly every port could work on different subnet serviced by dnsmasq DHCP servers. And DHCP staff works flawlessly on every interface. The problem is strange behavior with communication between devices connected to those interfaces. My little lab looks like that: -lan0: 10.0.0.1/24, connected device “PC” with obtained IP 10.0.0.2 -lan1: 10.0.1.1/24, connected device “Raspberry” with obtained IP 10.0.1.2 -lan2: 10.0.2.1/24, connected device “Kali” with obtained IP 10.0.2.2 -lan3 not important. And now my problems.
- Raspberry can’t ping PC or Kali and same goes for Kali but somehow PC CAN ping Raspberry. I’m not using bridge on any interface. Firewall is completly open. From R2 I can obviously reach any interface and device. The point is I would like to communicate with other subnets, but in this situation I kinda don’t understand why it is happening. Is this even achivable to let them speak between each other? If not, than why PC is pinging Raspberry? Could it be some hardware bug?
- Second issue is an extension to that above problem with communication. Im trying to implement with dnsmasq functionality to let devices to speak with each other by the names rather than IP. I configured hosts (like shown below) and tried to use the working connection from PC to Raspberry. I used “ping 10.0.1.2” - worked, “ping Raspberry” - not worked, could not find host. R2 can ping devices by the name I assigned to them, so it’s probably some problem with broadcasting how hosts should resolve the name. Hosts obtained DNS server address from DHCP and it’s pointing on connected interface so for PC it’s 10.0.0.1.
I’m using Debian 10 5.4.58-bpi-r2-main. Config files looks like that:
auto lo iface lo inet loopback auto eth0 iface eth0 inet manual pre-up ip link set $IFACE address 36:40:66:99:8d:ec up post-down ip link set $IFACE down auto eth1 iface eth1 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down #wan in dhcp mode allow-hotplug wan iface wan inet dhcp auto lan0 iface lan0 inet static address 10.0.0.1 netmask 255.255.255.0 hwaddress ether 8a:c1:03:9a:f3:a2 auto lan1 iface lan1 inet static address 10.0.1.1 netmask 255.255.255.0 hwaddress ether f2:31:2e:be:0b:30 auto lan2 iface lan2 inet static address 10.0.2.1 netmask 255.255.255.0 hwaddress ether 6e:22:8b:84:1f:97 auto lan3 iface lan3 inet static address 10.0.3.1 netmask 255.255.255.0 hwaddress ether 62:9c:87:b2:b9:05
interface=lan0 dhcp-range=lan0,10.0.0.2,10.0.0.254,48h ... interface=lan1 dhcp-range=lan1,10.0.1.2,10.0.1.100,48h ... interface=lan2 dhcp-range=lan2,10.0.2.2,10.0.2.254,48h ... dhcp-host=B8:27:EB:0D:18:7C,raspberry,10.0.1.2,infinite dhcp-host=2C:60:0C:9A:A2:A5,Kali,10.0.2.2,infinite dhcp-host=90:2B:34:18:B1:B4,PC,10.0.0.2,infinite
127.0.0.1 localhost 127.0.1.1 bpi-r2 ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters
domain home search home nameserver 127.0.0.1
If something needs more precise information, I would gladly provide more of them. Thanks in advance for any help