Rare project developers

[mc36 <>]

hi,
good news, you have connectivity... then my next question is,
did you anything to qemu to know about the network 192.168.0.0/24?
if not, then you'll have to configure freerouter to perform nat for
this range to it's uplink interface... assuming it's the default
installation or close to it, you can simply append the client
range to the already configured nat (that's how 10.255.255.0/24
reaches the internet) here we go:
object-group network host4
 sequence 20 192.168.0.0 255.255.255.0
br,
cs



On 5/25/22 06:46, Gabriel Tetzner wrote:
> Hi Csaba,
>
> -if the ubuntu client can ping the 192,168.0.1?
>
> Yes, it can ping 192.168.0.1
>
> output:
> ping1.png
> -if the ubuntu client can ping the 10.0.2.15?
>
> Yes, it can ping 10.0.2.15
>
> output:
>
> ping2.png
>
> -if freerouter installed the default route: sho ipv4 rou inet
>
> show ipv4 route inet - output:
>
>
> checkipv4route.png
>
> -if the client can ping the freerouter's default gw? (from the above output)
>
> No, he no ping the freerouter default gw.
>
> output:
>
> ping3.png
>
> I am pretty sure, that I have to point the route from 192.168.0.1 to 
> 10.0.2.2, am I right?
>
>
> Em qua., 25 de mai. de 2022   s 01:05, mc36 < <>> 
> escreveu:
>
>     hi,
>     it should work with routed interfaces.... things to check:
>     -if the ubuntu client can ping the 192,168.0.1?
>     -if the ubuntu client can ping the 10.0.2.15?
>     -if freerouter installed the default route: sho ipv4 rou inet
>     -if the client can ping the freerouter's default gw? (from the above 
> output)
>     br,
>     cs
>
>
>     On 5/25/22 01:33, Gabriel Tetzner wrote:
>      > Hi all,
>      >
>      > Question:
>      >
>      > I decided to test a different DHCP Server topology on FreeRouter.
>      >
>      > Topology (VMs):
>      >
>      >     * RARE/freeRtr - Debian 11
>      >     * 2 Clients - Ubuntu 21.04
>      >
>      > The network configuration, defined a NAT (WAN) to Internet and a 
> Internal network (LAN).
>      > I got the client to receive the DHCP IP on the FreeRouter, but it is 
> without external connectivity.
>      > I wanted to know if it is necessary to configure a routing policy for 
> the Ethernet1 interface or is a bridge perhaps needed to perform such a routing 
> function?
>      >
>      > Gateway: 192.168.0.1 (Internal network - Interface Ethernet2).
>      > Objective: Fetch connectivity via 10.0.2.15 (NAT - Ethernet1 
> interface).
>      >
>      > Configuration Server DHCP freeRtr:
>      >
>      > !
>      >
>      > server dhcp4 dhcp-server
>      >      pool 192.168.0.2 192.168.0.100
>      >      gateway 192.168.0.1
>      >      netmask 255.255.255.0
>      >      no dns-server
>      >      domain-name
>      >      interface ethernet2
>      >      vrf inet
>      >      exit
>      > !
>      >
>      > I need my DHCP to receive external connectivity, more details from the 
> question on github:
>      > 
> https://github.com/Tetzdesen/Experimentos-FreeRouter/tree/main/experiment-dhcp/experiment-two
>     
> <https://github.com/Tetzdesen/Experimentos-FreeRouter/tree/main/experiment-dhcp/experiment-two>
>      > 
> <https://github.com/Tetzdesen/Experimentos-FreeRouter/tree/main/experiment-dhcp/experiment-two
>     
> <https://github.com/Tetzdesen/Experimentos-FreeRouter/tree/main/experiment-dhcp/experiment-two>>
>      >
>      >
>      >