On Thu, Mar 22, 2018 at 02:45:07PM +, Darac Marjal wrote:
> So, what about locally-created Ethernet devices (e.g. Virtual Machine
> interfaces, or devices without a burned-in MAC address)? For these,
> you don't need to apply for your own OUI. The MAC address standard
> states that if the seco
On Thu, Mar 22, 2018 at 10:50:59AM +, David wrote:
On Thu, 2018-03-22 at 11:15 +0100, to...@tuxteam.de wrote:
On Thu, Mar 22, 2018 at 09:46:02AM +, Thomas Pircher wrote:
> On Thu, 22 Mar 2018, David wrote:
> > Does Debian keep a table of MAC addresses? If so where can I locate it?
>
> Th
On Thu, 2018-03-22 at 11:15 +0100, to...@tuxteam.de wrote:
> On Thu, Mar 22, 2018 at 09:46:02AM +, Thomas Pircher wrote:
> > On Thu, 22 Mar 2018, David wrote:
> > > Does Debian keep a table of MAC addresses? If so where can I locate it?
> >
> > The kernel does. You can get the ARP table e.g. wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 22, 2018 at 09:46:02AM +, Thomas Pircher wrote:
> On Thu, 22 Mar 2018, David wrote:
> > Does Debian keep a table of MAC addresses? If so where can I locate it?
>
> The kernel does. You can get the ARP table e.g. with
>
> ip neigh li
On Thu, 22 Mar 2018, David wrote:
> Does Debian keep a table of MAC addresses? If so where can I locate it?
The kernel does. You can get the ARP table e.g. with
ip neigh list
This table is relatively short-lived and if you haven't talked to that
device recently it might not show up in the ta
On Jo, 09 mai 13, 11:51:12, Alex Moonshine wrote:
>
> And there I was thinking about running Jessie/AMD64 on my
> soon-to-be-upgraded computer (I currently use Sid/i386).
> May using ia32-libs for 32-bit support in Jessie/Sid be a temporary
> workaround while multiarch-binnmu problems are being so
On Wed, 08 May 2013 19:57:29 +0200
Sven Joachim wrote:
> Yes, unless you use multiarch. There is still the unresolved issue
> that binNMUs break co-installability. Packages which have been
> binNMU'ed on one architecture but not on another are not
> coinstallable at all, and even those where th
Not a solution, but might I also suggest installing/running apt-listbugs?
It will go through the BTS during an upgrade. From the man page:
apt-listbugs is a tool which retrieves bug reports from the Debian
Bug
Tracking System and lists them. In particular, it is intended
to be
On 2013-05-08 19:38 +0200, Bob Proulx wrote:
> Sven Joachim wrote:
>> Bob Proulx wrote:
>> > Testing has already started to get propagation of new packages from
>> > Sid. All of the packages blocked due to the freeze were unblocked.
>> > But also all of the new packages going into Sid will be the
Sven Joachim wrote:
> Bob Proulx wrote:
> > Testing has already started to get propagation of new packages from
> > Sid. All of the packages blocked due to the freeze were unblocked.
> > But also all of the new packages going into Sid will be there ten days
> > and if no one finds any reason to st
On 2013-05-08 19:20 +0200, Bob Proulx wrote:
> Testing has already started to get propagation of new packages from
> Sid. All of the packages blocked due to the freeze were unblocked.
> But also all of the new packages going into Sid will be there ten days
> and if no one finds any reason to stop
Frank McCormick wrote:
> Sounds like a good idea. I like running bleeding-edge software but
> not if I have to spend a lot of time on the BTS :) Can I just make a
> simple change in my sources list to "testing" and wait for
> everything to catch up?
For the next two months I would run Wheezy. It
On 05/08/2013 12:40 PM, Bob Proulx wrote:
Frank McCormick wrote:
Booted up my Sid partition this morning and found the network failed
to initialize. A message during boot said something to the effect
auto lo had been declared twice in /etc/network/interfaces and then
that the same file was unrea
Frank McCormick wrote:
> Booted up my Sid partition this morning and found the network failed
> to initialize. A message during boot said something to the effect
> auto lo had been declared twice in /etc/network/interfaces and then
> that the same file was unreadable.
http://bugs.debian.org/cgi-
On 05/08/2013 10:03 AM, Frank McCormick wrote:
Booted up my Sid partition this morning and found the network failed
to initialize. A message during boot said something to the effect
auto lo had been declared twice in /etc/network/interfaces and then
that the same file was unreadable.
Wel
I have fixed the problem. I just had to type irqpoll as a kernel boot option. Does anyone know why this is?On 2/15/06, jlmb <
[EMAIL PROTECTED]> wrote:Nil Cire wrote:> Oh, the wlan0's not on there because I did not have the card plugged in.
> I have already recomplied the modules. I noticed that th
Nil Cire wrote:
> Oh, the wlan0's not on there because I did not have the card plugged in.
> I have already recomplied the modules. I noticed that the eth0 in
> 2.6.15 does not have an Rx or Tx rate while the eth0 in 2.6.12 does.
> Once again, I would like to reiterate that the route table for 2.6.
Oh, the wlan0's not on there because I did not have the card plugged in. I have already recomplied the modules. I noticed that the eth0 in 2.6.15 does not have an Rx or Tx rate while the eth0 in 2.6.12 does. Once again, I would like to reiterate that the route table for
2.6.15 is empty.
On 2/15/
> 2.6.15:
> eth0 Link encap:Ethernet HWaddr 00:D0:B7:02:C2:3D
> inet6 addr: fe80::2d0:b7ff:fe02:c23d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:
On 2/14/06, jlmb <[EMAIL PROTECTED]> wrote:
Nil Cire wrote:> Recently, I installed the new kernel package linux-image-2.6.15-1-686> for etch and found that I cannot connect to my dhcp server (router). In> grub, if I choose kernel 2.6.12, the internet and networking works just
> fine after it boots
Nil Cire wrote:
> Recently, I installed the new kernel package linux-image-2.6.15-1-686
> for etch and found that I cannot connect to my dhcp server (router). In
> grub, if I choose kernel 2.6.12, the internet and networking works just
> fine after it boots up. I'm even able to use my wireless card
On Fri, Nov 07, 2003 at 04:46:01AM +1100, Rob Weir wrote:
> On Wed, Nov 05, 2003 at 09:37:59PM +0100, Luis Fernando Llana D?az said
> > Besides, the kernel "shipped" with the installation CD (of the network
> > installation) does not losses any packet. I am disparated, as the computer is
> > new,
On Wed, Nov 05, 2003 at 09:37:59PM +0100, Luis Fernando Llana D?az said
> Besides, the kernel "shipped" with the installation CD (of the network
> installation) does not losses any packet. I am disparated, as the computer is
> new, I do not know if the problem resides in the kernel, it is a tempo
On Mon, Jul 10, 2000 at 12:37:57PM +0100, Oliver Schoenknecht wrote:
> Although the kernel (2.2.16) is compiled with network-support and
> the module for the NIC is loaded properly, I get a "connect :
> Network is unreachable"-message each time...
Insufficient data. Can you post the output of '
What do you get if you do:
ifconfig
route
Ron Rademaker
On Mon, 10 Jul 2000, Oliver Schoenknecht wrote:
> Hello everyone,
>
> I am currently building my own webserver but still I do have a
> problem with my 3com 3C900-NIC.
>
> Although the kernel (2.2.16) is compiled with network-support and
Because this I lost a Debian machine to SuSE when installing a PL
(private line). The machine with Debian doesnt ping (operation not permitted)
and when with SuSE there is no problem! And I forgot to check ipchains -L!
Quoting Geoff Mitchell ([EMAIL PROTECTED]):
> That was it (more or less)
That was it (more or less). The default input and output policies in
ipfwadm were set to deny. Thanks for the (amazingly quick) response!
Geoff
At 10:53 PM 7/3/00 -0700, you wrote:
Check if ipchains has some rule (ipchains -L).
/etc/init.d/netbase set
some rules.
Regards,
Check if ipchains has some rule (ipchains -L). /etc/init.d/netbase set
some rules.
Regards,Paulo Henrique
Quoting Geoff Mitchell ([EMAIL PROTECTED]):
> I just upgraded to the frozen version of the alpha dist on my Jensen and am
> having network problems. I can no l
>
Thanks for the insight. I ended up changing to having the drivers loaded in
the kernel and adding the append statement into the lilo.conf file. I can now
communicate with both the internal and external networks.
I also removed my networking statements from the /etc/init.d/network file and
ad
On 2000-03-02 10:59:25, Doug wrote:
> I was under the impression that the append line was used when the
> networking is built into the kernel (not in modules).
You pass config info to modules via setings in /etc/modules.conf.
Perhaps, you need to "force settings" (opposed to relaying on pnp
confi
Thanks for the reply jeff. I was under the impression that the append line was
used when the networking is built into the kernel (not in modules). Should I
add this into lilo.conf even if I am using modules?
I guess an additional question would be if I should compile the networking into
the ke
The instructions I sent were for drivers compiled into the kernel. If you
are using modules, you'll have to do something like in the Ethernet howto,
in particular, you'll prob. have to pass the IO port and IRQ...
http://www.linuxdoc.org/HOWTO/Ethernet-HOWTO-3.html
On Thu, 2 Mar 2000, Doug wrote:
Read over the Linux Network Administrators Guide, you need to pass some
parameters to the kernel to let it know that it needs to look for 2
cards. The NAG is kinda old, but that piece of it still applies:
http://www.linuxdoc.org/LDP/nag/nag.html
For instance, I have a firewall w 2 3c503 cards in
Hello!
Just wanted to apologize about these X mails I sent. M$ Outlook Express
gave me an error but still sent the mail properly, and that confused me.
Sorry!
Kind Regards,
Stephan Hachinger
--
Sent through Global Message Exchange - http://www.gmx.net
q
q
:1500 Metric:1
RX packets:0
errors:0 dropped:0 overruns:0 frame:0
TX packets:9
errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Interrupt:10 Base
address:0xfc00
Original Message Subject: Re: Network problems with
Vortex AdapterDate
:1500 Metric:1
RX packets:0
errors:0 dropped:0 overruns:0 frame:0
TX packets:9
errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Interrupt:10 Base
address:0xfc00
Original Message Subject: Re: Network problems with
Vortex AdapterDate
thanks for your response I had infact been using the same network adapter with
Debian
1.3 and it worked well the problem started with Debian version 2.0 with kernel
2.0.34.
Red Hat running the 2.0.34 kernel works fine. I will follow your suggetsions
and get
back to you with the result.
Nils-
I have had similar problems with 3c905b.
The trouble is propbably that the PCI card is in the first PCI slot, the
bios has problems reporting it to the kernel. Check the /proc/pci what irq
it has, if no irq is shown than its the PCI slot. You can either change
position of the card or turn PCI to m
Hi:
I would like to thank for all the kind responses and generous assistance
I have received on my problem regarding setting the network.
During the installation, I was asked to set the network drivers.
Initially, I thought I tried all of the 3COM drivers, and had an
impression that at least o
Hi, Vincent!
I have 3C905-TX Netowrk card. Module that one shoud is is called 3c59x
It's listed when you run modconf.
Hope that help,
Sasha.
> Hi, I'm just starting with Linux. I just installed it yesterday but I
> can't seem to get it to recognize the network. It keeps saying 'No
> network fo
Ok, sorry, but I am very new on Linux. Which program is the "Network
Setup"on Linux and in which directory is it?
Thanks
Rogerio
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscrib
[EMAIL PROTECTED] wrote:
>
> I have two PCs. A 80386 and a Pentium. They have Ethernet cards (NE
> 2000) and Windows 3.11, on the 386, and Windows 95, on Pentium. With this
> system I can share files, printers...
> Months ago, I have diveded my hard disk with fdisk to install Lin
On Sun, 17 Nov 1996, Bruce Perens wrote:
> There seems to be a bad AlterNet link between master.debian.org and Pixar.
> This might mess up mailing list service until they get it working.
Actually it is worse then that UUNET seems to have severe problems at the
moment. They confirmed >70% packet d
44 matches
Mail list logo
