Just catching up on some old emails--although there is probably no reason to
do so ;-)
On Monday 26 August 2013 12:16:10 am Robert Holtzm wrote:
On Sun, Aug 25, 2013 at 07:38:55PM -0400, Randy Kramer wrote:
On Sunday 25 August 2013 3:10:43 pm Alexander Kapshuk wrote:
Thanks for your prompt
On Wed, Aug 28, 2013 at 10:58:18PM +0100, Lisi Reisz wrote:
Yes, NM likes to do its own configuring and is apt to clash with anything
in /etc/network/interfaces.
Mmmm, apt-to-clash (-bash: apt-to-clash: command not found) :)
--
If you're not careful, the newspapers will have you hating the
On 08/26/2013 02:55 PM, Curt wrote:
On 2013-08-25, Alexander Kapshukalexander.kaps...@gmail.com wrote:
The line you suggested commenting out happens to have been commented out by
default.
Ditto here. Never touched the 'interfaces' file and it's commented out. I'm
using network
On Thu 29 Aug 2013 at 20:46:35 +0300, Alexander Kapshuk wrote:
Apologies for the delay in replying to all the posts sent in
response to my original query.
I would like to thank everyone for their input.
Turns out, the 'physical ports' option in my modem's settings
somehow got unselected,
On Monday 26 August 2013 18:15:06 Robert Holtzm wrote:
I don't use ifupdown. It seems to work well with NM when its commented
out.
Yes, NM likes to do its own configuring and is apt to clash with anything
in /etc/network/interfaces.
Lisi
--
To UNSUBSCRIBE, email to
On Sun 25 Aug 2013 at 21:16:10 -0700, Robert Holtzm wrote:
On Sun, Aug 25, 2013 at 07:38:55PM -0400, Randy Kramer wrote:
I'm not an expert at this stuff, but I believe you need that line--try
uncommenting it.
Assuming eth0 is your internet card (where you plug in your Ethernet cable
On 2013-08-25, Alexander Kapshuk alexander.kaps...@gmail.com wrote:
The line you suggested commenting out happens to have been commented out by
default.
Ditto here. Never touched the 'interfaces' file and it's commented out. I'm
using network manager (or whatever that gnome thingy is
My desktop uses wired networking. While my laptop is capable of utilizing
both wired and wireless interfaces. My modem is a TP-LINK ADSL + wireless
router.
Wired networking stopped working on both the desktop and laptop, while the
wireless networking continues to work on my laptop.
Tried using a
On 8/26/13, Alexander Kapshuk alexander.kaps...@gmail.com wrote:
My desktop uses wired networking. While my laptop is capable of utilizing
both wired and wireless interfaces. My modem is a TP-LINK ADSL + wireless
router.
Wired networking stopped working on both the desktop and laptop, while
On Mon 26 Aug 2013 at 15:28:54 +0300, Alexander Kapshuk wrote:
My desktop uses wired networking. While my laptop is capable of utilizing
both wired and wireless interfaces. My modem is a TP-LINK ADSL + wireless
router.
Wired networking stopped working on both the desktop and laptop, while the
Problem is, I can't seem to log onto the router's amin console at
192.168.1.1 from my desktop. I did manage to log onto it from my laptop
wirelessly. The DHCP server was reported as running. All the other settings
seemed OK as well.
On Aug 26, 2013 3:55 PM, Zenaan Harkness z...@freedbms.net
On 08/26/2013 04:08 PM, Brian wrote:
On Mon 26 Aug 2013 at 15:28:54 +0300, Alexander Kapshuk wrote:
My desktop uses wired networking. While my laptop is capable of utilizing
both wired and wireless interfaces. My modem is a TP-LINK ADSL + wireless
router.
Wired networking stopped working
On Mon 26 Aug 2013 at 16:45:59 +0300, Alexander Kapshuk wrote:
I'm running the Gnome desktop environment, which uses the
NetworkManager to manage the network interfaces.
1. Disable NM with
On 8/27/13, Brian a...@cityscape.co.uk wrote:
On Mon 26 Aug 2013 at 16:45:59 +0300, Alexander Kapshuk wrote:
I'm running the Gnome desktop environment, which uses the
NetworkManager to manage the network interfaces.
1. Disable NM with
update-rc.d network-manager disable
You can
On Mon, 2013-08-26 at 16:09 +0300, Alexander Kapshuk wrote:
Problem is, I can't seem to log onto the router's amin console at
192.168.1.1 from my desktop. I did manage to log onto it from my
laptop wirelessly. The DHCP server was reported as running. All the
other settings seemed OK as well.
On Mon, Aug 26, 2013 at 12:35:30PM +0100, Brian wrote:
On Sun 25 Aug 2013 at 21:16:10 -0700, Robert Holtzm wrote:
On Sun, Aug 25, 2013 at 07:38:55PM -0400, Randy Kramer wrote:
I'm not an expert at this stuff, but I believe you need that line--try
uncommenting it.
Assuming
Howdy,
Upon starting my PC, wireless networking was found to be working, but not
the wired one.
/var/log/daemon.log says DHCPv4 request timed out. Canceled DHCP
transaction.
What could be wrong here?
Thanks.
On Sun, Aug 25, 2013 at 06:27:34PM +0300, Alexander Kapshuk wrote:
Howdy,
Upon starting my PC, wireless networking was found to be working, but not
the wired one.
/var/log/daemon.log says DHCPv4 request timed out. Canceled DHCP
transaction.
What could be wrong here?
I had the same
On 8/26/13, Alexander Kapshuk alexander.kaps...@gmail.com wrote:
Howdy,
Upon starting my PC, wireless networking was found to be working, but not
the wired one.
/var/log/daemon.log says DHCPv4 request timed out. Canceled DHCP
transaction.
What could be wrong here?
Sounds like DHCP server
Thanks for your prompt response.
The line you suggested commenting out happens to have been commented out by
default.
On Aug 25, 2013 8:45 PM, Robert Holtzm hol...@cox.net wrote:
On Sun, Aug 25, 2013 at 06:27:34PM +0300, Alexander Kapshuk wrote:
Howdy,
Upon starting my PC, wireless
On Sunday 25 August 2013 3:10:43 pm Alexander Kapshuk wrote:
Thanks for your prompt response.
The line you suggested commenting out happens to have been commented out by
default.
I'm not an expert at this stuff, but I believe you need that line--try
uncommenting it.
Assuming eth0 is your
On Sun, Aug 25, 2013 at 07:38:55PM -0400, Randy Kramer wrote:
On Sunday 25 August 2013 3:10:43 pm Alexander Kapshuk wrote:
Thanks for your prompt response.
The line you suggested commenting out happens to have been commented out by
default.
I'm not an expert at this stuff, but I believe
22 matches
Mail list logo
