On Wednesday 18 January 2017 15:09:49 Valeri Galtsev wrote:
> On Wed, January 18, 2017 4:24 am, Eliezer Croitoru wrote:
> > You could say the same thing about computers in general:
> > I hate them, they automated many tasks in life and took many jobs out of
> > the
> > market!.
>
> And they suck.
day, January 16, 2017 11:34 AM
> To: centos@centos.org
> Subject: Re: [CentOS] Reliable way of having both LAN and WIFI on headless
> box
>
> On Friday 13 January 2017 12:40:33 Gianluca Cecchi wrote:
>> On Fri, Jan 13, 2017 at 12:33 PM, Gary Stainburn
>>
>> wrote:
>&
On 01/11/2017 03:42 AM, Gary Stainburn wrote:
> On Tuesday 10 January 2017 22:20:08 Kahlil Hodgson wrote:
>> I'd be looking at your logs to see if there is any indication why the
>> wifi does not come up during boot
>>
>>> sudo journalctrl -b# current boot
>>> sudo journalctrl -b -1 # previous
[mailto:centos-boun...@centos.org] On Behalf Of Gary Stainburn
Sent: Monday, January 16, 2017 11:34 AM
To: centos@centos.org
Subject: Re: [CentOS] Reliable way of having both LAN and WIFI on headless
box
On Friday 13 January 2017 12:40:33 Gianluca Cecchi wrote:
> On Fri, Jan 13, 2017 at 12:33
On Friday 13 January 2017 12:40:33 Gianluca Cecchi wrote:
> On Fri, Jan 13, 2017 at 12:33 PM, Gary Stainburn
>
> wrote:
> > Also, it was suggested that I use nmcli in a cronjob to re-activate it if
> > it
> > drops. I can check to see if it's still active by 'grep'ing the IP
> > address,
> > but
On Fri, Jan 13, 2017 at 12:33 PM, Gary Stainburn
wrote:
>
>
> Also, it was suggested that I use nmcli in a cronjob to re-activate it if
> it
> drops. I can check to see if it's still active by 'grep'ing the IP
> address,
> but I don't know the nmcli to re-activate an existing WIFI connection.
>
On Monday 09 January 2017 16:05:16 Gary Stainburn wrote:
> Once again I am building a headless Centos 7 box that needs to reliably be
> on both the LAN and WIFI network at all times. Amongst other things it's
> going to be an AirPrint bridge enabling IPads to print to printers on a
> different VLA
On Tuesday 10 January 2017 22:20:08 Kahlil Hodgson wrote:
> I'd be looking at your logs to see if there is any indication why the
> wifi does not come up during boot
>
> > sudo journalctrl -b# current boot
> > sudo journalctrl -b -1 # previous boot
>
> Kal
Thanks for this. I'll give this a tr
On Tuesday 10 January 2017 20:59:12 Eliezer Croitoru wrote:
> NetworkManger should work pretty nice and good as required.
> Just run the right cronjob every minute to make sure the connection is up
> or down and find out if it's possible to reconnect.
> NetworkManager is kind of does all you need a
ay, January 10, 2017 11:25 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Reliable way of having both LAN and WIFI on headless
> box
>
> On Tuesday 10 January 2017 08:53:17 John R Pierce wrote:
>> On 1/9/2017 7:11 PM, fred roller wrote:
>> > On Mon, Jan 9, 2017 at 12:04
bject: Re: [CentOS] Reliable way of having both LAN and WIFI on headless
box
On Tuesday 10 January 2017 08:53:17 John R Pierce wrote:
> On 1/9/2017 7:11 PM, fred roller wrote:
> > On Mon, Jan 9, 2017 at 12:04 PM, Frank
> > Cox
> >
> > wrote:
> >> That
On Tuesday 10 January 2017 08:53:17 John R Pierce wrote:
> On 1/9/2017 7:11 PM, fred roller wrote:
> > On Mon, Jan 9, 2017 at 12:04 PM, Frank Cox
> >
> > wrote:
> >> That sounds like a weak signal from your wifi transmitter.
> >
> > Or signal interference. Where is the antennae located on the serv
On 1/9/2017 7:11 PM, fred roller wrote:
On Mon, Jan 9, 2017 at 12:04 PM, Frank Cox
wrote:
That sounds like a weak signal from your wifi transmitter.
Or signal interference. Where is the antennae located on the server? Ran
into signal issues with antennae which were tucked behind the server
On Mon, Jan 9, 2017 at 12:04 PM, Frank Cox
wrote:
> That sounds like a weak signal from your wifi transmitter.
>
Or signal interference. Where is the antennae located on the server? Ran
into signal issues with antennae which were tucked behind the server before.
___
On Mon, 9 Jan 2017 16:05:16 +
Gary Stainburn wrote:
> However, the WIFI
> link is unreliable. Sometimes it doesn't activate, or after a while
> de-activates. Sometimes it doesn't even appear in nmtui to enable me to
> activate it.
That sounds like a weak signal from your wifi transmitter.
Once again I am building a headless Centos 7 box that needs to reliably be on
both the LAN and WIFI network at all times. Amongst other things it's going
to be an AirPrint bridge enabling IPads to print to printers on a different
VLAN.
I have asked about this before and got a solution working
16 matches
Mail list logo
