28 Oct
2014
28 Oct
'14
8:32 a.m.
Thanks Brian
The internal NIC has always been a problem for me, as I had a couple of “known” devices it
was easier to disable the onboard and use what I had.
I’m happy for things to go wrong… its part of my learning experience but like most things
with Linux, I don’t have the experience to find out why something is failing.
Tom showed me the spare tyre approach to getting RIP running and so I took that rather
than trying to work out where the real issues were. My “conflict” with RIP44d has gone
away now that I’m running ampr-ripd but accept the whole things could start again on the
next upgrade.
I’m back up and running again having learn’t more about RIP, OpenVPN and IPTables so its
not all bad :-)
Andy
On 28 Oct 2014, at 13:01, Brian <n1uro(a)n1uro.ampr.org> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Andy;
On Tue, 2014-10-28 at 11:30 +0000, Andy Brittain wrote:
My conflict was driven by problems with the
onboard NIC and OpenVPN.
Having rebuilt everything and disabling the onboard NIC everything worked fine until I
installed OpenVPN at which point I started to get reboot hangs.
That's almost like saying the following:
"I blew a tire in my car, so I shifted the weight so that the rim
doesn't touch the road."
While you may be fortunate and have a smooth road to drive on, sooner or
later you're going to hit a bump on the other side and that rim will
touch... aka: your pc may lock. You may wish to verify proper driver for
your internal NIC is correct and current.
Keep in mind this: one big difference between windows and linux is that
windows does hardware read/writes via bios, Linux does them direct to
the devices themselves. As I test, I've taken CDRW units that began to
fail under NERO and other cd burning softwares on windows and then used
the same physical device under linux, which always created the CD.
Hopefully for you, the system will become more stable for you now.
--
If Microsoft intended Windows to be for ham usage,
they would have incorporated our protocols into their kernel.
73 de Brian Rogers - N1URO
email: <n1uro(a)n1uro.ampr.org>
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, Pennsylvania,
Rhode Island, and Vermont.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net