Gateway with an avahi-reflector can't resolve hostnames in a subnet, even though clients in both subnets can - networking

I've got a router (runs OpenWrt), on which I've installed avahi and configured it to be a reflector.
I've got two subnets (e.g. subnet1: 192.168.1.X; subnet2: 192.168.2.X).
Subnet1 is the LAN network of that router, subnet2 is plugged into the WAN port (some other router is the gateway there).
Devices with avahi on both subnets can resolve hostnames through the reflector - e.g. device 192.168.2.20 can resolve a hostname "LinuxDevice.local" as 192.168.1.10.
So the avahi reflector works, BUT the router with the reflector cannot resolve hostnames in the subnet2. It can resolve hostnames in subnet1 (the LAN one).
I really need the router to be able to resolve hostnames and I have no clue why it can't.
I'm pretty sure my firewall settings are correct - I've opened ports for the mDNS traffic.
Also changed the avahi-daemon.conf file to allow broadcasting on the loopback interface.

Related

Tailscale doesn't reconnect after WAN failover on upstream router

QUESTION:
Is there a way to trigger Tailscale to restart in a scenario like the following so that packets again flow to a remote Tailscale subnet over a backup ISP connection?
Scenario: Tailscale does not reconnect after my upstream router fails over to its backup ISP connection.
Prior to failover, local client machines can ping public IP addresses -- 8.8.8.8 for example -- as well as private IP addresses on the other side of a Tailscale subnet router -- 10.0.0.2 for example.
After failover, local clients regain public Internet access, but the private network on the other side of the Tailscale subnet router remains unreachable. The remote Tailscale subnet never becomes reachable again, even after waiting over 15 minutes.
The upstream router fails back after plugging the local WAN1 ethernet cable back in. Clients can still access the public Internet and can again reach the remote Tailscale subnet.
Test configuration:
Tailscale is running on a local Linux machine with IP forwarding enabled.
IP address is 192.168.0.2.
Default route is via 192.168.0.1.
Tailscale flags:
--advertise-routes=192.168.0.0/24
--snat-subnet-routes=false
--accept-routes
Local upstream router has two WAN ports configured for failover only.
WAN1 connects to a cable modem in bridge mode.
WAN2 connects to an LTE router in bridge mode.
LAN IP address is 192.168.0.1.
Static route to 10.0.0.0/8 via 192.168.0.2.
Tailscale is running on a remote EC2 instance in an AWS VPC with IP forwarding enabled.
IP address is 10.0.0.2.
Default route is via 10.0.0.1.
Tailscale flags:
--advertise-routes=10.0.0.0/8
--snat-subnet-routes=false
--accept-routes
tailscaled generally reacts to linkchange events, like links going up or down, and figures out which interface has the default route. If both interfaces remain up and both interfaces have a default route, it may not know which one to use.

Accessing connected devices to a local network wirelessly

Hello Everyone!
I want to know that is there any way to access a photocopier machine which is connected to a computer through Ethernet wire and that computer is connected to my WiFi network?
P.S: What if I don't know the IP assigned to that Photocopier machine?
If the wireless network is part of the wired network you should have any problem reaching the photocopier.
If you don't know the IP address, you can reach it by host name if the DHCP and DNS are working properly. If you are on an Active Directory infrastructure and DHCP and DNS are integrated it should be transparent.
If you are on your home with a "home" router they usually do the hostname to IP resolve (DNS).
You can nslookup hostname in your machine to see if your dns is resolving the ip address. you can also ping hostname or ping ip address to test that you can reach the desired host. Some hosts block ping (ICMP) requests, please note that ping is ping does not respond is not a definitive solution.
Please note that in your home router you should use your router or default gateway to be the DNS also, and then add the google public DNS or your ISP.
Also when connecting the access point to an existing network you may have 2 DHCP servers providing IP addresses to hosts, you should disable DHCP on the Access Point and connect the AP to the network using the switch port and not the WAN port (the WAN port will try to do NAT and assign a different set of IP addresses).

Tcp spoofing with a trusted ip

I am facing a very strange problem. I have a task to establish a TCP connection to a server who has a trusted IP. And I have to run the code in a host with private IP address. The trusted IP is 10.10.10.15, which is also a private IP. And the question arises that the IP address of my host and the trusted IP is not on the same network. To be specific, my IP address is 10.0.35.1/24. Please let me know if there is any solution to this problem
Presumably these subnets, i.e. 10.10.10.0/24 (?) and 10.0.35.0/24, are part of your local network. You will need a Layer 3 device to perform inter-VLAN routing.
This will be a router with Layer 3 VLAN interfaces, in the Cisco world they would be SVIs, that would be acting as the default gateway of the subnets in your network. What happens is all traffic that needs to go between two hosts between different networks, has to go through their default gateway and it will be routed to the destination network/VLAN.
As long as the network devices between the two clients are able to route packets between these networks, the hosts will be able to reach each other. In your code, you simply need to specify that these packets need to go to the private IP address of the other host.

devstack juno networking route between networks

How can I configure neutron to allow routing between private networks in the same tenant? When I connect two private subnets with a router, I can't ping instances across the router.
The router isn't enough. You also need to specify a security group rule allowing incoming ICMP packets to the VMs.
It sounds like you need to set the host routes for each network or set the default gateway to be the router that connects the 2 networks.

dnsmasq resolve DNS queries normally

I'm new to dnsmasq and networking isn't my strong point, hopefully i'm missing something simple.
I have a Ubuntu laptop running dnsmasq. The laptop's WiFi is connected to the Internet, the laptop's ethernet is connected to a LAN.
Plugging my machine into the LAN I am assigned an IP address by the laptop. Accessing www.google.com on my machine gets picked up the laptop and i'm served the laptops Apache page, which is my desired result. The problem is I can't access any other website, Destination Host Unreachable.
I'd like the laptop running dnsmasq to allow my machine to resolve DNS queries normally and only be restricted when accessing www.google.com.
My dnsmasq.conf is the default except:
address=/www.google.com/192.168.0.1
interface=eth0
dhcp-range=192.168.0.50,192.168.0.150,12h
I've a feeling it might be related to the IP settings on each network?
The WiFi has a static IP 192.168.1.55 taking to the router at 192.168.1.1 and the DNS server at 192.168.1.10.
The ethernet is configured manually with an IP 192.168.0.1 setting the router as the WiFi IP 192.168.1.55 and the same for the DNS server 192.168.1.55.
Thanks in advance for any help.
Pete
After a lot of fiddling, this was related to iptables and not dnsmasq.

Resources