Keep finding this address in routes -> 10.18.160.1



  • Anyone have ideas on why I have this showing up in my routes?
    My home addresses use 10.x.x.x/24.
    I can't figure out what to do with this, plus I have a firewall rule that doesn't seem to help.



  • Is that a multiwansetup and this is a monitor IP? We add static route behind the scenes for monitor IPs to make sure the monitorpings always go out the correct interface.



  • @hoba:

    Is that a multiwansetup and this is a monitor IP? We add static route behind the scenes for monitor IPs to make sure the monitorpings always go out the correct interface.

    Okay, so what you are saying is that since I have 2 nics (Lan and bridge), the ip works as a traffic cop to make sure traffic is going the right way? Does that make sense?  But why would you use up an IP address for something like this?  I guess I'm not knowledgeable enough to realize the use of this.
    It's good to know this so that I don't assign that ip to anything as a static.
    Has anything related been posted somewhere else?  I don't want to post a dupe message.
    Thanks for your help.



  • No, I was talking about multiwan and loadbalancing. This is not the case with your setup so I don't know what's going on. It was just a guess.



  • @hoba:

    No, I was talking about multiwan and loadbalancing. This is not the case with your setup so I don't know what's going on. It was just a guess.

    Okay… do you think I could have something setup wrong with my Lan+Bridge?  I also have dd-wrt running on wifi.  I basically setup dd-wrt to use Lan card and then plugged switch into bridge connector.  There shouldn't be any problem using wireless router right?
    Is there a list of IP's that are used by the system posted somewhere on this board?



  • Okay, so I started having problems with my wan ip last night and eventually got to the point that I couldn't get out for more than a couple seconds.  I thought it might be my firewall rules, but it's weird that I was able to get out for at least 3 or 4 days with no problem, then last night it all went to pot.  So this morning I reinstalled the box and I'm out fine again.  It seems like I'm having to reinstall every so often; I thought it might be cause I was loading snort, but I didn't even have snort on this time.  ???  It's kind of frustrating.  I'm going to upgrade to 1.0.1 and setup my firewall rules again and see what happens.



  • Okay… so after all this I'm still getting these blocked, looks like it at least. Could this be generated on my network?  It doesn't look like it is.  These were all blocked @17 WAN spoof check is what it says.

    Nov 11 10:48:43 WAN 10.18.160.1:67 255.255.255.255:68 TCP
      Nov 11 10:48:50 WAN 10.18.160.1:67 255.255.255.255:68 TCP
      Nov 11 10:48:51 WAN 10.18.250.1:67 255.255.255.255:68 TCP
      Nov 11 10:48:58 WAN 10.18.250.1:67 255.255.255.255:68 TCP
      Nov 11 10:49:03 WAN 10.18.160.1:67 255.255.255.255:68 TCP
      Nov 11 10:49:03 WAN 10.18.160.1:67 255.255.255.255:68 TCP



  • Port 67 is the port a bootp/dhcp server listens on, port 68 is the port the DHCP server
    sends out information on. So there is a DHCP server on your WAN. These things tend to spew a lot of packets. Very annoying.



  • @sai:

    Port 67 is the port a bootp/dhcp server listens on, port 68 is the port the DHCP server
    sends out information on. So there is a DHCP server on your WAN. These things tend to spew a lot of packets. Very annoying.

    Thanks.


Log in to reply