2015-04-18 - Re: [GRASE-Hotspot] how does Grase determine which tun to use.

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 7cf16c20966b35aac8ededb14dd4683021a68fa52e0eae549cdea19a07a0ec04
Message ID: <CAESLx0JRFktUQcQCqhpTnW5jeuUxjyar3RGXuV2m0zWm4RKT8g@mail.gmail.com>
Reply To: <f74d9388-1035-4b91-8066-e10ad6b84195@grasehotspot.org>
UTC Datetime: 2015-04-18 03:44:19 UTC
Raw Date: Sat, 18 Apr 2015 20:44:19 +1000

Raw message 

Hi Dave

Can you please file a bug about the status page. Grase is actually using
the correct tun (it creates the tun it needs at startup), it's just the
status page that's at fault.

In the installation instructions, I take it you read about the
grase-conf-openvpn package before installing it? That's where the second
tun device comes from.

Regards

Tim

On Fri, Apr 17, 2015 at 11:25 PM, dave <da***e@argyle.com.au> wrote:

> 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
>
> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gr***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at
> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f74d9388-1035-4b91-8066-e10ad6b84195%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f74d9388-1035-4b91-8066-e10ad6b84195%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread