1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SNMP / Internal IP Address

Discussion in 'DD-WRT Firmware' started by MBChris, Jun 28, 2005.

  1. MBChris

    MBChris Network Guru Member

    @all

    i found the MRTG-Bundle from innovations..... works with rrd and routers2.cgi which i mean its great to handle. I would like to integrate all my routers there . But now ive a big Problem :( Or is it not big ?

    All Client-Routers are in Gateway-Mode and getting DHCP from the Main-Router (So there WAN-Adress is sometimes change :( ) They all have differnet internal Nets e.g. 192.168.44.0/24. So the internal IP is 192.168.44.1. Now i would integrate them in the MRTG-requests with there internal Address.
    On the Main-Ap (the default Gateway for all clients) i insert static routes to these net's and hosts

    Code:
    route add -net 192.168.44.0 netmask 255.255.255.0 gateway 192.168.0.101 <- main AP
    route add -host 192.168.44.1 gateway 192.168.0.101
    
    a ping to 192.168.44.1 respond ok
    a telent to 192.168.44.1 is also ok

    BUT

    if i query SNMP over 192.168.44.1 i get no response !! And thats my problem.
    if i query SNMP over the DHCP-Address (e.g. 192.168.0.105) which the Router has gotten in the Login-Procedure, SNMP is also responding !

    REM: regardless of the Routing Mode (Gateway, RIP2 or OSPF) allways the same issue

    YES, i know i could give the routers static IPs over DHCP but this is my last way to make it functional because there is low RAm on the Main-AP and i dont know whats happen if i do about 50-100 Static-IP Entries in the nvram-var dhcp_statics ?!?!?!?!?!

    Hope someone could give me a hint

    Chris
     
  2. MBChris

    MBChris Network Guru Member

    sorry for pushing up this thread but i need a solution ....
     
  3. u3gyxap

    u3gyxap Network Guru Member

    Why don't you hardcode the settings into your client routers, let's say in the 192.168.0.240-249 range and force the DHCP server (another WRT I guess) to serve the 192.168.0.2-239. You still have the dynamic DHCP going, and the clinet WRTs on static. Easy, simple and reliable.
    The other way around is to setup DynDNS to your client router, and use the name in MRTG - SNMPRouter1.DynDNS.com or whatever. That also means you will need internet access for the client router, and the server that is running MRTG. I have this setup working.
     
  4. MBChris

    MBChris Network Guru Member

    YES, you are right the best way to do that IS static IPs for the Client WRTs !!!
    Better also for some other tasks !

    Thx for all replies, im happy with this solution now !
     

Share This Page