2015-04-17 - how does Grase determine which tun to use.

Header Data

From: dave <da***e@argyle.com.au>
Message Hash: 7e35b06b426aa4b97671cecfbeac6d65ec0f48c96f4d69dd1f49caad15ce06c1
Message ID: <f74d9388-1035-4b91-8066-e10ad6b84195@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2015-04-17 06:25:46 UTC
Raw Date: Fri, 17 Apr 2015 06:25:46 -0700

Raw message 

We have a new install and everything was working fine until we did a 
reboot. 
Unfortunately I don't have exact setting from before reboot. 

Anyhow - The main issue seems to be that Grase has determined that the LAN 
IP address should be the IP that is associated with tun1.
But in fact the LAN IP setting that we saved are associated with tun0.

eth0      Link encap:Ethernet  HWaddr 00:0c:29:f2:dc:da  
          inet addr:192.168.10.50  Bcast:192.168.10.255  Mask:255.255.255.0 
          inet6 addr: fe80::20c:29ff:fef2:dcda/64 Scope:Link 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
          RX packets:1246 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:1220 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000  
          RX bytes:148542 (148.5 KB)  TX bytes:687073 (687.0 KB) 
 

eth1      Link encap:Ethernet  HWaddr 00:0c:29:f2:dc:e4   
          inet6 addr: fe80::20c:29ff:fef2:dce4/64 Scope:Link 
         UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1 
          RX packets:2025 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:615 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000  
          RX bytes:320086 (320.0 KB)  TX bytes:177660 (177.6 KB) 


lo        Link encap:Local Loopback   
          inet addr:127.0.0.1  Mask:255.0.0.0 
          inet6 addr: ::1/128 Scope:Host 
          UP LOOPBACK RUNNING  MTU:65536  Metric:1 
          RX packets:310 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:310 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:0  
          RX bytes:38988 (38.9 KB)  TX bytes:38988 (38.9 KB) 


tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-
00-00-00   
          inet addr:172.16.8.1  P-t-P:172.16.8.1  Mask:255.255.248.0 
          UP POINTOPOINT RUNNING  MTU:1500  Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:100  
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B) 


tun1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-
00-00-00   
          inet addr:10.64.63.176  P-t-P:10.64.62.1  Mask:255.255.255.255 
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:100  
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



Grase status page shows 

<https://lh3.googleusercontent.com/-Zd6KgfPXA58/VTEIlBv9B3I/AAAAAAAAAFU/fsSWULku_OU/s1600/Screen%2BShot%2B2015-04-17%2Bat%2B11.14.37%2Bpm.png>

As you can see tun1 is showing up when my settings are applied to tun0. 

So how is Grase determining that it should be tun1 instead of tun0 and how 
can I make it identify the correct one. 

And why does the tun1 exist anyway? What is it for?


Dave

Thread