Re: Communication between hosts on different network interfaces

2024-01-30 Thread olp_76
Indeed, that is why I always added 0.0.0.0/0 Sorry for not mentioning it. On Tuesday, January 30, 2024 at 08:56:19 p.m. GMT+9, Stuart Henderson wrote: On 2024-01-07, All wrote: > This is very much doable with DHCP one liner: > add the following to your dhcpd.conf ((!) inside the

Re: Communication between hosts on different network interfaces

2024-01-30 Thread Stuart Henderson
On 2024-01-07, All wrote: > This is very much doable with DHCP one liner: > add the following to your dhcpd.conf ((!) inside the block of your > 192.168.2.0/24 network) > option classless-static-routes 192.168.3.0/24 192.168.2.1; > > This will install static route into all machines in

Re: Communication between hosts on different network interfaces

2024-01-30 Thread Ibsen S Ripsbusker
Dear colleagues, A printer doesn't need internet access, and that is why I can block the internet access. The printer on the white network a label printer that just works. The other printer is a laser printer connected by USB to an Ubuntu computer on the white network, because that was easier

Re: Communication between hosts on different network interfaces

2024-01-07 Thread All
This is very much doable with DHCP one liner: add the following to your dhcpd.conf ((!) inside the block of your 192.168.2.0/24 network) option classless-static-routes 192.168.3.0/24 192.168.2.1; This will install static route into all machines in 192.168.2.0/24 network. When they will try to

Re: Communication between hosts on different network interfaces

2024-01-06 Thread Nick Holland
On 1/6/24 15:09, Ibsen S Ripsbusker wrote: Dear colleagues, I have various network appliances that I don't really trust, like a printer. I have these plugged into an unmanaged switch and connected to network interface igc2. I want to allow the igc1 network to make web requests to the igc2

Re: Communication between hosts on different network interfaces

2024-01-06 Thread Brian Conway
On Sat, Jan 6, 2024, at 2:09 PM, Ibsen S Ripsbusker wrote: > I also tried setting different subnets. > > /etc/hostname.igc1: > inet 192.168.2.1/24 > > /etc/hostname.igc2: > inet 192.168.3.1/24 This is what I have done, with a pf rule to block connections originating from my less-trusted