You are not logged in.

#1 2009-04-13 14:03:45

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

[SOLVED]Network problem after upgrade!

Hello,

After I upgraded Xorg, the kernel and a lot of other packages, I can 't connect to the internet with Arch. When I start Arch the network is up and running, but when I use Firefox I can 't connect to any webpage and when I ping google.com, he can 't find google.com. So I tried to restart my network and I got the following error: eth0 add_adress: No buffer space available. Starting kernel 2.6.28 doesn 't solve the problem. Could anyone help me?

Jozef

P.s. Please, forgive me my spelling and gramatic mistakes.

Last edited by jozef00 (2009-05-02 10:18:45)

Offline

#2 2009-04-14 14:35:01

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Hello,

I don't had enough time for the problem yesterday, so I announced the problem as solved. But now I know that I have enough time and the problem isn't solved, so I look forward for your help.

Jozef

Offline

#3 2009-04-23 18:19:24

mattduckman
Member
Registered: 2009-04-23
Posts: 3

Re: [SOLVED]Network problem after upgrade!

i too get this error. my server hasn't rebooted in several months, but starting today i get these errors during bootup:

dhcpcd: eth0: send_arp: Message too long
nmbd:  ... subnetdb.c:create_subnets(206)
nmbd: ... create_subnets: No local IPv4 non-loopback interfaces!
nmbd:  ... subnetdb.c:create_subnets(207)
nmbd: ... create_subnets: Waiting for an interface to appear ...

additionally, when i try to start the network, i get:

dhcpcd: eth0: add_address: No buffer space available

any help would be fantastic

Last edited by mattduckman (2009-04-23 18:51:02)

Offline

#4 2009-04-24 15:35:55

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Hi,

Here are some outputs for the person that's able to help:

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F
          UP BROADCAST RUNNING MULTICAST  MTU:0  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1609 (1.5 Kb)  TX bytes:810 (810.0 b)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

ifonfig -a

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F
          UP BROADCAST RUNNING MULTICAST  MTU:0  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1609 (1.5 Kb)  TX bytes:810 (810.0 b)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

route

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

dhclient eth0

There is already a pid file /var/run/dhclient.pid with pid 3043
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No buffer space available
Listening on LPF/eth0/00:11:2f:ed:73:3f
Sending on   LPF/eth0/00:11:2f:ed:73:3f
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
send_packet: Message too long
DHCPREQUEST on eth0 to 255.255.255.255 port 67
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
send_packet: Message too long
No DHCPOFFERS received.
Trying recorded lease 192.168.0.3
SIOCSIFADDR: No buffer space available
SIOCSIFNETMASK: Cannot assign requested address
SIOCSIFBRDADDR: Cannot assign requested address
connect: Network is unreachable
SIOCSIFADDR: No buffer space available
No working leases in persistent database - sleeping.

/etc/rc.conf

# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Amsterdam"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(mii vboxnetflt vboxdrv  slhc via-rhine ac97_bus snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-mpu401-uart snd-ac97-codec snd-via82xx soundcore)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="linuxpc"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng !iptables network netfs crond @alsa @samba @cups hal @dbus @fam)

Please could someone help us?

Jozef

Offline

#5 2009-04-24 18:10:11

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED]Network problem after upgrade!

@jozef00
For some reason the MTU of your connection is set to zero maybe thats the problem. Which network card are you using? Maybe someone else with a similar card can check if it works or not.

@mattduckman
Which network card do you have? Same as above, maybe there is some problem with the driver in a more recent kernel.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#6 2009-04-24 18:37:52

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Thanks for your reaction R00KIE!

My networkcard is a Via Rhine II Fast Ethernet Adapter

And I got some other questions for you!

1) How could I change the MTU and to what must I change it?
2) As I change it and it is wrong, will Arch then still boot?

Jozef

Last edited by jozef00 (2009-04-24 18:38:34)

Offline

#7 2009-04-25 02:09:44

mattduckman
Member
Registered: 2009-04-23
Posts: 3

Re: [SOLVED]Network problem after upgrade!

for some reason, lspci isn't installed on my computer. Is there another way to check for hardware?

i probably have the same or similar card because i have a VIA CPU and other VIA components in my computer.

Offline

#8 2009-04-25 12:38:49

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED]Network problem after upgrade!

@jozef00
To change the mtu size you need to use ifconfig. You should be able to do it with

ifconfig eth0 mtu 1500

1500 is the default mtu size, if it doesn't work then unless it outputs a different error message then I'm out of ideas.
Arch will always boot, you will set the mtu only after you finish booting (manually at first just to test) and later if it works it will be set at the end of the boot process (unless someone else can suggest a better way to do it).

@mattduckman
lspci is owned by the pciutils package, you should be able to get it with

pacman -S pciutils

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#9 2009-04-26 15:34:03

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Hello,

After

ifconfig eth0 mtu 1500

I got the following output:

/etc/rc.d/network restart

:: Stopping Network                                                                                                                                   [DONE]
:: Starting Network                                                                                                                                    [DONE]

dhclient eth0

There is already a pid file /var/run/dhclient.pid with pid 3445
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:11:2f:ed:73:3f
Sending on   LPF/eth0/00:11:2f:ed:73:3f
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.3 -- renewal in 119285 seconds.

ping to a private IP

ping -c 3 192.168.0.1
connect: Network is unreachable

1) ifconfig
2) ifconfig -a
3) route

I will post them over 10 minutes.

Although it doesn't work, we are on the right way. Perhaps it will work when I set the MTU to 1500 during boot.

I look forward for someone that can solve my problem. But in the meantime thanks to R00KIE for his help.

Jozef

Offline

#10 2009-04-26 15:52:17

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

