Re: Routing Networks

From: Isaac Gelado (igf_at_tid.es)
Date: 01/14/04

  • Next message: Adrian Penisoara: "Handling 100.000 packets/sec or more"
    Date: Wed, 14 Jan 2004 08:43:37 +0100
    To: freebsd-hackers@freebsd.org
    
    

    Nicolás de Bari Embríz G. R. escribió:
    > Hi all, I need some help routing or making Nat on a LAN.
    >
    > I have something like this:
    >
    >
    > I N T E R N E T
    > -----------------
    > ^ ^
    > | |
    > fxp0 public IP public IP
    > | |
    > FreeBSD server LINUX server
    > | |
    > dc0 192.168.10.1 |
    > dc1 192.168.1.1 ^ 192.168.1.3
    > ^ | ^
    > | | |
    > | | |
    > ----------------
    > | Switch/Hub |
    > ----------------
    > | |
    > ------------------ -----------------
    > | LAN A | | LAN B |
    > | 192.168.10.2-254 | | 192.168.1.4-100 |
    > ------------------ -----------------
    >
    >
    > What i want to do is that a computer on LAN A with an IP on the range of
    > 192.168.10.2-254 can ping, telnet, ssh, etc. to a computer on LAN B
    > "192.168.1.X".
    >
    > How can i solve this problem, is this is a route or Nat problem ?

    I think it is a route problem. You must add next static route:

       - On the linux machine route all incoming packets with dest addr
    192.168.10.x to 192.168.1.1

    It shouldn't be necesary a static route on the freebsd machine since it
    has a network device with an addr of LAN B. Of course you must run a
    route daemon in both machines (I supouse it's running now since they are
    working as gateways) and the previous route must be added to the route
    daemon running on the linux machine.

    You can allways check that packets are going by the correct way with
    traceroute.

    Regards,
      Isaac

    -- 
      __________________________________________________________
    |        Isaac Gelado           |                          |
    |       Telefónica I+D          | Tlf 983367649            |
    |    Paq. Tec. de Boecillo      |                          |
    |        Valladolid             | igf@tid.es               |
    |_______________________________|__________________________|
    |   As gold which he cannot spend will make no man rich    |
    | so knowledge which he cannot apply will make no man wise |
    |__________________________________________________________|
    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
    

  • Next message: Adrian Penisoara: "Handling 100.000 packets/sec or more"

    Relevant Pages

    • Re: Routing Networks
      ... I need some help routing or making Nat on a LAN. ... I think it is a route problem. ... daemon running on the linux machine. ...
      (freebsd-hackers)
    • Re: 2nd route to LAN added when client connects
      ... The route I am speaking of is the route to local LAN that is put in the ... After the RAS client connects there is another route added so the two ... is the Internal Interface on the server used by RAS. ...
      (microsoft.public.win2000.ras_routing)
    • RE: Route added by RRAS that overrides local LAN route on NIC
      ... route was still added it no longer interfered with my LAN network route ... routes are added to the routing table on the server when a RAS client ... Microsoft CSS Online Newsgroup Support ...
      (microsoft.public.windows.server.sbs)
    • Re: 2nd route to LAN added when client connects
      ... The route I am speaking of is the route to local LAN that is put in the ... After the RAS client connects there is another route added so the two ... is the Internal Interface on the server used by RAS. ...
      (microsoft.public.win2000.ras_routing)
    • Re: Network configuration problem.
      ... >> Also, with the Linksys wireless device, how did you connect it? ... >> wireless users are simply bridged over to that network. ... > defaults the LAN address of the Linksys router is 192.168.1.1 but since ... Did you try specifying the subnet mask on the route you put into your ...
      (Fedora)