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

Forward to new device?

Discussion in 'Tomato Firmware' started by BikeHelmet, Apr 18, 2017.

  1. BikeHelmet

    BikeHelmet Networkin' Nut Member

    Hi everyone,

    Is there an easy way to remap or forward a single IP into a new subnet? Ex: Make a printer respond to 192.168.0.30 as well as 192.168.10.30, because 100+ legacy devices are all configured to point to a static local IP.

    I've been combing over DNSmasq documentation and playing with IPtables commands in the firewall section, but can't seem to get it to work. Someone that uses this stuff daily might know the proper syntax off the top of their head?

    Cheers,

    -BikeHelmet
     
  2. ruggerof

    ruggerof LI Guru Member

    I am not sure if I understood you correctly but have you tried using Avanced / Lan Access?
     
  3. BikeHelmet

    BikeHelmet Networkin' Nut Member

    I want to make it so that if you ping 192.168.0.30, 192.168.10.30 responds.

    Cisco docs indicate proxy-arp is required, because the requests have to flow through the router itself.

    May have found another way around the issue. Haven't gotten anything with IPTables/DNSMasq to work.
     
  4. Monk E. Boy

    Monk E. Boy Network Guru Member

    Setup your LAN as 192.168.0.0/16. Then both 192.168.0.0/24 and 192.168.10.0/24 are part of the same network and both IPs are valid for LAN traffic.

    Then you can just assign 192.168.10.30 to the printer and 192.168.0.0/24 IPs to clients and it'll all just work.
     
  5. BikeHelmet

    BikeHelmet Networkin' Nut Member

    100+ devices have static IPs entered into their print drivers. Subnets are changing to avoid conflicts with another linked network. All the devices are remapped easily enough through Static DHCP. But print drivers within Windows need to be changed manually, unless you (through some trickery) convince a computer that a device has two IP addresses.

    We found a relatively easy way to roll out changes to the print drivers.
     
  6. Monk E. Boy

    Monk E. Boy Network Guru Member

    If the printer is an active directory object you can just change the active directory object with the new information and devices should pick up the new printer automagically. Worst case you force it with gpupdate. There's also ways to script the change with powershell or another scripting language.

    Glad to hear you figured it out. I love the a-ha moment after I've been banging my head against the wall for a while.
     

Share This Page