By a number:
1) Is the MTU only set before a network restart.
2) Is the MTU set before and after a network restart.

route (no number)

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

I have to go to my dinner. I will give you the other outputs after that.

Jozef

Offline

#11 2009-04-26 16:45:42

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

By a number:
1) Is the MTU only set before a network restart.
2) Is the MTU set before and after a network restart.

ifconfig NUMBER1

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F 
          UP BROADCAST RUNNING MULTICAST  MTU:0  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4850 (4.7 Kb)  TX bytes:3066 (2.9 Kb)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

ifconfig NUMBER2

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6030 (5.8 Kb)  TX bytes:4274 (4.1 Kb)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

ifconfig -a NUMBER1

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F 
          UP BROADCAST RUNNING MULTICAST  MTU:0  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7210 (7.0 Kb)  TX bytes:5412 (5.2 Kb)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

ifconfig -a NUMBER2

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8390 (8.1 Kb)  TX bytes:6460 (6.3 Kb)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

With kind regards and full with hope,

Jozef

Last edited by jozef00 (2009-04-26 16:46:37)

Offline

#12 2009-04-26 17:21:56

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED]Network problem after upgrade!

As far as I know the mtu size is set to the default value when you insert the module/driver or bring the interface up, for me it's always 1500, I don't need to do anything.

To try to get everything configured correctly get hold of the dhclient package and install it.
Then do

/etc/rc.d/network stop
ifconfig eth0 mtu 1500 up
dhclient

then check if you got an ip with ifconfig, check /etc/resolv.conf to see if you got the dns servers configured properly by dhclient and check the output of "route -n" to check if the routes are ok.

Edit:
You didn't have the outputs of ifconfig while I was writing the reply .... you are not getting any IP. Do you have a router configured to give IPs with dhcp? Do you have things setup properly in rc.conf?

Last edited by R00KIE (2009-04-26 17:25:10)


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#13 2009-04-27 14:10:37

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Hello R00KIE,

Here are the outputs of the commands you gave me:

/etc/rc.d/network stop

:: Stopping Network                                      [DONE]

dhclient

Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No buffer space available
Listening on LPF/eth0/00:11:2f:ed:73:3f
Sending on   LPF/eth0/00:11:2f:ed:73:3f
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
SIOCSIFADDR: No buffer space available
SIOCSIFNETMASK: Cannot assign requested address
SIOCSIFBRDADDR: Cannot assign requested address
SIOCADDRT: No such process
bound to 192.168.0.3 -- renewal in 129128 seconds.

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:11:2F:ED:73:3F 
          inet6 addr: fe80::211:2fff:feed:733f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2139 (2.0 Kb)  TX bytes:1620 (1.5 Kb)
          Interrupt:23 Base address:0xec00

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

ping -c 3 192.168.0.1

connect: Network is unreachable

route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

I haven't change last time rc.conf so I think it is fine. My router is set to give IP's by DHCP, we got several Windows PC's in the house and they all work, so the DHCP-server works. Because a ping to an IP-adress doesn't work too, I don't think it is a DNS problem. I got a dual-boot PC with Arch and Windows, under Windows I got network, but not under Arch. So the network card works too.

Jozef

Offline

#14 2009-04-27 14:37:02

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

I don't understand the output of route -n, so I can't check if the output is OK, because I am not an networkspecialist.

Jozef

Offline

#15 2009-04-27 17:13:06

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED]Network problem after upgrade!

Thats odd, dhclient does fail to do something and its not being able to get/set an ipv4 address. and I'm running out of ideas hmm
Check this http://wiki.archlinux.org/index.php/Con … _WOL_issue and make sure that you don't have something similar in your card configuration settings under windows (you mention dual boot, it's just a guess).

You may also want to try this http://wiki.archlinux.org/index.php/IPv … the_Module and give the normal network setup and/or dhclient another go, although I guess it will not change much. Don't forget to run these things as root or using sudo.

As for the route command it should output something like (in your case it may be slightly different)

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 eth0

If nothing works then I guess you need to check if an older kernel works (the one you had before the update), if it does then most probably there is a driver bug.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#16 2009-04-28 17:15:36

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Hello R00KIE,

I got some good news. The network problem is nearly solved. As you can see in my rc.conf, there are two modules set before the driver module of my network card (via-rhine). With the new kernel I haven't rebuild them, so they are not loaded. Now I removed them from the module line and now I can start my network as root with the following commands:

ifconfig eth0 mtu 1500 up
dhclient

Now I am able to internet, but the question is now how I could set the MTU during boot? I thank you a lot R00KIE!

Jozef

Offline

#17 2009-04-28 20:08:27

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED]Network problem after upgrade!

I guess the normal network setup didn't work for you then, even after removing the modules you don't need from the modules line, most stuff you have there should be automatically loaded, I just don't know about slhc. Even the network module should be loaded automatically.

To setup everything on boot I guess you can remove "network" from your daemons line, then add

ifconfig eth0 mtu 1500 up
dhclient

to /etc/rc.local and it should do everything for you on every boot, it's not a pretty solution but should work.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#18 2009-04-29 12:03:28

jozef00
Member
From: 127.0.0.1
Registered: 2008-10-12
Posts: 44

Re: [SOLVED]Network problem after upgrade!

Hello R00KIE,

It works, problem solved. Thank you for your help!!!!!!!!! I will wait with announcing the problem as solved until the problem is solved by mattduckman.

Jozef

Last edited by jozef00 (2009-04-29 12:03:54)

Offline

#19 2009-05-01 21:55:28

mattduckman
Member
Registered: 2009-04-23
Posts: 3

Re: [SOLVED]Network problem after upgrade!

R00KIE, i never got this problem resolved, but thanks for your help.

i ended up replacing the network device

Offline

Board footer

Powered by FluxBB