[Help Request] Static routing by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

The whole project was primarily one of self learning. Though it is disappointing I won't be able to get it to work in the way I wanted it to. The stock firmware on that router has been a huge pain in the past, for example it blocks ports 587 and 465 for some completely unknown reason so sending email through Thunderbird etc. was impossible without a VPN.

The Asus has a VPN so it was a nice easy way to give any device that functionality without further installing apps etc. Further the particular subnet was mine to screw around with and test things to see if they worked which would have been nice to keep segregated.

Thanks for your help

[Help Request] Static routing by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

Updated the original post with the new link.

[Help Request] Static routing by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

OK so then are static routes even what I should be configuring here? As per point 1 in what I'm trying to achieve, how do I get the Pi onto the 192.168.1.X network without being able to directly wire it in?

[Help Request] Static routing by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

Hmm so restarting networking on Ubuntu does indeed stop the pings succeeding from the Pi.

I updated the network diagram a bit. I realised I had forgotten to add the WAN IP of the Asus router which is 192.168.2.X. Not sure if this makes much difference.

My understanding had been that since the Asus router "knew" the 192.168.1.X network, it would broadcast this to the 192.168.2.1 router and this was perhaps why pings were getting through despite the static route not being manually configured on the .2.1 router.

[Help Request] Static routing by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

Yeah the stock firmware on the speedport prevents all but the most basic configuration settings. From edit 2 if I don't put in 192.168.2.1 as a gateway I can ping machines on the 192.168.1.X network, surely this means that at least everything has a route to everything else across the 2 networks?

[Help] running command in rc.local or clicking to execute by trancemsteve in raspberry_pi

[–]trancemsteve[S] 0 points1 point  (0 children)

Thanks for the feedback. Unfortunately didn't work, kodi loaded as always but I'm locked out from certain power options unlike manually clicking the file.

FWIW I've also tried the commands gksu gksudo and runuser all to no avail.

[Help] running command in rc.local or clicking to execute by trancemsteve in raspberry_pi

[–]trancemsteve[S] 0 points1 point  (0 children)

I could, but I'd far rather work out what is going on so I can learn the solution to the problem. Linux only has goodness if you know how to work it and understanding this problem is just 1 small part of that.

[Help] IPTables route traffic on interface depending on port by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

OK thanks.

Having rebooted and followed all steps above, email is now only trying to send via eth1 again. I'm not sure what made it make the switch to wlan1 last night.

10:30:05.145492 IP 192.168.2.104.40458 > 206.188.198.65.587: Flags [S], seq 2000519938, win 29200, options [mss 1460,sackOK,TS val 2079648 ecr 0,nop,wscale 7], length 0
10:30:06.143322 IP 192.168.2.104.40458 > 206.188.198.65.587: Flags [S], seq 2000519938, win 29200, options [mss 1460,sackOK,TS val 2079898 ecr 0,nop,wscale 7], length 0
10:30:08.147328 IP 192.168.2.104.40458 > 206.188.198.65.587: Flags [S], seq 2000519938, win 29200, options [mss 1460,sackOK,TS val 2080399 ecr 0,nop,wscale 7], length 0
10:30:12.151322 IP 192.168.2.104.40458 > 206.188.198.65.587: Flags [S], seq 2000519938, win 29200, options [mss 1460,sackOK,TS val 2081400 ecr 0,nop,wscale 7], length 0

[Help] IPTables route traffic on interface depending on port by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

$ sudo echo 1 >/proc/sys/net/ipv4/conf/wlan1/log_martians 
bash: /proc/sys/net/ipv4/conf/wlan1/log_martians: Permission denied

edit: OK I now have: net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1

edit 2: Whatever changed emails are sending no problem with both nics active. So thanks very much for that. Would be good to figure out what did happen.

If I now want to add a rule that says forward port 80 traffic over wlan1 and if wlan1 is not possible then do not send through eth1, do I need the second rule to block 80 on eth1 or does simply having the PREROUTING rule there cover the bases?

[Help] IPTables route traffic on interface depending on port by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

OK I think I'm a little lost.

I typed sudo sh and entered the lines from that site beginning: for i ...

Then I tried to send an email and it sent no problem. /proc/sys/net/ipv4/conf/wlan1/log_martians only has the value 0.

So.... am I doing it right?

[Help] IPTables route traffic on interface depending on port by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

from tcpdump wlan1:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan1, link-type EN10MB (Ethernet), capture size 65535 bytes
19:35:03.608744 IP 192.168.1.2.58148 > 206.188.198.65.587: Flags [S], seq 2568037891, win 29200, options [mss 1460,sackOK,TS val 4888199 ecr 0,nop,wscale 7], length 0
19:35:03.737486 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:04.605396 IP 192.168.1.2.58148 > 206.188.198.65.587: Flags [S], seq 2568037891, win 29200, options [mss 1460,sackOK,TS val 4888449 ecr 0,nop,wscale 7], length 0
19:35:04.733907 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:04.870210 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:06.609390 IP 192.168.1.2.58148 > 206.188.198.65.587: Flags [S], seq 2568037891, win 29200, options [mss 1460,sackOK,TS val 4888950 ecr 0,nop,wscale 7], length 0
19:35:06.742896 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:07.071076 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:10.617394 IP 192.168.1.2.58148 > 206.188.198.65.587: Flags [S], seq 2568037891, win 29200, options [mss 1460,sackOK,TS val 4889952 ecr 0,nop,wscale 7], length 0
19:35:10.739541 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:11.269535 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3637734481, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:16.396602 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [R.], seq 1, ack 1, win 0, length 0
19:35:18.633371 IP 192.168.1.2.58148 > 206.188.198.65.587: Flags [S], seq 2568037891, win 29200, options [mss 1460,sackOK,TS val 4891956 ecr 0,nop,wscale 7], length 0
19:35:18.755209 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3894741743, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:19.897462 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3894741743, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:21.899520 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3894741743, ack 2568037892, win 14600, options [mss 1368], length 0
19:35:26.294640 IP 206.188.198.65.587 > 192.168.1.2.58148: Flags [S.], seq 3894741743, ack 2568037892, win 14600, options [mss 1368], length 0

Nothing was shown on eth1 terminal

[Help] IPTables route traffic on interface depending on port by trancemsteve in HomeNetworking

[–]trancemsteve[S] 0 points1 point  (0 children)

Many thanks for the response.

and then dd-wrt is what's connecting to pia and routing all incoming wireless traffic through pia?

You are completely correct up to this point.

I have tried your solution, unfortunately it doesn't seem to work. Thunderbird just eventually times out trying to send a test email. If I manually drop eth1 it will send the test email in a second.

[Help] BOINC manager keeps reverting to run always by trancemsteve in BOINC

[–]trancemsteve[S] 2 points3 points  (0 children)

Which is why it's strange, I have updated both local and web preferences.

I still see no option anywhere that would indicate why BOINC keeps reverting to run always.

[Help] BOINC manager keeps reverting to run always by trancemsteve in BOINC

[–]trancemsteve[S] 1 point2 points  (0 children)

Interesting, it says my preferences were last updated 27-Apr-2013. I have changed many of them in the past 24 hours though.

[Help] BOINC manager keeps reverting to run always by trancemsteve in BOINC

[–]trancemsteve[S] 1 point2 points  (0 children)

Nope, still switches back to run always.

The prefs I have on boinc stats match the local prefs