Re: Network Problems
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 second-least-significant bit of the first octet is > 1, then the whole MAC address is "locally administered". Thus, if your > MAC address starts with "x2", "x6", "xA" or "xE" (where x is any > digit), then it is locally-adminsitered and, in theory, it is up to > you to ensure uniqueness (at least, unique within the boundary of your > Ethernet domain). Also x3, x7, xB and xF - but those should only be used for multicast addressing. Cheers, Tom -- Who messed with my anti-paranoia shot? signature.asc Description: Digital signature
Re: Network Problems
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? > > The kernel does. You can get the ARP table e.g. with > > ip neigh list There's also the arp (8) command: you can query and manipulate the ARP table (arp stands for "address resolution protocol", which is tasked with keeping this MAC -- IP mapping up to date). For example, just typing "sudo arp" will show you a list of known IP Address to MAC address mappings. With "arp -s " you can set one such mappings. And so on. Cheers -- tomás Thank you to Thomas and Tomas for replying. I think as Thomas stated it's a router problem, I've been looking at what the various routers are storing and not found a problem to date. I suspect that allocating random MAC addresses is the problem and I need to find out what I can allocate without causing problems. There must be some rules somewhere, I suspect the Arduino uses a block of addresses and I've duplicated something. MAC addresses follow a set format. They are 6 bytes long: the first 3 bytes is the Organisationally Unique Identifier (OUI), the second 3 bytes are the NIC specific identifier. Typically, MAC addresses are set by the manufacturer of the Ethernet device. Each manufacturer is allocated one or more OUIs. They are free to allocate the last three bytes however they like, so long as they remain unique within the organisation. So Intel can produce a device with 12:34:56 as the last three bytes, and so can Netgear, but once combined with the OUI, the whole *should* be globally unique. 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 second-least-significant bit of the first octet is 1, then the whole MAC address is "locally administered". Thus, if your MAC address starts with "x2", "x6", "xA" or "xE" (where x is any digit), then it is locally-adminsitered and, in theory, it is up to you to ensure uniqueness (at least, unique within the boundary of your Ethernet domain). David. -- For more information, please reread. signature.asc Description: PGP signature
Re: Network Problems
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. with > > > > ip neigh list > > There's also the arp (8) command: you can query and manipulate > the ARP table (arp stands for "address resolution protocol", which > is tasked with keeping this MAC -- IP mapping up to date). > > For example, just typing "sudo arp" will show you a list of known > IP Address to MAC address mappings. With "arp -s " you > can set one such mappings. And so on. > > Cheers > -- tomás Thank you to Thomas and Tomas for replying. I think as Thomas stated it's a router problem, I've been looking at what the various routers are storing and not found a problem to date. I suspect that allocating random MAC addresses is the problem and I need to find out what I can allocate without causing problems. There must be some rules somewhere, I suspect the Arduino uses a block of addresses and I've duplicated something. David.
Re: Network Problems
-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 list There's also the arp (8) command: you can query and manipulate the ARP table (arp stands for "address resolution protocol", which is tasked with keeping this MAC -- IP mapping up to date). For example, just typing "sudo arp" will show you a list of known IP Address to MAC address mappings. With "arp -s " you can set one such mappings. And so on. Cheers - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlqzglkACgkQBcgs9XrR2kai7wCdH863goBZDFtVIFpJeqVoHxEu 3/4An1ELnMKk9e8y8FBo3Xr9ZZ6022A8 =FwQH -END PGP SIGNATURE-
Re: Network Problems
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 table. Another place you could look for MAC addresses is your router. Most routers keep a table of MAC addresses which is a bit longer-lived than the ARP table on a host, because they need to hand out IP addresses over DHCP and need to remember the MAC-IP combination for some time. Thomas
Network Problems
Dear Group, I'm having some network issues where I have several Arduino's on my network and I may have given two of them the same MAC address. Does Debian keep a table of MAC addresses? If so where can I locate it? It could of course be my browser that is keeping this table, I'm using PaleMoon. David.
Solved : Upgrade to Jessie : some network problems
Le Mon, 4 May 2015 11:52:18 +0200, Petter Adsen pet...@synth.no a écrit : Are you sure you might not have gotten a different IP address after the upgrade? And what does the line for /mnt/nfssave in /etc/fstab on the client and the appropriate line in /etc/exports on the server say? That solved the trick :-( I had static IPs on all my network, so I thought the updgrade to Jessie would keep it this way. But I have two wifi routeurs on my network that provide DHCP to the wifi net, and clearly ALSO on the wired net. Thank you for pointing me on this one, I was starting to become crazy ;-) \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505151540.3a767...@gaston.baronie.vez
Re: Upgrade to Jessie : some network problems
On Sun, 3 May 2015 16:24:43 +0200 Nicolas FRANCOIS nicolas.franc...@free.fr wrote: Hi. After upgrading from Wheezy to Jessie, I have a few networking problems : - I had a clear HiID on aMule before, now I get a LowID. I don't know why, I only upgraded my desktop, my router/firewall is an ipFire box transferring the correct ports to my client. It's not really important, but I'd like to understand what's going on. - I had trouble with my NFS and SMB mounts on a wheezy NAS. I couldn't mount them anymore : $ sudo mount /mnt/nfssave mount.nfs: access denied by server while mounting $ sudo mount /mnt/smbshare/ mount: mauvais type de système de fichiers, option erronée, superbloc erroné sur //192.168.10.84/partage, page de code ou programme auxiliaire manquant, ou autre erreur (pour plusieurs système de fichiers (NFS ou CIFS par exemple), un programme /sbin/mount.type auxiliaire pourrait être nécessaire) I solved the SMB problem by updating my NAS box and installing smb-utils, but I still can't mount the NFS share. No indication on ANY log from the server when I try to mount it, nothing has changed in the configuration... Can you help me, especially on the NFS problem ? Or point me to what I could do to debug all this ? Are you sure you might not have gotten a different IP address after the upgrade? And what does the line for /mnt/nfssave in /etc/fstab on the client and the appropriate line in /etc/exports on the server say? Also try running mount with -v. Petter -- I'm ionized Are you sure? I'm positive. pgpWh9HC6BhLJ.pgp Description: OpenPGP digital signature
Upgrade to Jessie : some network problems
Hi. After upgrading from Wheezy to Jessie, I have a few networking problems : - I had a clear HiID on aMule before, now I get a LowID. I don't know why, I only upgraded my desktop, my router/firewall is an ipFire box transferring the correct ports to my client. It's not really important, but I'd like to understand what's going on. - I had trouble with my NFS and SMB mounts on a wheezy NAS. I couldn't mount them anymore : $ sudo mount /mnt/nfssave mount.nfs: access denied by server while mounting $ sudo mount /mnt/smbshare/ mount: mauvais type de système de fichiers, option erronée, superbloc erroné sur //192.168.10.84/partage, page de code ou programme auxiliaire manquant, ou autre erreur (pour plusieurs système de fichiers (NFS ou CIFS par exemple), un programme /sbin/mount.type auxiliaire pourrait être nécessaire) I solved the SMB problem by updating my NAS box and installing smb-utils, but I still can't mount the NFS share. No indication on ANY log from the server when I try to mount it, nothing has changed in the configuration... Can you help me, especially on the NFS problem ? Or point me to what I could do to debug all this ? Thank you. \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150503162443.202b0...@gaston.baronie.vez
How to handle network problems
Networking inside some VM's was so slow as to be non-functional; I finally found https://bugzilla.redhat.com/show_bug.cgi?id=855640, which suggested (note 11) ethtool -K eth0 gro off With that change, everything worked well, except that speedtest.net was not able to connect for the upload speed test. So I'm not sure if the problem is completely fixed. If anyone has suggestions about diagnosing or solving the problem, that would be great. I am also wondering if I should let someone know about this problem since the solution is really just a work-around. I'm not sure if the real problem is with the virtio drivers, the hardware network drivers, the bridging code, kvm, I had the problem with a Windows 7 VM (with RedHat's virtio drivers), but there are reports of similar trouble with Linux guests. There is also a very similar report with newer kernels (http://askubuntu.com/questions/503863/poor-upload-speed-in-kvm-guest-with-virtio-eth-driver-in-openstack-on-3-14 and references from there), but since that is reported as a regression it may be different. The vm is running under KVM under libvirt, via virt-manager. Using bridged networking from libvirt and virtio from inside the VM. Thanks. Ross Boylan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cak3ntrcy4toh0uq2116ismpwd_0bjxfigyfesmk7zbedsm3...@mail.gmail.com
Re: network problems
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 sorted out? Already since wheezy ia32-libs doesn't do what you think it does. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: network problems
On Wed, 08 May 2013 19:57:29 +0200 Sven Joachim svenj...@gmx.de 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 the version is the same, /usr/share/doc/$package/changelog.Debian.gz differs across architectures, making it necessary to use dpkg's --force-overwrite option. I don't expect this to be fixed anytime soon, so if you are on amd64 and want to run wine, skype or other 32-bit software, you had better stay on Wheezy. 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 sorted out? BW, Alex -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130509115112.4acfbffa@moonpc
network problems
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. Snooping around I commented out what appeared to be the only auto lo line. This is what the file looks like now: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface #auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp I followed this with ifup etho and the network came up. What I find strange is there didn't seem to be two lines declaring auto lo and that commenting out the only line I found solved the problem. These are the changes apt-get made yesterday before this problem surfaced..but to me it doesn't seem any of the packages would change networking Will install 36 packages, and remove 2 packages. 55.7 MB of disk space will be used === [INSTALL, DEPENDENCIES] libdrm-dev:i386 [INSTALL, DEPENDENCIES] libegl1-mesa:i386 [INSTALL, DEPENDENCIES] libegl1-mesa-dev:i386 [INSTALL, DEPENDENCIES] libegl1-mesa-drivers:i386 [INSTALL, DEPENDENCIES] libgbm1:i386 [INSTALL, DEPENDENCIES] libkms1:i386 [INSTALL, DEPENDENCIES] libopenvg1-mesa:i386 [INSTALL, DEPENDENCIES] libprocps1:i386 [INSTALL, DEPENDENCIES] libwayland0:i386 [INSTALL, DEPENDENCIES] libxcb-glx0-dev:i386 [INSTALL, DEPENDENCIES] libxtables10:i386 [INSTALL, DEPENDENCIES] libxxf86vm-dev:i386 [INSTALL, DEPENDENCIES] x11proto-dri2-dev:i386 [INSTALL, DEPENDENCIES] x11proto-gl-dev:i386 [INSTALL, DEPENDENCIES] x11proto-xf86vidmode-dev:i386 [REMOVE, DEPENDENCIES] linux-image-686:i386 [REMOVE, DEPENDENCIES] linux-image-686-pae:i386 [UPGRADE] firmware-linux:i386 0.36+wheezy.1 - 0.38 [UPGRADE] firmware-linux-nonfree:i386 0.36+wheezy.1 - 0.38 [UPGRADE] gir1.2-networkmanager-1.0:i386 0.9.4.0-10 - 0.9.8.0-3 [UPGRADE] initramfs-tools:i386 0.109.1 - 0.112 [UPGRADE] iptables:i386 1.4.16.3-4 - 1.4.18-1 [UPGRADE] libcairo-gobject2:i386 1.12.2-3 - 1.12.14-2 [UPGRADE] libcairo-script-interpreter2:i386 1.12.2-3 - 1.12.14-2 [UPGRADE] libcairo2:i386 1.12.2-3 - 1.12.14-2 [UPGRADE] libcairo2-dev:i386 1.12.2-3 - 1.12.14-2 [UPGRADE] libgmp10:i386 2:5.0.5+dfsg-2 - 2:5.1.1+dfsg-3 [UPGRADE] libgmpxx4ldbl:i386 2:5.0.5+dfsg-2 - 2:5.1.1+dfsg-3 [UPGRADE] libnm-glib-vpn1:i386 0.9.4.0-10 - 0.9.8.0-3 [UPGRADE] libnm-glib4:i386 0.9.4.0-10 - 0.9.8.0-3 [UPGRADE] libnm-util2:i386 0.9.4.0-10 - 0.9.8.0-3 [UPGRADE] liborc-0.4-0:i386 1:0.4.16-2 - 1:0.4.17-2 [UPGRADE] libraw1394-11:i386 2.0.9-1 - 2.1.0-1 [UPGRADE] libtar0:i386 1.2.16-1 - 1.2.19-1 [UPGRADE] libvdpau1:i386 0.4.1-8 - 0.6-2 [UPGRADE] procps:i386 1:3.3.4-2 - 1:3.3.6-1 [UPGRADE] python:i386 2.7.3-4 - 2.7.3-5 [UPGRADE] python-minimal:i386 2.7.3-4 - 2.7.3-5 === Can anyone provide any insight ? -- Cheers Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/518a5b4f.2070...@videotron.ca
Re: network problems
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. Well it seems a bug in IFUPDOWN was responsible. Thankfully, it's been fixed and we're back in business. -- Cheers Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/518a7c52.8050...@videotron.ca
Re: network problems
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-bin/bugreport.cgi?bug=707052 There were two different bugs. Here is the entire set: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707041 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707048 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707048 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707052 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707054 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707092 These are the changes apt-get made yesterday before this problem surfaced..but to me it doesn't seem any of the packages would change networking Somewhere along the way you upgraded 'ifupdown' from 0.7.8 that it had been to 0.7.41 or 0.7.42. Can anyone provide any insight ? Yes. Now that Wheezy has released Sid is once again very Unstable. The last year that Sid has been frozen has made Sid relatively stable. But now the floodgates are open again and everyone is pushing changes, sometimes untested changes, into Sid again. For the next few months it will be exceptionally rough there as a year's worth of pending disruptive changes are pushed through. If you are using Sid then you must be able to track problems in the BTS and be able to use snapshot.debian.org to recover previous versions of packages and return to them as bugs appear. You might consider using Testing Jessie instead as it will be somewhat insulated from the thrash in Unstable Sid. Let the calamity begin! Bob signature.asc Description: Digital signature
Re: network problems
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 unreadable. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707052 There were two different bugs. Here is the entire set: //snip// Yes. Now that Wheezy has released Sid is once again very Unstable. The last year that Sid has been frozen has made Sid relatively stable. But now the floodgates are open again and everyone is pushing changes, sometimes untested changes, into Sid again. For the next few months it will be exceptionally rough there as a year's worth of pending disruptive changes are pushed through. If you are using Sid then you must be able to track problems in the BTS and be able to use snapshot.debian.org to recover previous versions of packages and return to them as bugs appear. You might consider using Testing Jessie instead as it will be somewhat insulated from the thrash in Unstable Sid. Let the calamity begin! Bob 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? I have run Sid for years and it **seems** that it wasn't this disruptive ? (see my other message about apt-get wanting to purge gedit and rhythmbox etc) -- Cheers Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/518a84f1.9040...@videotron.ca
Re: network problems
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 just released. It will be very similar to the Sid of just before that time. deb http://ftp.us.debian.org/debian wheezy main deb http://ftp.us.debian.org/debian wheezy-updates main deb http://security.debian.org/ wheezy/updates main 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 it then they will flow into Testing. So in about ten days Testing will get a large impulse spike of new packages. Therefore I would wait out the instability in Testing Jessie by sticking with Wheezy and getting security upgrades from it. I would sit there for... oh... say... two months. By then things should have settled down. Then you could move back to Testing. deb http://ftp.us.debian.org/debian jessie main deb http://security.debian.org/ jessie/updates main I have run Sid for years and it **seems** that it wasn't this disruptive ? (see my other message about apt-get wanting to purge gedit and rhythmbox etc) Human memory is a funny thing. It isn't really very good at these things. What you should do is keep track of it in a journal. Memory is usually fault. Instead write down every time you have a problem. Keep a record. If you do that then you will find that there are waves of problems that come and go. I have been keeping record of my problems since 2011-04-03. From then through 2011 I had 41 problems in sid. That was half a year when Sid was active and unfrozen. In all of 2012 I had 37 problems. That was when Sid was frozen and the freeze definitely reduced the number of problems in Sid. So far in 2013 I have had 5 problems but the year is young and things are no longer frozen. Bob signature.asc Description: Digital signature
Re: network problems
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 it then they will flow into Testing. So in about ten days Testing will get a large impulse spike of new packages. No, it won't because a new eglibc version was uploaded to sid, and it seems all newly built packages are going to depend on it. And since eglibc does not even build on kfreebsd, it's going to be a while before it will go into testing. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87txmdxtuq@turtle.gmx.de
Re: network problems
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 stop it then they will flow into Testing. So in about ten days Testing will get a large impulse spike of new packages. No, it won't because a new eglibc version was uploaded to sid, and it seems all newly built packages are going to depend on it. And since eglibc does not even build on kfreebsd, it's going to be a while before it will go into testing. Good to know about the eglibc transition. You say it. Is that referring to all of the newly uploaded packages? I am uncertain what you are referring to here. I think it referred to too many different things all at once. :-) I think you might mean that it is eglibc and eglibc won't move to Testing until it is debugged on kfreebsd. And all new uploads will be blocked behind eglibc. So when the eglibc transition completes then at that time there will be an even larger impulse spike in Testing when those packages are finally allowed to transition to Testing. In which case Testing would be a reasonably good place to be *until* the day before the new eglibc transitions to it. And then people might want to avoid testing through the impulse spike of the packages waiting behind it moving into Testing. Then after that time it would return to being quite okay again. That is my tea-leaf reading interpretation of the future anyway. :-) Bob signature.asc Description: Digital signature
Re: network problems
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 there ten days and if no one finds any reason to stop it then they will flow into Testing. So in about ten days Testing will get a large impulse spike of new packages. No, it won't because a new eglibc version was uploaded to sid, and it seems all newly built packages are going to depend on it. And since eglibc does not even build on kfreebsd, it's going to be a while before it will go into testing. Good to know about the eglibc transition. You say it. Is that referring to all of the newly uploaded packages? I am uncertain what you are referring to here. I think it referred to too many different things all at once. :-) I think you might mean that it is eglibc and eglibc won't move to Testing until it is debugged on kfreebsd. And all new uploads will be blocked behind eglibc. Yes, that's what I meant. Sorry for being unclear. So when the eglibc transition completes then at that time there will be an even larger impulse spike in Testing when those packages are finally allowed to transition to Testing. In which case Testing would be a reasonably good place to be *until* the day before the new eglibc transitions to it. And then people might want to avoid testing through the impulse spike of the packages waiting behind it moving into Testing. Then after that time it would return to being quite okay again. 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 the version is the same, /usr/share/doc/$package/changelog.Debian.gz differs across architectures, making it necessary to use dpkg's --force-overwrite option. I don't expect this to be fixed anytime soon, so if you are on amd64 and want to run wine, skype or other 32-bit software, you had better stay on Wheezy. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877gj9xsl2@turtle.gmx.de
Re: network problems
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 invoked before each upgrade by apt, or other similar package managers, in order to check whether the upgrade/installation is safe. It's a nice way to thumbnail what might get broken in the upgrade, and you can hold packages and restart the upgrade. --b On Wed, May 8, 2013 at 1:01 PM, Frank McCormick debianl...@videotron.cawrote: 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 unreadable. http://bugs.debian.org/cgi-**bin/bugreport.cgi?bug=707052http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707052 There were two different bugs. Here is the entire set: //snip// Yes. Now that Wheezy has released Sid is once again very Unstable. The last year that Sid has been frozen has made Sid relatively stable. But now the floodgates are open again and everyone is pushing changes, sometimes untested changes, into Sid again. For the next few months it will be exceptionally rough there as a year's worth of pending disruptive changes are pushed through. If you are using Sid then you must be able to track problems in the BTS and be able to use snapshot.debian.org to recover previous versions of packages and return to them as bugs appear. You might consider using Testing Jessie instead as it will be somewhat insulated from the thrash in Unstable Sid. Let the calamity begin! Bob 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? I have run Sid for years and it **seems** that it wasn't this disruptive ? (see my other message about apt-get wanting to purge gedit and rhythmbox etc) -- Cheers Frank -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.**debian.orgdebian-user-requ...@lists.debian.orgwith a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/**518a84f1.9040...@videotron.cahttp://lists.debian.org/518a84f1.9040...@videotron.ca
apt-get network problems
I'm having a lot of trouble with the apt-get update process. I keep getting errors trying to update the packages. Most of this seems to hang on ftp.us.debian.org. Which I am begining to suspect is an alias for mirrors as I'm finding network IP traffic to different debian mirrors other than those I care to identify in my apt/source.list file. Unfortunately they are having a lot of failures in closing out the synchronization. This is also showing up in my firewall rulesets with errors like: Nov 13 14:18:32 cling kernel: MISSED:IN= OUT=eth0 SRC=192.168.0.5 DST=128.101.240.212 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=53069 DF PROTO=TCP SPT=45028 DPT=80 WINDOW=4501 RES=0x00 ACK PSH FIN URGP=0 Is anyone else experiencing problems with updating they debian package libraries? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Network problems after system recovery
Hi list, I just duplicated my system onto a Thinkpad T40 like this: - used netinst to install a base etch system, - used a generated list of installed packages from my old (dying) machine to install all the same packages, - compiled an extra kernel from Debian sources using my old kernel config with a couple of changes for the different hardware, - then copied over all my backed up data and some config files. Foolproof, right? Well, nearly...the main problem is networking, which is not my strong suit, so I'm hoping for a couple of tips. On the old machine, NetworkManager worked beautifully; once I had commented out all but the loopback interface from /etc/network/interfaces, it took care of everything - with KNetworkManager, it would automatically connect to a wired interface if plugged in, or to an open wireless network, asking me for an appropriate key or passphrase if required. During the netinstall and package installations, the wired ethernet connection worked automatically with the e100 module and DHCP. But now the installation is complete, there is a complex bundle of problems: - with NetworkManager: - Wired ethernet is claimed to be connected, sometimes reporting a 169.* ip address, in which case pinging the router fails, or a 192.* address, in which case the router can be pinged; in both cases I cannot connect to the internet, even using numerical addresses. NetworkManager reports: NetworkManager: information DHCP returned name servers but system has disabled dynamic modification! -Wireless connection using wpa_supplicant fails, with this output: NetworkManager: debug info [1157879555.879241] [snip] NetworkManager: information SUP: sending command 'INTERFACE_ADD wireless wext /var/run/wpa_supplicant ' ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported NetworkManager: information SUP: response was '' NetworkManager: WARNING nm_utils_supplicant_request_with_check (): supplicant_interface_init: supplicant error for 'INTERFACE_ADD wireless wext /var/run/wpa_supplicant '. Response: '' NetworkManager: WARNING real_act_stage2_config (): Activation (wireless/wireless): couldn't connect to the supplicant. NetworkManager: information Activation (wireless) failed for access point (default) NetworkManager: information Activation (wireless) failed. NetworkManager: information Deactivating device wireless. NetworkManager: information Activation (wireless) failure scheduled... NetworkManager: information Activation (wireless) Stage 2 of 5 (Device Configure) complete. ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 7 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 4 value 0x0 - ] - If I re-establish my interfaces file and use ifupdown: - Wired ethernet with DHCP fails with: DHCPDISCOVER on ethernet to 255.255.255.255 port 67 interval 4 send_packet: Message too long; or with a static setup, it doesn't enable browsing. - Wireless works, but not with wpa_supplicant. Uses DHCP and the airo module. AFAIKT (which is not very) this means that there are at least two problems: DHCP has stopped working for the ethernet interface - presumably because of some installed program - and wpa_supplicant is not working for the wireless interface. Any pointers as to how to begin solving these problems would be greatly appreciated. Thanks, John
Re: network problems specific to linux-image-2.6.15-1-686 (SOLVED)
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 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.I don't think the route table has anything to do with dhclient notworking but the other way around. dhclient not working is the reason theroute table is empty.Have you try with a static network configuration? jorge--To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]-- Eric Lin My public key is at www.keyserver.net . Switch to Dvorak will expire on August 14, 2006Typed on Dvorak. Switch to the Dvorak Keyboard Layout. Faster. Easier. Better.Choose Linux. Always on Target.
Re: network problems specific to linux-image-2.6.15-1-686
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:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) You need to recompile the ndiswrapper module for the new kernel. I recommend using package: module-assistant. Note that your wireless device isn't detected. As far as eth0, I'm not quite sure what's going on since the device appears to be working. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: network problems specific to linux-image-2.6.15-1-686
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.15does 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/06, jlmb [EMAIL PROTECTED] wrote: 2.6.15: eth0Link encap:EthernetHWaddr 00:D0:B7:02:C2:3D inet6 addr: fe80::2d0:b7ff:fe02:c23d/64 Scope:Link UP BROADCAST RUNNING MULTICASTMTU:1500Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b)TX bytes:0 (0.0 b)You need to recompile the ndiswrapper module for the new kernel. Irecommend using package: module-assistant. Note that your wirelessdevice isn't detected. As far as eth0, I'm not quite sure what's going on since the deviceappears to be working.--To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]-- Eric Lin My public key is at www.keyserver.net. Switch to Dvorak will expire on August 14, 2006Typed on Dvorak. Switch to the Dvorak Keyboard Layout. Faster. Easier. Better.Choose Linux. Always on Target.
Re: network problems specific to linux-image-2.6.15-1-686
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.15 is empty. I don't think the route table has anything to do with dhclient not working but the other way around. dhclient not working is the reason the route table is empty. Have you try with a static network configuration? jorge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
network problems specific to linux-image-2.6.15-1-686
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 in 2.6.12 with no problems. It seems like the kernel cannot detect the network interfaces or something because when I run dhclient eth0, I just keep on seeing multiple dhcprequests. Even with a lot of tries, I am never able to recieve a dhcpoffer. I tried typing route to see if the kernel route tables had my network in them but they were empty. Back in 2.6.12, typing route would give me something. Thanks for any help.--Eric Lin Typed on Dvorak. Switch to the Dvorak Keyboard Layout. Faster. Easier. Better.Choose Linux. Always on Target.
Re: network problems specific to linux-image-2.6.15-1-686
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 in 2.6.12 with no problems. It seems like the kernel cannot detect the network interfaces or something because when I run dhclient eth0, I just keep on seeing multiple dhcprequests. Even with a lot of tries, I am never able to recieve a dhcpoffer. I tried typing route to see if the kernel route tables had my network in them but they were empty. Back in 2.6.12, typing route would give me something. Thanks for any help. -- Eric Lin Typed on Dvorak. Switch to the Dvorak Keyboard Layout. Faster. Easier. Better. Choose Linux. Always on Target. Which modules do your NIC and wireless card use? Run ifconfig with both kernels and provide us that information. jorge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: network problems specific to linux-image-2.6.15-1-686
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 up. I'm even able to use my wireless card in 2.6.12 with no problems.It seems like the kernel cannot detect the network interfaces or something because when I run dhclient eth0, I just keep on seeing multiple dhcprequests. Even with a lot of tries, I am never able to recieve a dhcpoffer. I tried typing route to see if the kernel route tables had my network in them but they were empty. Back in 2.6.12, typing route would give me something. Thanks for any help. -- Eric Lin Typed on Dvorak. Switch to the Dvorak Keyboard Layout. Faster. Easier. Better. Choose Linux. Always on Target.Which modules do your NIC and wireless card use? ndiswrapper for the wireless card, NIC uses e_100 or somehing Run ifconfig with both kernels and provide us that information. Here's the ifconfig output: On the 2.6.12: eth0 Link encap:Ethernet HWaddr 00:D0:B7:02:C2:3D inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2d0:b7ff:fe02:c23d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:119 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:31542 (30.8 KiB) TX bytes:1062 (1.0 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3060 (2.9 KiB) TX bytes:3060 (2.9 KiB) wlan0 Link encap:Ethernet HWaddr 00:0D:0B:0C:2F:72 inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20d:bff:fe0c:2f72/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:153 errors:0 dropped:0 overruns:0 frame:0 TX packets:59 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44953 (43.8 KiB) TX bytes:7293 (7.1 KiB) Interrupt:11 Memory:842-8422000 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:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2540 (2.4 KiB) TX bytes:2540 (2.4 KiB) jorge-- Eric Lin Typed on Dvorak. Switch to the Dvorak Keyboard Layout. Faster. Easier. Better.Choose Linux. Always on Target.
Re: Newbie Network Problems
Roger Creasy said: Hello: I am trying to connect a Debian machine to my home network. I have one windows xp box and 2 Debian machines. What do I have to do to be able to share files and browse from any of the three machines to any other of the three? WinXP shares some folders by default, I believe anything in the shared documents directory should be accessable as a SMB share with no additional configuration. To share from your linux machines you'll have to setup Samba or NFS, although Samba is more than capable of serving files for Linux machines. I've got it setup on my server at home using the CIFS filesystem because I transfer large files (DVD Rips) to and from the server on a regular basis. The Samba howto is very good. http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/ -- - Josh www.omg-stfu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Newbie Network Problems
Hello: I am trying to connect a Debian machine to my home network. I have one windows xp box and 2 Debian machines. What do I have to do to be able to share files and browse from any of the three machines to any other of the three? TIA Roger
Re: Newbie Network Problems
On Sat, Sep 24, 2005 at 07:05:15PM -0400, Roger Creasy wrote: Hello: I am trying to connect a Debian machine to my home network. I have one windows xp box and 2 Debian machines. What do I have to do to be able to share files and browse from any of the three machines to any other of the three? Take a look at samba. NFS would do for just the debian boxes. Grtz, ,Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weirdest network problems of my ilfe
[EMAIL PROTECTED] schreef: Hi, Ok after installing the new router that came w/ my dsl i'm having the most mind-boggling internet problems of my life. Here's some background on my network: +Linux box |Linux laptop (wireless) Wireless/Wired Router/Modem+Windows box #1 |Windows laptop +Windows laptop (wireless) Ok, so first off... all of my family's windows boxes are working fine. Everything is just normal. The linux boxen however, have problems. Internet generally works (although some sites (slashdot, gmail, etc) won't load in firefox (for some reason they will in links). I can't connect to yahoo/jabber/msn/etc w/ gaim, but i can w/ centericq. I've been trying to figure out all this for forever and so i tried to tcptraceroute my way to messenger.hotmail.com as an experiment (on port 1863 or whatever it was). It took a while, but the route was traced. The funny thing is that if i start tracing the route, and then start up gaim, i connect just fine. same goes for the sites that didn't load up in my browser... I can't figure out why everything works on the windows, but not on my linux boxen. the network stuff is all assigned by the router (dhcp). What should i do? Can it be a problem with ECN? You could try to disable it and see if it works better that way. echo 0 /proc/sys/net/ipv4/tcp_ecn Google for more info; one link I found is http://answerpointe.cctec.com/maillists/nanog/historical/0104/msg00714.html -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weirdest network problems of my ilfe [SOLVED]
Hey thanks for everyone's responses... i'm still not 100% sure what the problem ended up being, but this is what i did (this was thanks to some submissions on the list, #debian, and trial and error). The lowering of the MTU explanation made the most sense to me, but it didn't actually do anything differently. I messed around w/ many other settings and got ready to yell at my isp (but i really really hate talking to the customer support people). Anyway, someone recommended releasing my DHCP information and then getting another address. That didn't make a difference, but i figured since it was taking sooo long to tcptraceroute my way back to various places something had to be up w/ the DNS. My /etc/resolv.conf had the 192.168.0.1 and xx.xx.3.65 (i can't remember the number exactly, just the last two octets). I heard someone tell me some of those routers are pretty screwy so i deleted the line w/ 192.168.0.1 and tried tcptraceroute again... much faster this time, and then everything else worked too. Still not sure what exactly is up, because i had tried deleting that line before w/ no effect. But maybe it really was necessary to release my dhcp lease also (i don't understand why that would make a difference... could someone explain why? or am i just confused?). Anyway, it's nice that everything's working again. Cameron Matheson P.S. Yesterday i was trying to figure out why the windoze boxen would work when the linux boxen wouldn't (they also have 192.168.0.1 as one of their dns servers). The only thing i could think of is i thought at one time i had heard that windows boxen alternate which dns server they use every time they send out a request, whereas Linux tries to always use the primary. Is that plausible? [EMAIL PROTECTED] wrote: Hi, Ok after installing the new router that came w/ my dsl i'm having the most mind-boggling internet problems of my life. Here's some background on my network: +Linux box |Linux laptop (wireless) Wireless/Wired Router/Modem+Windows box #1 |Windows laptop +Windows laptop (wireless) Ok, so first off... all of my family's windows boxes are working fine. Everything is just normal. The linux boxen however, have problems. Internet generally works (although some sites (slashdot, gmail, etc) won't load in firefox (for some reason they will in links). I can't connect to yahoo/jabber/msn/etc w/ gaim, but i can w/ centericq. I've been trying to figure out all this for forever and so i tried to tcptraceroute my way to messenger.hotmail.com as an experiment (on port 1863 or whatever it was). It took a while, but the route was traced. The funny thing is that if i start tracing the route, and then start up gaim, i connect just fine. same goes for the sites that didn't load up in my browser... I can't figure out why everything works on the windows, but not on my linux boxen. the network stuff is all assigned by the router (dhcp). What should i do? Thanks, Cameron Matheson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weirdest network problems of my ilfe [SOLVED]
On 9/16/05, Cameron Matheson [EMAIL PROTECTED] wrote: P.S. Yesterday i was trying to figure out why the windoze boxen would work when the linux boxen wouldn't (they also have 192.168.0.1 as one of their dns servers). The only thing i could think of is i thought at one time i had heard that windows boxen alternate which dns server they use every time they send out a request, whereas Linux tries to always use the primary. Is that plausible? Since you've narrowed it down to your router, you may want to see if there's a firmware upgrade for it. -- Jiann-Ming Su I have to decide between two equally frightening options. If I wanted to do that, I'd vote. --Duckman
weirdest network problems of my ilfe
Hi, Ok after installing the new router that came w/ my dsl i'm having the most mind-boggling internet problems of my life. Here's some background on my network: +Linux box |Linux laptop (wireless) Wireless/Wired Router/Modem+Windows box #1 |Windows laptop +Windows laptop (wireless) Ok, so first off... all of my family's windows boxes are working fine. Everything is just normal. The linux boxen however, have problems. Internet generally works (although some sites (slashdot, gmail, etc) won't load in firefox (for some reason they will in links). I can't connect to yahoo/jabber/msn/etc w/ gaim, but i can w/ centericq. I've been trying to figure out all this for forever and so i tried to tcptraceroute my way to messenger.hotmail.com as an experiment (on port 1863 or whatever it was). It took a while, but the route was traced. The funny thing is that if i start tracing the route, and then start up gaim, i connect just fine. same goes for the sites that didn't load up in my browser... I can't figure out why everything works on the windows, but not on my linux boxen. the network stuff is all assigned by the router (dhcp). What should i do? Thanks, Cameron Matheson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weirdest network problems of my ilfe
On Thu, Sep 15, 2005 at 06:36:17PM -0600, [EMAIL PROTECTED] wrote: Hi, Ok after installing the new router that came w/ my dsl i'm having the most mind-boggling internet problems of my life. Here's some background on my network: +Linux box |Linux laptop (wireless) Wireless/Wired Router/Modem+Windows box #1 |Windows laptop +Windows laptop (wireless) Ok, so first off... all of my family's windows boxes are working fine. Everything is just normal. The linux boxen however, have problems. Internet generally works (although some sites (slashdot, gmail, etc) won't load in firefox (for some reason they will in links). I can't connect to yahoo/jabber/msn/etc w/ gaim, but i can w/ centericq. I've been trying to figure out all this for forever and so i tried to tcptraceroute my way to messenger.hotmail.com as an experiment (on port 1863 or whatever it was). It took a while, but the route was traced. The funny thing is that if i start tracing the route, and then start up gaim, i connect just fine. same goes for the sites that didn't load up in my browser... I can't figure out why everything works on the windows, but not on my linux boxen. the network stuff is all assigned by the router (dhcp). What should i do? Try loweeing the MTU on your eth device(s) to 1492. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto pgpeCWH2228JI.pgp Description: PGP signature
Re: weirdest network problems of my ilfe
On Thu, 2005-09-15 at 18:36 -0600, [EMAIL PROTECTED] wrote: Hi, Ok after installing the new router that came w/ my dsl i'm having the most mind-boggling internet problems of my life. Here's some background on my network: Cameron, First connect your linux box directly to the internet if doable and see if the problem is there. If it is, yell ar your ISP. Else it might be a problem with the adsl boxen itself. In other words Linux works anyway, blame and contact your ISP cause everything works but some special ports and addresses that you are trying to reach. .Alejandro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weirdest network problems of my ilfe
[EMAIL PROTECTED] wrote: Hi, Ok after installing the new router that came w/ my dsl i'm having the most mind-boggling internet problems of my life. Here's some background on my network: +Linux box |Linux laptop (wireless) Wireless/Wired Router/Modem+Windows box #1 |Windows laptop +Windows laptop (wireless) Ok, so first off... all of my family's windows boxes are working fine. Everything is just normal. The linux boxen however, have problems. Internet generally works (although some sites (slashdot, gmail, etc) won't load in firefox (for some reason they will in links). I can't connect to yahoo/jabber/msn/etc w/ gaim, but i can w/ centericq. I've been trying to figure out all this for forever and so i tried to tcptraceroute my way to messenger.hotmail.com as an experiment (on port 1863 or whatever it was). It took a while, but the route was traced. The funny thing is that if i start tracing the route, and then start up gaim, i connect just fine. same goes for the sites that didn't load up in my browser... I can't figure out why everything works on the windows, but not on my linux boxen. the network stuff is all assigned by the router (dhcp). What should i do? you might want to try few liveCD distros to see if some of them works differently, if some of them works better see what settings it uses you can use some network monitoring tool to see what's being sent (e.g. tcpdump) so that you can see what's going on, it might give you soem ideas... use ping with different packet sizes to different destinations (your ISP gateway etc.), see response times, packet loss etc. and compare to windows boxes (the ones that work OK). erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ethernet/network problems in new sarge install
Hello, I have just upgraded my server PC which is a Pentium III 1 ghz to Sarge. The machine is used as a router/firewall for 2 other computers. The problem that I'm having is I installed etherconf to configure eth0 used for the router and now it changes the name to minikerr.minikerr everytime I boot. I go back and change it through the hostname command but it still resets itself after a reboot... Also, etherconf never setup my eth0 right so I eventually removed it via aptitude and configured it manually through ifconfig. THe problem is that when I boot it configures both ethernet adapters for DHCP and my home network uses static addresses. It did the same thing w/etherconf installed... :( My 2nd ethernet adapter is for the cable modem using DHCP so no problems there... If anyone can help me out I would be very appreciative!!! Thanks in advance... John __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethernet/network problems in new sarge install
John Anderson wrote: Hello, I have just upgraded my server PC which is a Pentium III 1 ghz to Sarge. The machine is used as a router/firewall for 2 other computers. The problem that I'm having is I installed etherconf to configure eth0 used for the router and now it changes the name to minikerr.minikerr everytime I boot. I go back and change it through the hostname command but it still resets itself after a reboot... Also, etherconf never setup my eth0 right so I eventually removed it via aptitude and configured it manually through ifconfig. THe problem is that when I boot it configures both ethernet adapters for DHCP and my home network uses static addresses. It did the same thing w/etherconf installed... :( AFAIK there is no GUI point and drool way to setup networking in Debian. You probably have to manually setup your /etc/network/interfaces file like everyone else and maybe touch some other files as well: run man interfaces My 2nd ethernet adapter is for the cable modem using DHCP so no problems there... If anyone can help me out I would be very appreciative!!! Suumarizing from currect threads, the docs are at http://www.tldp.org/HOWTO/Ethernet-HOWTO-2.html#ss2.4 and the 'ifrename' package may help. Thanks in advance... John __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethernet/network problems in new sarge install
John Anderson wrote: Hello, I have just upgraded my server PC which is a Pentium III 1 ghz to Sarge. The machine is used as a router/firewall for 2 other computers. The problem that I'm having is I installed etherconf to configure eth0 used for the router and now it changes the name to minikerr.minikerr everytime I boot. I go back and change it through the hostname command but it still resets itself after a reboot... Also, etherconf never setup my eth0 right so I eventually removed it via aptitude and configured it manually through ifconfig. THe problem is that when I boot it configures both ethernet adapters for DHCP and my home network uses static addresses. It did the same thing w/etherconf installed... :( My 2nd ethernet adapter is for the cable modem using DHCP so no problems there... If anyone can help me out I would be very appreciative!!! Thanks in advance... John Hi To change the hostname run base-config or change the following files manually: /etc/hostname /etc/mailname /etc/hosts I have never used etherconf but I think you will be able to solve tyour problem by editing /ec/network/interfaces You will find a line looking something like this: iface eth0 inet dhcp change that to: iface eth0 inet static -Øyvind -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New kernel, network problems - solution?
There have been several posts lately from people having post-upgraded-kernel network problems. I recently experienced a similar problem after installing a new kernel (network unreachable, Linksys device refusing connection, etc). When I tried unsuccessfully to 'ifup eth0' it was suggested that I needed to have CONFIG_FILTER configured. So, I went back and did that, and now everything's fine. But here's what the config help (for a 2.4.x kernel) says about CONFIG_FILTER: CONFIG_FILTER: The Linux Socket Filter is derived from the Berkeley Packet Filter. If you say Y here, user-space programs can attach a filter to any socket and thereby tell the kernel that it should allow or disallow certain types of data to get through the socket. Linux Socket Filtering works on all socket types except TCP for now. See the text file Documentation/networking/filter.txt for more information. You need to say Y here if you want to use PPP packet filtering (see the CONFIG_PPP_FILTER option below). If unsure, say N. If unsure, say N?? If you do that, networking breaks. This is not the first time I've had this experience (I have a bad memory when it comes to kernel options!), but I think that option should say, if unsure, say Y. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
Marty Landman [EMAIL PROTECTED] writes: I now see that the driver only writes information about transmission errors when its debug flag is set higher than the default. Where do you see that Kevin? And since I suspect an ongoing problem would it make sense for me to change this to possibly capture more errors than now, and if so, how? I meant I saw it while looking at the Tulip driver source. If you load the driver with tulip_debug set to 2, it should log transmit errors. (However, it may also log lots of other stuff, too, which could slow things down or fill your logs.) Here's how to unload and reload the driver with a different tulip_debug setting: ifdown eth0 rmmod tulip modprobe tulip tulip_debug=2 ifup eth0 There's no guarantee that the resulting log will actually tell you anything useful, however. -- Kevin Buhr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
Marty Landman [EMAIL PROTECTED] writes: so I could've just done %ifdown -a ifup -a Yes, that would work. In fact, ifdown eth0 ifup eth0 would just restart the specific interface. The -a flag just means all interfaces flagged with auto in /etc/network/interfaces. A fast steady blink, normal color (green for that particular nic). The steadiness is what made it look strange, Okay, so, for whatever reason, the switch didn't like what the NIC was doing and, probably, disabled the port. Newbie here, where are the kernel logs? I'm not ashamed to admit being an idiot, obviously ;x All the logs are in /var/log. Kernel messages, and just about everything else, are written to the syslog series of files. Like almost all the files in /var/log, these files are rotated periodically (for syslog, it's on a daily basis), so you'll find the most recent messages in syslog, the next most recent in syslog.0, and older ones in syslog.1.gz through syslog.6.gz. Because syslog is rotated daily, the relevant messages may have already fallen off the end if this happened more than a week ago. Fortunately, there's also a dedicated kernel logfile that contains only kernel messages, the kern.log* series. These are rotated once a week, so you should be able to find your messages in there, if you can't find them in syslog*. If it's either the nic or the driver I vote for the driver since that nic's identical twin is installed on my wife's workstation which is running w98. But your specific unit could be faulty. For that matter, the cable between your NIC and the switch might be flakey, or the specific port on the switch might have a problem. Since you're fortunate enough to have a twin NIC, I would suggest swapping the NICs, being careful to swap the cable and port connection at the same time (so your wife's machine is using the same NIC-cable-port combination that you ran into trouble with on your machine). If the problem resurfaces, you have very strong evidence for a driver problem. -- Kevin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
Marty Landman [EMAIL PROTECTED] writes: woody:~# more /var/log/kern.log | grep eth0 Mar 4 09:11:41 woody kernel: eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:40:3E:9B, IRQ 11. [ . . . ] Oh, I see you found the logs. Well, obviously the driver didn't write anything relevant to the logs. And I now see that the driver only writes information about transmission errors when its debug flag is set higher than the default. Now that your machine's been running for a while without trouble, does the ifconfig output show any accumulated transmission errors? If not, I think your best bet is to try swapping cards with your wife's machine to determine whether it's really a hardware or software problem. -- Kevin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
At 02:11 PM 3/6/2004, Kevin Buhr wrote:
Oh, I see you found the logs.
Yes, except your explanation of the relationship between kernel and syslog
is most welcome and educational so thanks, just finished reading it.
BTW am I left to writing my own script if I wanted to grep the syslog for a
certain date that's already been archived or is there a command out there
to do this kind of thing already?
I now see that the driver only writes information about transmission
errors when its debug flag is set higher than the
default.
Where do you see that Kevin? And since I suspect an ongoing problem would
it make sense for me to change this to possibly capture more errors than
now, and if so, how?
Now that your machine's been running for a while without trouble, does the
ifconfig output show any accumulated transmission errors?
I don't see anything:
woody:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:A0:CC:40:3E:9B
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16384 errors:0 dropped:0 overruns:0 frame:0
TX packets:10759 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2033197 (1.9 MiB) TX bytes:1423412 (1.3 MiB)
Interrupt:11 Base address:0xe400
woody:~#
If not, I think your best bet is to try swapping cards with your wife's
machine to determine whether it's really a hardware or software problem.
Maybe this is a stupid way for me to approach it, but that definitely seems
like much more work than just waiting for a third occurrence of the
problem. And if it happens a third time the same way then I would next try
an hourly cron something like this {psuedo code only}
- ifconfig eth0 | grep (errors 0)
thenifdown -eth0
ifup -eth0
echo @`date` had to repair eth0 due to $errors detected
error(s)
/var/log/checketh0.log
elseecho @`date` no problems found
/var/log/checketh0.log
Not that swapping the cards is /that/ big a deal but I actually enjoy
programming and only do hardware when I have no other choice. :}
Marty Landman Face 2 Interface Inc. 845-679-9387
FormATable DB: http://face2interface.com/Products/FormATable.shtml
Make a Website: http://face2interface.com/Home/Demo.shtml
Free Formmailer: http://face2interface.com/Products/Formal.shtml
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
Marty Landman [EMAIL PROTECTED] writes: ifconfig eth0 down rmmod tulip # using this driver for my netgear fs310tx nic modprobe tulip /etc/rc.d/networking restart bash: /etc/rc.d/networking: No such file or directory route add gw 192.168.0.1 gw: host name lookup failure ping 192.168.0.1 ping: sendto: network is unreachable You meant /etc/init.d/networking, not /etc/rc.d/networking. (Also, your route add command had the wrong syntax as someone else pointed out, but you shouldn't need the route add command if your /etc/init.d/networking command works properly.) In other words, you reloaded the module, which might have had some effect, but you didn't bring the interface back up. That's why the ping failed here. The light for this nic on my switch was on and blinking so I removed it and reinserted; stopped blinking, went through the commands above again with similar results and then rebooted. Depending on your switch, this may mean the switch didn't like the way the NIC was behaving and automatically disconnected it from the network (until you disconnected and reconnected the cable). Usually, of course, the LED blinks when there's activity. Was this a different kind of blink than the usual activity blink, say a different colour or a different blinking rate? You said there were 1311 TX errors in the ifconfig output. The Tulip driver sometimes writes information to the logs. Do you have any lines like: eth0: Transmit error, Tx status NNN. or any other network-related lines in the kernel logs during the malfunction? Without further information, it looks like your NIC (either because it's faulty or there's a problem with the Tulip driver) is behaving badly---jabbering or causing too many collisions---and the switch is disconnecting it from the network so it doesn't bring everything down. -- Kevin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
At 05:51 PM 3/5/2004, Kevin Buhr wrote: You meant /etc/init.d/networking, not /etc/rc.d/networking. Heh, explains one problem, thanks Kevin. (Also, your route add command had the wrong syntax as someone else pointed out, but you shouldn't need the route add command if your /etc/init.d/networking command works properly.) In other words, you reloaded the module, which might have had some effect, but you didn't bring the interface back up. That's why the ping failed here. Whereas rebooting actually did bring the interface back up, which probably means that my /etc/init.d/networking script is ok? These are the pertinent lines from the networking script, right? restart) echo -n Reconfiguring network interfaces: ifdown -a ifup -a echo done. so I could've just done %ifdown -a ifup -a Depending on your switch Netgear FS605 -- no complaints with it so far of course, the LED blinks when there's activity. Was this a different kind of blink than the usual activity blink, say a different colour or a different blinking rate? A fast steady blink, normal color (green for that particular nic). The steadiness is what made it look strange, even during large data transfers I notice the lights are sporadic to some degree, plus it'd never be only one light blinking that long by itself since some other box on the lan would be on the sending or receiving end of the transfer. You said there were 1311 TX errors in the ifconfig output. Correct. The Tulip driver sometimes writes information to the logs. Do you have any lines like: eth0: Transmit error, Tx status NNN. or any other network-related lines in the kernel logs during the malfunction? Newbie here, where are the kernel logs? I'm not ashamed to admit being an idiot, obviously ;x Without further information, it looks like your NIC (either because it's faulty or there's a problem with the Tulip driver) is behaving badly---jabbering or causing too many collisions---and the switch is disconnecting it from the network so it doesn't bring everything down. If it's either the nic or the driver I vote for the driver since that nic's identical twin is installed on my wife's workstation which is running w98. Although it's worth mentioning that the first time this happened about a month ago I reinstalled the os on my wife's workstation. Is it plausible that these two nics being the same card model something related to one could upset the other, or is that way too big a reach? Unfortunately this sounds like a situation where the problem will either resurface, or bug me to death wondering why if it doesn't it happened to begin with. Marty Landman Face 2 Interface Inc. 845-679-9387 FormATable DB: http://face2interface.com/Products/FormATable.shtml Make a Website: http://face2interface.com/Home/Demo.shtml Free Formmailer: http://face2interface.com/Products/Formal.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
At 05:51 PM 3/5/2004, Kevin Buhr wrote: The Tulip driver sometimes writes information to the logs. Do you have any lines like: eth0: Transmit error, Tx status NNN. or any other network-related lines in the kernel logs during the malfunction? woody:~# more /var/log/kern.log | grep eth0 Mar 4 09:11:41 woody kernel: eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:40:3E:9B, IRQ 11. Mar 4 09:11:41 woody kernel: eth0: MII transceiver #1 config 1000 status 782d advertising 01e1. Mar 4 09:23:24 woody kernel: eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:40:3E:9B, IRQ 11. Mar 4 09:23:24 woody kernel: eth0: MII transceiver #1 config 1000 status 782d advertising 01e1. Mar 4 09:23:24 woody kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. woody:~# more /var/log/kern.log.0 | grep eth0 Feb 16 17:44:29 woody kernel: eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:40:3E:9B, IRQ 11. Feb 16 17:44:29 woody kernel: eth0: MII transceiver #1 config 1000 status 782d advertising 01e1. Feb 16 17:49:12 woody kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 16 20:28:28 woody kernel: eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:40:3E:9B, IRQ 11. Feb 16 20:28:28 woody kernel: eth0: MII transceiver #1 config 1000 status 782d advertising 01e1. Feb 16 20:28:28 woody kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 19 15:14:47 woody kernel: eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:40:3E:9B, IRQ 11. Feb 19 15:14:47 woody kernel: eth0: MII transceiver #1 config 1000 status 782d advertising 01e1. Feb 19 15:14:47 woody kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. woody:~# All I found on the log before and after the problem since I rebooted at the time. Marty Landman Face 2 Interface Inc. 845-679-9387 FormATable DB: http://face2interface.com/Products/FormATable.shtml Make a Website: http://face2interface.com/Home/Demo.shtml Free Formmailer: http://face2interface.com/Products/Formal.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
unexplained network problems
Running woody on a lan using another box - 192.168.0.1 as the gateway. The debian box runs samba as do two other nix boxes. Last night everything seemed fine, this morning for unknown reasons my debian box doesn't seem to be able to talk with anything else. Can ping myself by name, network ip, or as localhost but ping attempts to other boxes hang. An ifconfig -a shows the nic up and running, with 0 RX packet errors and 1311 TX packet errors. A netstat -rn shows two entries, one for my class c network and one for my gateway which is win xp. destination gateway genmask flags iface 192.168.0.0 0.0.0.0 255.255.255.0 U eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG eth0 Here's what happened next: # as root of course - manually copying from the console ifconfig eth0 down rmmod tulip # using this driver for my netgear fs310tx nic modprobe tulip /etc/rc.d/networking restart bash: /etc/rc.d/networking: No such file or directory route add gw 192.168.0.1 gw: host name lookup failure ping 192.168.0.1 ping: sendto: network is unreachable The light for this nic on my switch was on and blinking so I removed it and reinserted; stopped blinking, went through the commands above again with similar results and then rebooted. Everything is ok now. Only I feel like an idiot. What happened and how did I fix it? Had a problem with this box's connection a few weeks ago too, which is how I knew the steps to try and recover. Any pointers on how I can educate myself to at least understand what I'm doing - not to mention get a clue about what problem is bringing my network down every couple weeks would be most gratefully accepted. Marty Landman Face 2 Interface Inc. 845-679-9387 FormATable DB: http://face2interface.com/Products/FormATable.shtml Make a Website: http://face2interface.com/Home/Demo.shtml Free Formmailer: http://face2interface.com/Products/Formal.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
On Thursday 04 March 2004 15:33, Marty Landman shoved this in my mailbox: route add gw 192.168.0.1 gw: host name lookup failure This should be: route add default gw 192.168.0.1 You may want to check the arp table: arp anything in it? joost DISCLAIMER This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify A.S.T.R.I.D. nv/sa immediately and then delete this e-mail. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
At 09:35 AM 3/4/2004, Joost De Cock wrote: This should be: route add default gw 192.168.0.1 Ah, thank you. So perhaps rebooting simply did what I failed to do manually? You may want to check the arp table: woody:~# arp Address HWtype HWaddress Flags MaskIface delliver.face2interface ether 00:08:74:C0:5E:69 C eth0 woody:~# Then I pinged the other boxes on my lan and arp showed them all except for woody, which is this box. I am still concerned about why this happened to begin with. It's looking like the fix was to reinstall my nic driver, but why did things go bad? This as said happened two weeks ago as well, also for unknown reasons so am assuming it's the same thing. Well next time if there is a next time I'll know just what to try for recovery. Here's a funky idea, if this were to happen on a steady basis I could put a cron job in to check for the symptoms and if the network's lost then reinstall my nic. :0} Maybe tulip isn't all that good a match for my netgear fs310tx nic? So after some time it misbehaves and stops working? Marty Landman Face 2 Interface Inc. 845-679-9387 FormATable DB: http://face2interface.com/Products/FormATable.shtml Make a Website: http://face2interface.com/Home/Demo.shtml Free Formmailer: http://face2interface.com/Products/Formal.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unexplained network problems
On Thu, 4 Mar 2004, Marty Landman wrote: route add default gw 192.168.0.1 Ah, thank you. So perhaps rebooting simply did what I failed to do manually? Could be, but I don't think so. You may want to check the arp table: Next time check arp when the problem occurs. Could be another machine is trying to use the machine's IP. Later, Bill Carlson -- Systems Administrator[EMAIL PROTECTED] | Anything is possible, Virtual Hospital http://www.vh.org/ | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debugging network problems
On Wed, Jan 21, 2004 at 04:46:37PM -0800, Bill Moseley wrote: So the question is, in a setup like the above what's the best way to get in and sniff the packets? My $0.02 is: 2 ethernet cards, 2 cross-wire TP cables, one decent Debian installation turned into a router: [Brother] - :eth0:[decent OS + decent HW]:eth1: - [DSL] You should be able to use the fax email feature, and sniff with tcpdump on either of the eth[01] interfaces. HTH, Jan. -- Jan Minar Please don't CC me, I'm subscribed. x 9 pgp0.pgp Description: PGP signature
Debugging network problems
Friend has a Brother Fax/Printer thingy. It has an ethernet port and it has this Internet Fax setup (which is not really a fax) where you type in someone's email address, scan some documents and it emails an image (tiff format). It's basically a mail client. Here's the problem: He has a pppoe setup. He's got a DSL modem/router that does the dialup to the ISP. AFAIK when you connect to the router it then connects to the DSL. He has the machine configured to send to his smtp server at his ISP -- just like his normal mail account. He can send a few pages without any problem. But if he tries sending a lot of data it doesn't work. The printer just says Network Failure and that's it. Placing the print on my LAN and sending documents to my exim server works perfectly. So, I think the next step is to use tcpdump or etherreal to see if his SMTP connection if failing for some reason. His DSL modem/router is also a wireless switch. I've tried using tcpdump and etherreal but I think the switch is hiding the packets from my machine. So the question is, in a setup like the above what's the best way to get in and sniff the packets? -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? I have the same card. Are you using 40 or 128 bit encryption? Have you tried setting encryption manually? Such as: ~$ iwconfig eth1 enc 01234567890123456789123456 (for 128 bit encryption there are 26 characters needed and for the 40 bit encryption there are 10 characters needed...I think... so if you are using only 5 characters...that may be the problem) Also, have you played around with /etc/pcmcia/wireless.opts ? I don't use the interfaces file for the wireless settings like you do. All my configuration in in wireless.opts and the only thing in my interfaces file is this: auto eth1 iface eth1 inet dhcp One other thing, I remember vaguely having trouble with the bf24 kernel and wireless. Maybe you can try to do a custom kernel? Also what do you have for modules? This is what I have when I do lsmod: orinoco_cs 4724 1 orinoco37140 0 [orinoco_cs] hermes 6020 0 [orinoco_cs orinoco] Hope this gets you started in the right direction. Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Major network problems
Ever since a power outage this weekend, I have no internet access in my Linux box (which is used as a network router). Even local loopback isn't working. After testing with help from #debian, it seems that ifconfig is acting up.When I try to ifup -v lo, I get the following: ifconfig lo 127.0.0.1 up... ifconfig: only one address allowed for interface 'lo'. Same thing happens for eth0 and eth1, but with the gateway and broadcast lines included as well. After any of these commands, and when I reboot (which usually cleared any problems) ifconfig lists absolutely nothing, and not even ping to localhost will work (connect: invalid argument). Anyone have any ideas?
Re: Major network problems
On Mon, 2003-11-10 at 11:02, Jon Eisenstein wrote: Ever since a power outage this weekend, I have no internet access in my Linux box (which is used as a network router). Even local loopback isn't working. After testing with help from #debian, it seems that ifconfig is acting up. When I try to ifup -v lo, I get the following: ifconfig lo 127.0.0.1 up... ifconfig: only one address allowed for interface 'lo'. Same thing happens for eth0 and eth1, but with the gateway and broadcast lines included as well. After any of these commands, and when I reboot (which usually cleared any problems) ifconfig lists absolutely nothing, and not even ping to localhost will work (connect: invalid argument). Anyone have any ideas? Could the electric surge have whacked your hard disk? -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA I have been assured by a very knowing American of my acquaintance in London, that a young healthy child well nursed is at a year old a most delicious, nourishing, and wholesome food, whether stewed, roasted, baked, or boiled; and I make no doubt that it will equally serve in a fricassee or a ragout. A MODEST PROPOSAL FOR PREVENTING THE CHILDREN OF POOR PEOPLE IN IRELAND FROM BEING A BURDEN TO THEIR PARENTS OR COUNTRY -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Major network problems
Jon Eisenstein wrote: Ever since a power outage this weekend, I have no internet access in my Linux box (which is used as a network router). Even local loopback isn't working. After testing with help from #debian, it seems that ifconfig is acting up. When I try to ifup -v lo, I get the following: ifconfig lo 127.0.0.1 up... ifconfig: only one address allowed for interface 'lo'. Same thing happens for eth0 and eth1, but with the gateway and broadcast lines included as well. After any of these commands, and when I reboot (which usually cleared any problems) ifconfig lists absolutely nothing, and not even ping to localhost will work (connect: invalid argument). Anyone have any ideas? What does /etc/network/interfaces look like? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Network problems
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 temporal error of the network, Does rebooting into the shipped kernel help? There was some kernel option that two people on this list have used with VIA NICs and 2.4.2X kernels in the past week, but I can't remember it off the top of my head. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: armed overthrow Delta Force Etacs FTS2000 Legion of Doom signature.asc Description: Digital signature
Re: Network problems
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, I do not know if the problem resides in the kernel, it is a temporal error of the network, Does rebooting into the shipped kernel help? There was some kernel option that two people on this list have used with VIA NICs and 2.4.2X kernels in the past week, but I can't remember it off the top of my head. It was the 'noapic' option, in my case. Cheers! -- ,-. -ScruLoose- | Religion's in the hands of some crazy-ass people. Please do not | - Jimmy Buffet reply off-list. | `-' pgp0.pgp Description: PGP signature
Network problems
Hi all, I have a new computer and I have installed Debian on it and the network has a strange behavior. The downloads go very quick, in fact, I just have done an 'apt-get upgrade' and the average download speed has been 697KB/s. But things change radically when I want to access to that computer, for instance accesses to web pages from other machines on the same subnet are quite slow, access from ssh. In fact when I do 'ping' to the gateway I get no less than 50% of packets loss. The problem appears when I install any of the precompiled version of the kernel that I have tried: - kernel-image-2.4.20-3-686/testing uptodate 2.4.20-9 - kernel-image-2.4.18-686/stable uptodate 2.4.18-5 - kernel-image-2.4.22-1-686/testing uptodate 2.4.22-3 - kernel-image-2.4.21-5-686/testing uptodate 2.4.21-5 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 temporal error of the network, Hereafter there are the data of the Network card: 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (750ns min, 2000ns max), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at e400 [size=256] Region 1: Memory at e2001000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2 +,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Thank you all. -- Luis Fernando Llana Díaz If you use Internet Explorer 6 under Windog XP, click here http://antares.sip.ucm.es/~luis/ie/aviso.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more network problems
Did you check the gateway? -- Angel Gutierrez Rodriguez, Ph. D. Unit for Cell Biology Wenner-Gren Center P12 Dept. of Biosciences @ NOVUMSveavagen 164 Deja de pensar Karolinska Institutet 113 46 Stockholmsi hicimos bien o mal Halsovagen, 7 SWEDEN si aun nos queda algo que hacer S-141 57 Huddinge hagamoslo bien... SWEDEN Tlf.: 46-8-6089132 Tlf.: 46-8-7369986 Fax : 46-8-7745538 E-mail: [EMAIL PROTECTED]
Re: more network problems
on Fri, Sep 21, 2001 at 02:30:25PM -0700, Lazar Fleysher ([EMAIL PROTECTED]) wrote: Hello everybody earlier today Ihave posted a message about problems configuring network card. Basically the situation is that the computer does not see the network Please set your linewrap to something sane. however, if someone pings my computer I see number of receive errors increase as reported by ifconfig If I try to ping other computer, I see number of transmit error increase I also see that number of interrupts serviced increases as some pings me or I ping someone (from /proc/interrupts) It seems to me that the card itself is working (and it works underwin) but Iwant and need linux!!! Could someone tell me what is going on? and how to fix it ? Take a look at the Network Administrator's Guide (Google will provide) and work through the chapters on basic Ethernet configuration. If you can't get it working, follow the diagnostic steps and post relevent commands and output. If that fails, find a local user or installfest. You're not describing your problems well enough to provide useful guidance. I'd very strongly recommend you read the following excellent essay by Simon Tatham, How to Report Bugs Effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Please note that you are the person in the best position to know what you're trying to do, what you've done, how the system's responded, and generally how it's configured. It's very helpful if you can post: - *Exact* commands or steps tried. - *Exact* error output or log messages. Often, entering the error messages into a good search engine such as Google (http://www.google.com/) will help set you on the road to resolving your problems. While others can offer suggestions, guidance, and experience, we cannot see into either your mind or your machine's state. This is very much a case of you have to help us help you. Good luck. Thank you. Peace. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? Home of the brave http://gestalt-system.sourceforge.net/Land of the free Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html pgpL1WaaH9hmM.pgp Description: PGP signature
more network problems
Hello everybody earlier today Ihave posted a message about problems configuring network card. Basically the situation is that the computer does not see the network however, if someone pings my computer I see number of receive errors increase as reported by ifconfig If I try to ping other computer, I see number of transmit error increase I also see that number of interrupts serviced increases as some pings me or I ping someone (from /proc/interrupts) It seems to me that the card itself is working (and it works underwin) but Iwant and need linux!!! Could someone tell me what is going on? and how to fix it ? Lazar PS I have fresh install of 2.2.19-compact distribution with cabletron network card.
Network Problems
I upgraded my Debian (that I just got working!) to have KDE2.1.1 and somewhere along the way I installed something that now gives me a tap0 interface. I have to manually type 'ifconfig tap0 down' as root to be able to use PPP. What package started this guy up? How can I get rid of it. Shawn Garbett
Network Problems on Debian 2.2 box
Hi, Ok, the problem: I telnet, vnc, etc. (basically connect to the box with some sort of interactive client) and after about 5 mins (not sure couldn't quite time it) the client gets kicked of (Putty 0.51 reports Network error: Software caused connection abort). Now the machine refuses any network connections to for about 15-60 secs and sometimes during this period a subsequent portscan shows up ports that's definitly not on this machine (from which/what machine I don't know as a traceroute shows one hop which is correct and ngrep doesn't show anything usefull - not that I really know what to look for though). After this short period though I can reconnect only to be bumped of later again! The connection abort doesn't kill the telnet/bash session though and when I telnet in again the processes of the apps I was working on is still sitting there. A who shows me still connected (with the current session plus the previous ones shown) and killing the telnet process doesn't seem to refresh who's output. I'm running a 15 second delayed ping to an internet host in a screen session to try and see if the box looses connectivity but it seems fine, the only thing I can see is that it seems to pick up some network lag at intervals; the worst of which seem to conincide with being kicked, but not always! Where do I look to see what settings might control this type of behaviour, is there an app that does this? I've checked cron as well as at and the only jobs scheduled is mrtg and exim each every 30mins. I've attached the package list, process tree and extra info like the modules loaded. Please let me know what other info is required to make the picture clearer. The box has two 3com 905B NIC's sharing IRQ 10, with only one currently up. I want to set the box up as a Firewall/Proxy with a smtp gateway, and this behaviour will make internet access through it almost impossible! If it was just the telnet sessions timimg out I wouldn't have worried as much and accepted is as more of a security 'feature' but VNC sessions get booted as well, and I haven't set any timeouts! I'm pulling my hair out here, I've reinstalled this box twice and have the latest stable packages from my nearest mirror (ftp://ftp.is.co.za/linux/distributions/debian/) and security.debian.org! Thanks in advance, Eugene van Zyl init-+-atd |-cron |-getty |-getty |-getty |-getty |-getty |-getty |-gpm |-inetd---in.telnetd---bash---bash---pstree |-kflushd |-klogd |-kpiod |-kswapd |-kupdate |-pwcheck |-snort |-squid---squid-+-dnsserver | |-dnsserver | |-dnsserver | |-dnsserver | |-dnsserver | |-pinger | `-squid-+-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | |-squid | `-squid |-start---pike `-syslog-ng Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii adduser 3.11.1Add users and groups to the system. ii ae962-26Anthony's Editor -- a tiny full-screen editor ii apt 0.3.19Advanced front-end for dpkg ii at3.1.8-10 Delayed job execution and batch processing ii base-config 0.33.2Debian base configuration package ii base-files2.2.0 Debian base system miscellaneous files ii base-passwd 3.1.10Debian Base System Password/Group Files ii bash 2.03-6The GNU Bourne Again SHell ii bc1.05a-11 The GNU bc arbitrary precision calculator language ii bsdmainutils 4.7.1 More utilities from 4.4BSD-Lite. ii bsdutils 2.10f-5.1 Basic utilities from 4.4BSD-Lite. ii bzip2
Re: 3c905/network problems
Pete Meyer wrote: Hi all...I'm having difficulty getting my network card (3c905c) work under debian. I've tried using the 3c59x driver (I was using the wrong one before). It installs ok, but then DHCP won't configure the network. I know that there's a server present, because that's how windows is configured. I've also tried the 3c90x driver, but can't get it to compile. I was recently trying to get a 3c905cx-txm working. I compiled the module as gcc -c 3c90x.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer \ -fno-strength-reduce -pipe -m486 -malign-loops=2 \ -malign-jumps=2 -malign-functions=2 -DCPU=486 \ -DMODULE -D__KERNEL__ \ -DMODVERSIONS \ -I/usr/src/kernel-headers-2.2.18pre21/include That compiled with no errors. I installed the module, updated /etc/modutils/aliases, did update-mdules and depmod -a. No errors. Still didn't work. You have a different card, though, so maybe you'll have better luck. (You might not need the -DMODVERSIONS, I can't remember.) You should have a line like the following in /etc/network/interfaces. You probably know that, but thought I'd mention it. iface eth0 inet dhcp Also make sure your BIOS setting for Plug-and-Pray OS is turned off. -- Ron Peterson Network Systems Manager Mount Holyoke College GPG and other info at http://www.mtholyoke.edu/~rpeterso
3c905/network problems
Hi all...I'm having difficulty getting my network card (3c905c) work under debian. I've tried using the 3c59x driver (I was using the wrong one before). It installs ok, but then DHCP won't configure the network. I know that there's a server present, because that's how windows is configured. I've also tried the 3c90x driver, but can't get it to compile. Anyhow, I'd really appreciate any help/suggestions on this, as I've been working on it for about a week and a half now. Thanks, Pete Who needs Cupid? Matchmaker.com is the place to meet somebody. FREE Two-week Trial Membership at http://www.matchmaker.com/home?rs=200015
Network problems
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 the module for the NIC is loaded properly, I get a connect : Network is unreachable-message each time I try to ping any machine - neither the ones in our network are reached nor any external... of course ! I have also defined our standard gateway here and our DNS so what do I still do wrong ? Any clues are really appreciated ! --- Mit freundlichem Gruss [EMAIL PROTECTED] Oliver Schoenknecht Join us at http://www.kapa.de KOSTENLOS! Online-Auktion bei KAPA! Teilnahme unter: http://www.flohmarkt.kapa.de
Re: Network problems
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 the module for the NIC is loaded properly, I get a connect : Network is unreachable-message each time I try to ping any machine - neither the ones in our network are reached nor any external... of course ! I have also defined our standard gateway here and our DNS so what do I still do wrong ? Any clues are really appreciated ! --- Mit freundlichem Gruss [EMAIL PROTECTED] Oliver Schoenknecht Join us at http://www.kapa.de KOSTENLOS! Online-Auktion bei KAPA! Teilnahme unter: http://www.flohmarkt.kapa.de -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Network problems
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 'ifconfig' and 'route'? Can you ping localhost? Can you ping yourself via your network name? -- Bob Bernstein | Same sudden on unseen lips. None at | unseen. Bones on key on mod on preying Esmond, R.I., USA | in on never out. Feet fade if same | hands nohow. Ill seen worsen unseen. | Know knowing same seen none. None same | same hand unseen. Somehow boundless | old same still somehow unpack.
network problems running frozen on alpha
I just upgraded to the frozen version of the alpha dist on my Jensen and am having network problems. I can no longer ping from or to the machine. Attempting to ping from the alpha, I get the following: ping: sendto: Operation not permitted for each packet it attempts to send. There are no broken packages. I am still running a 2.0 kernel. Any thoughts or suggestions would be greatly appreciated. Thanks, Geoff Mitchell Geoff Mitchell [EMAIL PROTECTED] - I think your flesh is separated from the sins it commits and that explains why you smile while you balance on your stack of regrets. -- Brainiac - http://www.bigfoot.com/~geoff_mitchell
Re: network problems running frozen on alpha
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 longer ping from or to the machine. Attempting to ping from the alpha, I get the following: ping: sendto: Operation not permitted for each packet it attempts to send. There are no broken packages. I am still running a 2.0 kernel. Any thoughts or suggestions would be greatly appreciated. Thanks, Geoff Mitchell Geoff Mitchell [EMAIL PROTECTED] - I think your flesh is separated from the sins it commits and that explains why you smile while you balance on your stack of regrets. -- Brainiac - http://www.bigfoot.com/~geoff_mitchell -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: network problems running frozen on alpha
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,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 longer ping from or to the machine. Attempting to ping from the alpha, I get the following: ping: sendto: Operation not permitted for each packet it attempts to send. There are no broken packages. I am still running a 2.0 kernel. Any thoughts or suggestions would be greatly appreciated. Thanks, Geoff Mitchell Geoff Mitchell [EMAIL PROTECTED] - I think your flesh is separated from the sins it commits and that explains why you smile while you balance on your stack of regrets. -- Brainiac - http://www.bigfoot.com/~geoff_mitchell -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Geoff Mitchell [EMAIL PROTECTED] - I think your flesh is separated from the sins it commits and that explains why you smile while you balance on your stack of regrets. -- Brainiac - http://www.bigfoot.com/~geoff_mitchell
Re: network problems running frozen on alpha
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). 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,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 longer ping from or to the machine. Attempting to ping from the alpha, I get the following: ping: sendto: Operation not permitted for each packet it attempts to send. There are no broken packages. I am still running a 2.0 kernel. Any thoughts or suggestions would be greatly appreciated. Thanks, Geoff Mitchell Geoff Mitchell [EMAIL PROTECTED] - I think your flesh is separated from the sins it commits and that explains why you smile while you balance on your stack of regrets. -- Brainiac - http://www.bigfoot.com/~geoff_mitchell -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Geoff Mitchell [EMAIL PROTECTED] - I think your flesh is separated from the sins it commits and that explains why you smile while you balance on your stack of regrets. -- Brainiac - http://www.bigfoot.com/~geoff_mitchell
Re: Network problems after compile of 2.2.14 kernel
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 added statements to the /etc/networks/interfaces file to start each ethernet card. It looks like this part is working. Thanks for your help. Doug 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 configuration) for irq/io/speed? I guess an additional question would be if I should compile the networking into the kernel and not bother with the modules? That's your call. Shouldn't make any difference wrt to configuring the driver. /Allan -- Allan M. Wind Finger: [EMAIL PROTECTED] (GPG/PGP) P.O. Box 2022 Email: [EMAIL PROTECTED] Woburn, MA 01888-0022 ICQ: 44214251 USA Phone: 781.279.4513 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Network problems after compile of 2.2.14 kernel
Hello, I hope this is the right area to ask this question. I have a system I plan to use as a firewall eventually. Currently I am trying to get the networking (using two 3C509 network cards) to work. Originally my system was using the 2.0.36 kernel and everything seem to work fine. eth0 connected to our internal network and eth1 connected to the internet. I upgraded my system to the (frozen) distribution and downloaded the 2.2.14 kernel source. After compiling and installing the kernel and modules my system only saw one network card (eth0) and this connection doesn't work. I added the alias lines shown below to the /etc/modules.conf file. alias eth0 3c509 alias eth1 3c509 With these two lines (after a reboot) I see three lines refering to ethX adapters in the /var/log/syslog (eth0, eth1, eth2). eth0 and eth1 are for the exact same card (eth0 doesn't work but eth1 does for my internal network). eth2 works for the internet connection. NOTE: I also noticed that the eth0 line is generated at a different point on the starting process! What is going on here? How do I get rid of the first eth0 that doesn't work? Is there some new process for configuring network cards in this new Kernel? Thanks for your time! Doug Thistlethwaite
Re: Network problems after compile of 2.2.14 kernel
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 it. I had to add the following line to lilo.conf: append=ether=5,0x310,0,0,eth0 ether=9,0x300,0,0,eth1 Good Luck! -- Jeff On Thu, 2 Mar 2000, Doug wrote: Hello, I hope this is the right area to ask this question. I have a system I plan to use as a firewall eventually. Currently I am trying to get the networking (using two 3C509 network cards) to work. Originally my system was using the 2.0.36 kernel and everything seem to work fine. eth0 connected to our internal network and eth1 connected to the internet. I upgraded my system to the (frozen) distribution and downloaded the 2.2.14 kernel source. After compiling and installing the kernel and modules my system only saw one network card (eth0) and this connection doesn't work. I added the alias lines shown below to the /etc/modules.conf file. alias eth0 3c509 alias eth1 3c509 With these two lines (after a reboot) I see three lines refering to ethX adapters in the /var/log/syslog (eth0, eth1, eth2). eth0 and eth1 are for the exact same card (eth0 doesn't work but eth1 does for my internal network). eth2 works for the internet connection. NOTE: I also noticed that the eth0 line is generated at a different point on the starting process! What is going on here? How do I get rid of the first eth0 that doesn't work? Is there some new process for configuring network cards in this new Kernel? Thanks for your time! Doug Thistlethwaite -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Network problems after compile of 2.2.14 kernel
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: Hello, I hope this is the right area to ask this question. I have a system I plan to use as a firewall eventually. Currently I am trying to get the networking (using two 3C509 network cards) to work. Originally my system was using the 2.0.36 kernel and everything seem to work fine. eth0 connected to our internal network and eth1 connected to the internet. I upgraded my system to the (frozen) distribution and downloaded the 2.2.14 kernel source. After compiling and installing the kernel and modules my system only saw one network card (eth0) and this connection doesn't work. I added the alias lines shown below to the /etc/modules.conf file. alias eth0 3c509 alias eth1 3c509 With these two lines (after a reboot) I see three lines refering to ethX adapters in the /var/log/syslog (eth0, eth1, eth2). eth0 and eth1 are for the exact same card (eth0 doesn't work but eth1 does for my internal network). eth2 works for the internet connection. NOTE: I also noticed that the eth0 line is generated at a different point on the starting process! What is going on here? How do I get rid of the first eth0 that doesn't work? Is there some new process for configuring network cards in this new Kernel? Thanks for your time! Doug Thistlethwaite -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Network problems after compile of 2.2.14 kernel
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 kernel and not bother with the modules? Finally, are you using the 2.2.14 kernel? My 2.0.36 kernel worked without a hitch. Doug 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 it. I had to add the following line to lilo.conf: append=ether=5,0x310,0,0,eth0 ether=9,0x300,0,0,eth1 Good Luck! -- Jeff
Re: Network problems after compile of 2.2.14 kernel
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 configuration) for irq/io/speed? I guess an additional question would be if I should compile the networking into the kernel and not bother with the modules? That's your call. Shouldn't make any difference wrt to configuring the driver. /Allan -- Allan M. Wind Finger: [EMAIL PROTECTED] (GPG/PGP) P.O. Box 2022 Email: [EMAIL PROTECTED] Woburn, MA 01888-0022 ICQ: 44214251 USA Phone: 781.279.4513
Re: Potato network problems
If you get DENY messages in your logs, this is indicative of ipchains problem. Either your all your chains are flushed, and set to default DENY, or some other ipchains misconfiguration. Do ipchains -L to see if any of the chains are set to DENY, or flushed to DENY.
Potato network problems
I've got a potato box which just broke on a recent update. This machine is a IP masquerading gateway, it has ipmasq and the various other potato networking tools installed. The machine's been running fine, but when I did an update Monday evening it stopped talking to the net sometime during the night. I've been pulling my hair out trying to figure this one out. The update went perfectly fine, no errors or anything, but the machine just stopped talking -- the machine can't be seen from the net. The internal network (192.168.*.*) works just fine. The various services on the server also work fine from the internal network. The problem is that it won't talk to the net. I can ping the NIC which is on the net, the card responds fine. However, if I try to hit my external gateway's IP address I get nothing. Ifconfig and route -n show normal info; it should, I changed nothing other than doing a dselect update/install. There appears to be incoming traffic hitting the Internet NIC. I know the network link is up because if I reconfigure another machine I can get out directly (by bypassing the server). I do, however, get messages in /var/log/kern.log which mention kernel: packet log DENY. My questions are many. Did any ipchains stuff get updated in the past few days? Is anyone else experiencing this (I've got another similarly configured machine which has been working just fine -- go figure.:-)? Since I've triple check the various /etc networking-related files and my /etc/init.d/networks, I'm ass/u/ming it's something to do with the firewalling/ipmasq package. Does anyone have a barest-bones script for ipchains that I could play with just to examine that possibility? Any tips would be appreciate; TIA. -- Regards, | [EMAIL PROTECTED] | I'm a computer geek, not in marketing. .|| Since I'm paid for technical knowledge Randy|| and not opinions, any opinions voiced || are my own and not my employer's.
[OT] How to find out who to contact with Internet network problems?
Hi there, this is probably an off-topic question to this list. Sorry for this, but I don't know who else to ask or where to look, therefore I hope that my question is read by an experienced network admin of a large company network or an otherwise experienced user who can answer my question. Ok, I'm trying to contact a host across the Internet. The connection is very bad, packets get lost with a percentage of up to 30%. I traced the route and found the point where trouble is probably caused. If I ping a certain host/router (let's call it B), LOTS of packets get lost. If I ping the router one hop nearer to me (named A) only a small, negligible percentage gets lost. Who do I contact? The admin of A or B? How do I find out who is responsible? Is it ok to use the tech-c that I look up using whois? Thanks, Ralf -- Sign the EU petition against SPAM: L I N U X .~. http://www.politik-digital.de/spam/The Choice /V\ of a GNU /( )\ Generation ^^-^^
Re: [OT] How to find out who to contact with Internet network problems?
mail to both of them, not necessarily to the tech-c's, but better to the support@domain-of-tech-c-A,domain-of-tech-c-B. the tech-c's are usually too utilized to answer such questions and just bounce them to support... hth rw (whois -h whois.ripe.net AS1901-MNT - RW960-RIPE ;-) On Tue, 11 Jan 2000 19:28:00 +0100, Ralf G. R. Bergs writes: Who do I contact? The admin of A or B? How do I find out who is responsible? Is it ok to use the tech-c that I look up using whois? -- -- +++ EUnet/[EMAIL PROTECTED], 15.-17.2.'2k, Ebene02/Stand08 +++ - ___ - Robert WaldnerEUnet/AT tech staff // / ___ _/_ -- [EMAIL PROTECTED] RW960-RIPE --- /--- / / / / /___/ / --- ---EUnet EDV-DienstleistungsgesmbH--- -- /___ /___/ / / /___ /_ Diefenbachgasse 35A-1150 Wien - - Tel: +43 1 89933 Fax: +43 1 89933 533
Snapshot for debugging network problems
While tracking down network problems of any kind, it's quite handy to take a snapshot of the networking parameters so you can look at it after the event. I have a bash function which is currently: /bin/uname -a /sbin/ifconfig /sbin/route -n /usr/sbin/arp -n -a /bin/netstat -n -a -e /bin/ps auxwww /bin/date Then I use tcpdump -l -n -i interface [host host] | tee somefile to watch the traffic and /bin/fuser -n udp or tcp -v port number to see what might be causing trouble. The last one I really stumbled across, only having seen fuser used for investigating busy files and directories in the past. Are there any useful commands I've missed? What's the best tool for translating the output from tcpdump?[stop here if you like] For those that might be interested, the last problem I was trying to solve was a dramatic slowdown in ppp from my home machine to work. So slow that ssh just wouldn't connect, and telnet would take more than five minutes. Characters could take up to a minute to reflect. I was at work and had initiated the ppp connection. Looking at the traffic with tcpdump -l -i ppp0, it was completely dominated by traffic to the nameservers, and with the fuser command on the port numbers being shown, I was able to pin it down to icmplogd and tcplogd which were running on the m/c at home. (No longer.) I have no idea why this slowdown had happened only a couple of times in the past, but previously I'd put it down to a bad line or some ethernet problem at work. (It never seemed to affect the CHAP handshaking, though.) I attacked the problem this time because I was sitting at the work end, so I could easily confirm that everything on the ethernet was functioning. (And I really needed to transfer a file home.) It took me most of an hour to realise I should kill the two offending daemons. I'm still not sure what they were asking the nameservers, but I have a large traffic file available. I'm used to seeing messages like (from memory) bar 255, who is foo, tell bar and foo bar, foo is on 0:1:2:3:4:5 but this stuff was all numerical. Is there something that can print what it thinks it all means? Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: Snapshot for debugging network problems
Hmmm, 'ipchains -L' or 'ipchains -L -v' could be useful here. If the i/o chains filter or accept packets that could be (part of) the problem you're a step closer to the solution. I use ipchains sometimes to block/accept packets to see what will happen in some circumstances. I'm very curious what will come of this thread... Regards, Onno At 02:48 PM 11/5/99 +, David Wright wrote: While tracking down network problems of any kind, it's quite handy to take a snapshot of the networking parameters so you can look at it after the event. I have a bash function which is currently: /bin/uname -a /sbin/ifconfig /sbin/route -n /usr/sbin/arp -n -a /bin/netstat -n -a -e /bin/ps auxwww /bin/date Then I use tcpdump -l -n -i interface [host host] | tee somefile to watch the traffic and /bin/fuser -n udp or tcp -v port number to see what might be causing trouble. The last one I really stumbled across, only having seen fuser used for investigating busy files and directories in the past. Are there any useful commands I've missed? What's the best tool for translating the output from tcpdump?[stop here if you like] For those that might be interested, the last problem I was trying to solve was a dramatic slowdown in ppp from my home machine to work. So slow that ssh just wouldn't connect, and telnet would take more than five minutes. Characters could take up to a minute to reflect. I was at work and had initiated the ppp connection. Looking at the traffic with tcpdump -l -i ppp0, it was completely dominated by traffic to the nameservers, and with the fuser command on the port numbers being shown, I was able to pin it down to icmplogd and tcplogd which were running on the m/c at home. (No longer.) I have no idea why this slowdown had happened only a couple of times in the past, but previously I'd put it down to a bad line or some ethernet problem at work. (It never seemed to affect the CHAP handshaking, though.) I attacked the problem this time because I was sitting at the work end, so I could easily confirm that everything on the ethernet was functioning. (And I really needed to transfer a file home.) It took me most of an hour to realise I should kill the two offending daemons. I'm still not sure what they were asking the nameservers, but I have a large traffic file available. I'm used to seeing messages like (from memory) bar 255, who is foo, tell bar and foo bar, foo is on 0:1:2:3:4:5 but this stuff was all numerical. Is there something that can print what it thinks it all means? Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Strange network problems on ppp interface
On Tue, Nov 02, 1999 at 04:18:31PM -0800, [EMAIL PROTECTED] wrote: Hm! I reported almost the exact same problem right about the time when kernel 2.2.0 came out. At that time I was running 2.0.36+kerneli and had updated to 2.2.0, and didn't know a thing until our cable modem went out and I needed to use the Ricochet. I'm almost certain it's a kernel issue, because the same system worked fine with a Creative external modem on the same serial port. I've been using kernel 2.2.12 or 2.2.13 since I got the modem, so I'm fairly sure that the kernel isn't the problem here. But you do give interesting information, that it seems to be specifically related to Ricochet's network. I'll browse their web page. Thanks! --Dylan Thurston
Re: Strange network problems on ppp interface
On Tue, 2 Nov 1999, Dylan Thurston wrote: On Tue, Nov 02, 1999 at 04:18:31PM -0800, [EMAIL PROTECTED] wrote: Hm! I reported almost the exact same problem right about the time when kernel 2.2.0 came out. At that time I was running 2.0.36+kerneli and had updated to 2.2.0, and didn't know a thing until our cable modem went out and I needed to use the Ricochet. I'm almost certain it's a kernel issue, because the same system worked fine with a Creative external modem on the same serial port. I've been using kernel 2.2.12 or 2.2.13 since I got the modem, so I'm fairly sure that the kernel isn't the problem here. But you do give interesting information, that it seems to be specifically related to Ricochet's network. I'll browse their web page. H. Maybe whatever it was got fixed in the more recent kernels, if it was actually a kernel problem. I was running stock Debian 2.1 (I don't think I have my disc any longer) with a kernel built from kernel.org Were you running a stock slink without any of the unofficial updates before you upgraded to potato? -- Ferret no baka
Re: Strange network problems on ppp interface
On Tue, Nov 02, 1999 at 07:29:44PM -0800, [EMAIL PROTECTED] wrote: H. Maybe whatever it was got fixed in the more recent kernels, if it was actually a kernel problem. I was running stock Debian 2.1 (I don't think I have my disc any longer) with a kernel built from kernel.org Were you running a stock slink without any of the unofficial updates before you upgraded to potato? The update was basically from potato, version 25 October, to potato, version 30 October, if I have my chronology straight. Another update: ppp (still) works fine over my combo ethernet/modem PCMCIA card. The problem seems to be Ricochet-specific. --Dylan Thurston
Re: Strange network problems on ppp interface
The only other thing I can think of checking is your radio's firmware. Not having access to a Ricochet network right now I can't do any testing. On Tue, 2 Nov 1999, Dylan Thurston wrote: On Tue, Nov 02, 1999 at 07:29:44PM -0800, [EMAIL PROTECTED] wrote: H. Maybe whatever it was got fixed in the more recent kernels, if it was actually a kernel problem. I was running stock Debian 2.1 (I don't think I have my disc any longer) with a kernel built from kernel.org Were you running a stock slink without any of the unofficial updates before you upgraded to potato? The update was basically from potato, version 25 October, to potato, version 30 October, if I have my chronology straight. Another update: ppp (still) works fine over my combo ethernet/modem PCMCIA card. The problem seems to be Ricochet-specific.
Strange network problems on ppp interface
As of yesterday, I've been having some strange problems connecting through my Ricochet modem. I'm able to connect and ping places just fine; however, all useful connections (e.g., telnet, ftp, or http) fail: with telnet, for instance, I get the standard connect messages Trying 128.32.183.1... Connected to bosco.berkeley.edu. Escape character is '^]'. but then no welcome message. There's a tcpdump of such an attempt after my signature. I'd suspect a packet filtering problem, but I'm able to connect using my EtherNet card with no problem. The only change in my configuration that seems like it might be relevant is that I had just upgraded to the latest potato, after 5 days. The only packages upgraded that seem like they could possibly be relevant are hostname and libc6. Anyone have any ideas what could cause this kind of problem? Any help is greatly appreciated. Thanks, Dylan Thurston tcpdump follows: 13:18:58.493742 204.179.128.200.1102 207.69.194.216.ftp: FP 891443817:891443823(6) ack 890014480 win 16060 nop,nop,timestamp 1471784 933090531 (DF) 13:19:13.180204 204.179.128.200.1039 128.32.136.9.domain: 61999+ A? bosco.berkeley.edu. (36) 13:19:14.523709 128.32.136.9.domain 204.179.128.200.1039: 61999* 1/4/7 (260) 13:19:14.527411 204.179.128.200.1103 128.32.183.1.telnet: S 985306204:985306204(0) win 16060 mss 1460,sackOK,timestamp 1473387 0,nop,wscale 0 (DF) [tos 0x10] 13:19:14.873703 128.32.183.1.telnet 204.179.128.200.1103: S 3402697896:3402697896(0) ack 985306205 win 17520 mss 1460 (DF) 13:19:14.873862 204.179.128.200.1103 128.32.183.1.telnet: . ack 1 win 16060 (DF) [tos 0x10] 13:19:14.918216 204.179.128.200.1103 128.32.183.1.telnet: P 1:28(27) ack 1 win 16060 (DF) [tos 0x10] 13:19:17.913712 204.179.128.200.1103 128.32.183.1.telnet: P 1:28(27) ack 1 win 16060 (DF) [tos 0x10] 13:19:22.493719 204.179.128.200.1102 207.69.194.216.ftp: FP 0:6(6) ack 1 win 16060 nop,nop,timestamp 1474184 933090531 (DF) 13:19:23.913708 204.179.128.200.1103 128.32.183.1.telnet: P 1:28(27) ack 1 win 16060 (DF) [tos 0x10] 10 packets received by filter 0 packets dropped by kernel
Re: network problems - sorry for thousands of mails
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
Network Problems
I'm currently having problems with my network, and I'd like to know the best way to go about diagnosing the problem. Are there any utilities that I can use to assist in this process? The problem seems to be that whenever large amounts of information are sent accross the lan to one machine (bristlenose) it freezes, but not when the same info is passed across the network the other way. An example of this is: I log into bristlenose from arowana and cat /vmlinuz and it works fine (the terminal needs to be reset, but it works) I log into arowana from bristlenose and cat /vmlinuz and it is jerky, with the pauses becomming longer until it finally stops altogether, halfway through. This affects almost everythign I do on the net, as arowana currently acts as my gateway, and bristlenose as the client, so sending mail works fine, but retrieving it doesn't. (although retrieving it to arowana works fine) Any help solving this is greatly appreciated, Andrew Clark. PS. I'm subscribed to the digest, so please CC me. begin:vcard n:Clark;Andrew x-mozilla-html:FALSE url:http://www.andrewclark.ddns.org/ adr:;; version:2.1 email;internet:[EMAIL PROTECTED] fn:Andrew Clark end:vcard
Re: Network problems with Vortex Adapter... outputs
q q
Re: Network problems with Vortex Adapter... outputs
thanks for the quick repsonse...I was unable to get to the machine for a week... here's the output you asked for output of ping ping: sendto:operation not performed ping: wrote: 202.186.1.10 64 chars, ret=-1 output of route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 202.186.1.0 0.0.0.0 255.255.255.0 U 0 0 1 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo 0.0.0.0 202.186.1.50 0.0.0.0 UG 1 0 0 eth0 arp -an ?(202.186.1.10) at incomplete on eth0 output of ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 eth0 Link encap:Ethernet HWaddr 00:10:5A:09:26:63 inet addr:202.186.1.65 Bcast:202.186.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU: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: Sat, 17 Apr 1999 10:35:56 -0700 (PDT)From: George Bonser [EMAIL PROTECTED]Reply-To: [EMAIL PROTECTED]To: Karl Gordon [EMAIL PROTECTED]CC: debian-user@lists.debian.orgOn Sat, 17 Apr 1999, Karl Gordon wrote: Hi I'm running Hamm on a Micron Millenia XKU 333 with a 3Com Etherlink 905B PCI installed. The kernel is configured with the correct Vortex driver but the adapter does not connect with or even see the other machines on the network. It has the correct IP address and can 'ping' itself but no other machine can ping it or vice versa. I tried moving it around in the machine but that doesn't work either. I down loaded the latest version of the driver and re-compiled the kernel and nothing. Which kernel version are you using. What is the output ofarp -anafter you have attempted a ping.What are the output ofifconfigroute -n
Re: Network problems with Vortex Adapter... outputs.... kernel 2.0.34
thanks for the quick repsonse...I was unable to get to the machine for a week... here's the output you asked for output of ping ping: sendto:operation not performed ping: wrote: 202.186.1.10 64 chars, ret=-1 output of route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 202.186.1.0 0.0.0.0 255.255.255.0 U 0 0 1 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo 0.0.0.0 202.186.1.50 0.0.0.0 UG 1 0 0 eth0 arp -an ?(202.186.1.10) at incomplete on eth0 output of ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 eth0 Link encap:Ethernet HWaddr 00:10:5A:09:26:63 inet addr:202.186.1.65 Bcast:202.186.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU: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: Sat, 17 Apr 1999 10:35:56 -0700 (PDT)From: George Bonser [EMAIL PROTECTED]Reply-To: [EMAIL PROTECTED]To: Karl Gordon [EMAIL PROTECTED]CC: debian-user@lists.debian.orgOn Sat, 17 Apr 1999, Karl Gordon wrote: Hi I'm running Hamm on a Micron Millenia XKU 333 with a 3Com Etherlink 905B PCI installed. The kernel is configured with the correct Vortex driver but the adapter does not connect with or even see the other machines on the network. It has the correct IP address and can 'ping' itself but no other machine can ping it or vice versa. I tried moving it around in the machine but that doesn't work either. I down loaded the latest version of the driver and re-compiled the kernel and nothing. Which kernel version are you using. What is the output ofarp -anafter you have attempted a ping.What are the output ofifconfigroute -n
