2012-11-25 - Re: [GRASE-Hotspot] where did tun1 ifc come from?
Header Data
From: Tim White <ti***8@gmail.com>
Message Hash: 86c96cb81409ef715cad3a861cdf20d0ef2c5c50639c9f14b5a30637957fe4a7
Message ID: <50B28CDC.6010804@gmail.com>
Reply To: <CADDedMH3pwR+a+ucD7ijz+bf+=JbWTxS4yi1Lf0sB7VjfJeM5Q@mail.gmail.com>
UTC Datetime: 2012-11-25 14:25:48 UTC
Raw Date: Mon, 26 Nov 2012 07:25:48 +1000
Raw message
On 23/11/12 23:31, emre erdo\u011fan wrote:
> hi everyone. i have been using grase for 20 days and there were no
> problem. Everything was going ok till i changed my pc's location, from
> one room to another. Same computers are using the network and no
> software changes were made. However after this users could not get ip
> address from dhcp. Also this problem is affecting our network badly.
> Some computers had tcp problem.
> Because of dhcp and tcp errors, i checked the network adapters and the
> result is below:
> bilgiislem@ubuntuspot:~$ ifconfig
> eth0 Link encap:Ethernet HWaddr 00:16:17:57:3b:7e
> inet addr:192.168.0.221 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::216:17ff:fe57:3b7e/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1417 errors:0 dropped:23 overruns:0 frame:0
> TX packets:323 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:304746 (304.7 KB) TX bytes:31789 (31.7 KB)
> Interrupt:17
>
> eth1 Link encap:Ethernet HWaddr 00:02:44:ac:ff:14
> inet6 addr: fe80::202:44ff:feac:ff14/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3284 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1244 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:728852 (728.8 KB) TX bytes:692253 (692.2 KB)
> Interrupt:20 Base address:0x8000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Sunucu
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:716 errors:0 dropped:0 overruns:0 frame:0
> TX packets:716 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:109566 (109.5 KB) TX bytes:109566 (109.5 KB)
>
> tun0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:10.1.0.1 P-t-P:10.1.0.1 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:804 errors:0 dropped:0 overruns:0 frame:0
> TX packets:853 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:126857 (126.8 KB) TX bytes:618432 (618.4 KB)
>
> 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.149 P-t-P:10.64.63.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)
>
>
> Now the problem is continuing if i don't down tun1 (ifconfig tun1 down)
> What can be done?
> What may couse this?
> Can i fix it if i edit the /etc/chilli/ipup.sh and change $NET/$MASK
> with 10.1.0.0/24 <http://10.1.0.0/24> and $ADDR with 10.1.0.1?
> What do you think?
>
> Thanks and good luck to everybody...
tun1 has been there since the first install you did. It's there because
you installed the grase-conf-openvpn package, and it will not be
effecting your users as they are on a different network.
If you are having network issues, first thing to try is rebooting to see
if there is another issue. Modifying the ipup.sh script is just asking
for trouble.
Given that you moved the computer and made no software changes, what
changed in the hardware? Could you now have a faulty cable to the computer?
Tim
Thread
-
Return to November 2012
- Return to “emre erdoğan <po***e@gmail.com>”
-
Return to “Tim White <ti***8@gmail.com>”
- 2012-11-23 (Fri, 23 Nov 2012 15:31:20 +0200) - [GRASE-Hotspot] where did tun1 ifc come from? - emre erdoğan <po***e@gmail.com>
- 2012-11-25 (Mon, 26 Nov 2012 07:25:48 +1000) - Re: [GRASE-Hotspot] where did tun1 ifc come from? - Tim White <ti***8@gmail.com>