6.15 is the latest software but 3.10 is pretty old firmware (or maybe the RB you have only does up to that) . I am using a RB2011 and have 3.16 firmware on it. Make sure you click upgrade _and_ then reboot. Via the WWW/Winbox it doesn't say/prompt to reboot after you tell it to upgrade that part of it (but if you look in the log it says you have to)
run tcpdump/wireshark and check you are getting traffic going in both directions, only easy way to see what's really happening if its not what you expect
sbiddle: Multiple PPPoE clients are just a mess because of the default route issue. I only configure multiple IPs via static IP addresses and offer this to my customers, it's a far simpler option and means you just need a simple masquerade rules to easily route traffic based on a source IP with the correct public IP and you're away.
That would actually make a good software update, being able to specify the route table for the default gateway entry on any PPP clients.
sbiddle: Multiple PPPoE clients are just a mess because of the default route issue. I only configure multiple IPs via static IP addresses and offer this to my customers, it's a far simpler option and means you just need a simple masquerade rules to easily route traffic based on a source IP with the correct public IP and you're away.
That would actually make a good software update, being able to specify the route table for the default gateway entry on any PPP clients.
It would.
Multiple IP's is something that's so easy when you just have a static IP, but difficult when you do it other ways.
What model Routerboard do you have an how is everything connected? Is there another switch involved? Where are the server and the testing PC physically connected in relation to each other.
Just trying to form a picture in my head to try and work out what's happening here.
Maybe someone has made a dodgey cable join somewhere (joke).
I have been working on this from a different network segment than what the server sits on. I had a route in the main table to route between networks but I didn't add one in the 'server' routing table. ARRGGHHHHHHH!!!!!!!
Can't believe I didn't realise that sooner!!
Thank you very very much for everybody's help. Turn's out I'm just stupid.
I just assumed they were on the same subnet given the both started with 192.168.2.X. So that was a good example of how assumptions can be friend or foe.
I have a range split up at home and it didn't enter my mind.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
ID Verified
Trusted
2degrees
Retired Mod
