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
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
certa
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
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
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
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/ne
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
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 anot
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
MaskI
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
10 matches
Mail list logo
