2014-04-11 - Re: WAN IP change
Header Data
From: al***e@gmail.com
Message Hash: ff289830e5c3b8c01355d403d6d7b87042138d8de340fa3fb7fc657eaedd47c0
Message ID: <5ce419f4-3648-4b7c-80ef-1b20873d6b6b@grasehotspot.org>
Reply To: <6081525b-ae69-4624-bab3-ed5d13c49dae@grasehotspot.org>
UTC Datetime: 2014-04-11 09:15:42 UTC
Raw Date: Fri, 11 Apr 2014 09:15:42 -0700
Raw message
So turns out my issue wasn't with Grase, I checked my router and the issue
was with a subnet mask wrongly configured before my time!
After I fixed it, I changed the IP on the WAN interface (eth1) under
/etc/network/interfaces/ , rebooted the network services
(/etc/init.d/networking restart) and it worked straight away (I was able to
ping both GW and the Internet).
So I am terribly sorry for the wrong posting!
On Friday, April 11, 2014 6:08:34 AM UTC-7, ca***.@gmail.com wrote:
>
> I am having the same issue. My problem is that it is not practical for me
> to build the server at the site since it is technically a small trailer
> offsite. So I need to be able to change the WAN IP to connect to the
> internet. So helping alois helps me too :)
>
> On Friday, April 11, 2014 8:51:03 AM UTC-4, John Crisp wrote:
>>
>>
>>
>> On Thursday, 10 April 2014 20:38:04 UTC+2, al***.@gmail.com wrote:
>>>
>>> Long term, I NEED to change WAN network (the new network is 10x faster
>>> and the old one will be cut off)
>>>
>>> So is there a way, or I should just redo the entire installation process?
>>>
>>>
>>>
>> Personally I'd start again :-)
>>
>> Then make notes of your changes so you can back them out !!
>>
>
Thread
-
Return to April 2014
- Return to “al***e@gmail.com”
- Return to “ca***s@gmail.com”
-
Return to “John Crisp <jh***p@gmail.com>”
- 2014-04-01 (Tue, 01 Apr 2014 12:00:45 -0700) - WAN IP change - al***e@gmail.com
- 2014-04-01 (Tue, 01 Apr 2014 12:09:03 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-04 (Fri, 04 Apr 2014 07:46:28 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-04 (Fri, 04 Apr 2014 09:32:04 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-08 (Tue, 08 Apr 2014 17:46:32 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-09 (Wed, 09 Apr 2014 11:37:33 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-09 (Wed, 09 Apr 2014 15:49:26 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-10 (Thu, 10 Apr 2014 11:38:04 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-11 (Fri, 11 Apr 2014 05:51:03 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-11 (Fri, 11 Apr 2014 06:08:34 -0700) - Re: WAN IP change - ca***s@gmail.com
- 2014-04-11 (Fri, 11 Apr 2014 09:15:42 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-11 (Fri, 11 Apr 2014 09:17:24 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-11 (Fri, 11 Apr 2014 09:15:42 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-11 (Fri, 11 Apr 2014 06:08:34 -0700) - Re: WAN IP change - ca***s@gmail.com
- 2014-04-11 (Fri, 11 Apr 2014 05:51:03 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-10 (Thu, 10 Apr 2014 11:38:04 -0700) - Re: WAN IP change - al***e@gmail.com
- 2014-04-09 (Wed, 09 Apr 2014 15:49:26 -0700) - Re: WAN IP change - John Crisp <jh***p@gmail.com>
- 2014-04-09 (Wed, 09 Apr 2014 11:37:33 -0700) - Re: WAN IP change - al***e@gmail.com