Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
upgrade from hub to switch
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Wed Jun 17, 2009 8:33 am    Post subject: upgrade from hub to switch Reply with quote

Well, I have been bizzi since yesterday to replace a hub which connects my webserver and fileserver.Unfortunately, I havent come up with any solid clue so far why the webserver rejects to get connected to the network when I use the switch.

The switch is here, I am more thinking of software issue as the device works fine tested with 2 computers so far that fileserver and my laptop.

Thanks for the help, if you need more data pls let me know.Here are some few data of the webserver while connected using hub:
#cat /etc/conf.d/net
Quote:
config_eth0=( "dhcp" )
modules_eth0=( "ifplugd" )


#ifconfig
Quote:

eth0 Link encap:Ethernet HWaddr 00:50:8b:e9:59:30
inet addr:192.168.1.6 Bcast:192.168.1.127 Mask:255.255.255.128
inet6 addr: fe80::250:8bff:fee9:5930/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2594 errors:0 dropped:0 overruns:0 frame:0
TX packets:2313 errors:0 dropped:0 overruns:0 carrier:0
collisions:791 txqueuelen:1000
RX bytes:648871 (633.6 KiB) TX bytes:1477373 (1.4 MiB)

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:59 errors:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5722 (5.5 KiB) TX bytes:5722 (5.5 KiB)

_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
alex.blackbit
Advocate
Advocate


Joined: 26 Jul 2005
Posts: 2397

PostPosted: Wed Jun 17, 2009 10:25 am    Post subject: Re: upgrade from hub to switch Reply with quote

muhsinzubeir wrote:
... why the webserver rejects to get connected to the network when I use the switch.

what exactly does "connected" mean?
does your machine think it has a physical connection? i.e. a cable connected, or not? watch the logs when you plug in/out.
net-misc/ethercard-diag should be helpful too, but i never used it.
Back to top
View user's profile Send private message
szczerb
Veteran
Veteran


Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz

PostPosted: Wed Jun 17, 2009 10:34 am    Post subject: Reply with quote

Maybe the port on the switch that you're trying to connect the server to is borked?

Anyway, give us some more info about your network's topology and how exactly the problem manifests, because it seems like it's getting an adress. Or is it the one to give addresses?
Back to top
View user's profile Send private message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Wed Jun 17, 2009 11:23 am    Post subject: Reply with quote

Quote:
what exactly does "connected" mean?

I mean nothing happened, it doesnt get IP.Even if I try manually to give it IP address like ifconfig eth0 192.168.1.10/25 it will take the new IP address but not connected to the network.
Quote:

Maybe the port on the switch that you're trying to connect the server to is borked?

I dont think so as the same port that doesnt work for the webserver, does work well with other machines on the same port.

Topolgy:
==>Router incl.Wifi and dhcp server

||==>3com switch (fileserver+webserver)

||==>Wifi-laptops

||==>desktops

P:S
***Not sure if that diagram clear, but the router(4ports) connects laptops, desktops, and 3Com switch which holds the 2 servers fileserver && webserver.
***Let me go plugin a monitor to those machines in there and see if I can find something else

Thanks for the input.....
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
szczerb
Veteran
Veteran


Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz

PostPosted: Wed Jun 17, 2009 11:34 am    Post subject: Reply with quote

Maybe you accidentally set more then one interface of the network with the same mac? And the switch ignores the second one instead of sending it both ways or going into hub mode like it should? And are you sure the cable is healthy? Other then that I have no idea...

EDIT switch -> hub


Last edited by szczerb on Wed Jun 17, 2009 11:46 am; edited 1 time in total
Back to top
View user's profile Send private message
ndse2112
Tux's lil' helper
Tux's lil' helper


Joined: 21 May 2007
Posts: 100

PostPosted: Wed Jun 17, 2009 11:35 am    Post subject: Reply with quote

Are your interfaces and/or switch ports hardcoded to a speed/duplex or are they set to autoneg?

Try setting the interfaces in your machine to autoneg and see if they will get a link.
Back to top
View user's profile Send private message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Wed Jun 17, 2009 12:48 pm    Post subject: Reply with quote

I think I have found the problem, but still dont know how to solve.
I think with the 3Com switch, a slight delay happened and the dhcplient get a weard IP address(old lease or something).I have seen this on the messeages generate as it can be seen here below:

Quote:
Jun 17 18:12:48 webserver ifplugd(eth0)[7700]: Exiting.
Jun 17 18:12:50 webserver ifplugd(eth0)[11123]: ifplugd 0.28 initializing.
Jun 17 18:12:50 webserver ifplugd(eth0)[11123]: Using interface eth0/00:50:8B:E9:59:30 with driver <e100> (version: 3.5.23-k6-NAPI)
Jun 17 18:12:50 webserver ifplugd(eth0)[11123]: Using detection mode: SIOCETHTOOL
Jun 17 18:12:50 webserver ifplugd(eth0)[11123]: Initialization complete, link beat not detected.
Jun 17 18:12:50 webserver rc-scripts: WARNING: apache2 is scheduled to start when net.eth0 has started.
Jun 17 18:12:50 webserver rc-scripts: WARNING: netmount is scheduled to start when net.eth0 has started.
Jun 17 18:12:50 webserver rc-scripts: WARNING: nfsmount is scheduled to start when net.eth0 has started.
Jun 17 18:12:50 webserver rc-scripts: WARNING: proftpd is scheduled to start when net.eth0 has started.
Jun 17 18:12:50 webserver rc-scripts: WARNING: sshd is scheduled to start when net.eth0 has started.
Jun 17 18:13:18 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:13:19 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 17 18:13:21 webserver ifplugd(eth0)[11123]: client: eth0: dhcpcd 4.0.7 starting
Jun 17 18:13:21 webserver dhcpcd[11549]: eth0: dhcpcd 4.0.7 starting
Jun 17 18:13:21 webserver ifplugd(eth0)[11123]: client: eth0: broadcasting for a lease
Jun 17 18:13:21 webserver dhcpcd[11549]: eth0: broadcasting for a lease
Jun 17 18:13:31 webserver ifplugd(eth0)[11123]: client: eth0: timed out
Jun 17 18:13:31 webserver ifplugd(eth0)[11123]: client: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Jun 17 18:13:31 webserver dhcpcd[11549]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Jun 17 18:13:31 webserver ifplugd(eth0)[11123]: client: eth0: probing for an IPV4LL address
Jun 17 18:13:31 webserver dhcpcd[11549]: eth0: probing for an IPV4LL address
Jun 17 18:13:31 webserver ifplugd(eth0)[11123]: client: eth0: checking 169.254.1.12 is available on attached networks
Jun 17 18:13:31 webserver dhcpcd[11549]: eth0: checking 169.254.1.12 is available on attached networks
Jun 17 18:13:36 webserver ifplugd(eth0)[11123]: client: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:13:36 webserver dhcpcd[11549]: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:13:37 webserver ifplugd(eth0)[11123]: client: * Starting NFS sm-notify ...
Jun 17 18:13:37 webserver sm-notify[11773]: Already notifying clients; Exiting!
Jun 17 18:13:37 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:37 webserver ifplugd(eth0)[11123]: client: * Mounting NFS filesystems ...
Jun 17 18:13:37 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:37 webserver ifplugd(eth0)[11123]: client: * Mounting network filesystems ...
Jun 17 18:13:37 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:38 webserver ifplugd(eth0)[11123]: client: * Starting apache2 ...
Jun 17 18:13:42 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:42 webserver ifplugd(eth0)[11123]: client: * Checking proftpd configuration ...
Jun 17 18:13:42 webserver ifplugd(eth0)[11123]: client: Checking syntax of configuration file
Jun 17 18:13:42 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:42 webserver ifplugd(eth0)[11123]: client: * Starting proftpd ...
Jun 17 18:13:42 webserver proftpd[11942]: webserver.mambo-tech.net - ProFTPD 1.3.2 (stable) (built Fri Apr 17 15:30:43 CEST 2009) standalone mode STARTUP
Jun 17 18:13:42 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:43 webserver ifplugd(eth0)[11123]: client: * Starting sshd ...
Jun 17 18:13:43 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:13:43 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:14:44 webserver dhcpcd[11559]: eth0: broadcasting for a lease
trying directly to the router now****
Jun 17 18:17:13 webserver proftpd[11942]: webserver.mambo-tech.net - ProFTPD 1.3.2 standalone mode SHUTDOWN
Jun 17 18:17:13 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:17:14 webserver ifplugd(eth0)[11123]: client: * Stopping sshd ...
Jun 17 18:17:14 webserver ifplugd(eth0)[11123]: client:  [ ok ]
Jun 17 18:17:15 webserver ifplugd(eth0)[11123]: client: eth0: sending signal 1 to pid 11559
Jun 17 18:17:15 webserver ifplugd(eth0)[11123]: client: eth0: waiting for pid 11559 to exit
Jun 17 18:17:15 webserver dhcpcd[12548]: eth0: sending signal 1 to pid 11559
Jun 17 18:17:15 webserver dhcpcd[12548]: eth0: waiting for pid 11559 to exit
Jun 17 18:17:15 webserver dhcpcd[11559]: eth0: received SIGHUP, releasing lease
Jun 17 18:17:15 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:18:45 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:18:47 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 17 18:18:48 webserver ifplugd(eth0)[11123]: client: eth0: dhcpcd 4.0.7 starting
Jun 17 18:18:48 webserver dhcpcd[13017]: eth0: dhcpcd 4.0.7 starting
Jun 17 18:18:48 webserver ifplugd(eth0)[11123]: client: eth0: broadcasting for a lease
Jun 17 18:18:48 webserver dhcpcd[13017]: eth0: broadcasting for a lease
Jun 17 18:18:50 webserver ifplugd(eth0)[11123]: client: eth0: carrier lost
Jun 17 18:18:50 webserver dhcpcd[13017]: eth0: carrier lost
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: client: eth0: timed out
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: client:  [ !! ]
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: client:  [ !! ]
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: Link beat lost.
Jun 17 18:19:15 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Jun 17 18:19:16 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:20:01 webserver cron[13420]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jun 17 18:21:52 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:21:53 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 17 18:21:55 webserver ifplugd(eth0)[11123]: client: eth0: dhcpcd 4.0.7 starting
Jun 17 18:21:55 webserver dhcpcd[13863]: eth0: dhcpcd 4.0.7 starting
Jun 17 18:21:55 webserver ifplugd(eth0)[11123]: client: eth0: broadcasting for a lease
Jun 17 18:21:55 webserver dhcpcd[13863]: eth0: broadcasting for a lease
Jun 17 18:22:05 webserver ifplugd(eth0)[11123]: client: eth0: timed out
Jun 17 18:22:05 webserver ifplugd(eth0)[11123]: client: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Jun 17 18:22:05 webserver dhcpcd[13863]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Jun 17 18:22:05 webserver ifplugd(eth0)[11123]: client: eth0: probing for an IPV4LL address
Jun 17 18:22:05 webserver dhcpcd[13863]: eth0: probing for an IPV4LL address
Jun 17 18:22:05 webserver ifplugd(eth0)[11123]: client: eth0: checking 169.254.17.180 is available on attached networks
Jun 17 18:22:05 webserver dhcpcd[13863]: eth0: checking 169.254.17.180 is available on attached networks
Jun 17 18:22:10 webserver ifplugd(eth0)[11123]: client: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:22:10 webserver dhcpcd[13863]: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:22:10 webserver ifplugd(eth0)[11123]: Program executed successfully.
Trying to give manual IP address to the webserver****
Jun 17 18:22:55 webserver dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jun 17 18:22:55 webserver dhclient:
Jun 17 18:22:56 webserver dhclient: Listening on LPF/eth0/00:50:8b:e9:59:30
Jun 17 18:22:56 webserver dhclient: Sending on LPF/eth0/00:50:8b:e9:59:30
Jun 17 18:22:56 webserver dhclient: Sending on Socket/fallback
Jun 17 18:22:58 webserver dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 17 18:23:05 webserver dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 17 18:23:18 webserver dhcpcd[13868]: eth0: broadcasting for a lease
Jun 17 18:23:19 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jun 17 18:23:27 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jun 17 18:24:21 webserver dhcpcd[13868]: eth0: probing for an IPV4LL address
Jun 17 18:24:21 webserver dhcpcd[13868]: eth0: checking 169.254.222.153 is available on attached networks
Jun 17 18:24:26 webserver dhcpcd[13868]: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:25:34 webserver dhcpcd[13868]: eth0: broadcasting for a lease
Jun 17 18:26:38 webserver dhcpcd[13868]: eth0: probing for an IPV4LL address
Jun 17 18:26:38 webserver dhcpcd[13868]: eth0: checking 169.254.2.107 is available on attached networks
Jun 17 18:26:43 webserver dhcpcd[13868]: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:27:51 webserver dhcpcd[13868]: eth0: broadcasting for a lease
Jun 17 18:28:55 webserver dhcpcd[13868]: eth0: probing for an IPV4LL address
Jun 17 18:28:55 webserver dhcpcd[13868]: eth0: checking 169.254.3.65 is available on attached networks
Jun 17 18:29:00 webserver dhcpcd[13868]: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:30:01 webserver cron[13917]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jun 17 18:30:01 webserver cron[13918]: (root) CMD (/usr/bin/wget -O - -q -t 1 http://mambo-tech.net/cron.php)
Jun 17 18:30:09 webserver dhcpcd[13868]: eth0: broadcasting for a lease
Jun 17 18:31:13 webserver dhcpcd[13868]: eth0: probing for an IPV4LL address
Jun 17 18:31:13 webserver dhcpcd[13868]: eth0: checking 169.254.103.77 is available on attached networks
Jun 17 18:31:19 webserver dhcpcd[13868]: eth0: using IPv4LL address 0.0.0.0
Jun 17 18:31:50 webserver dhclient: Internet Systems Consortium DHCP Client V3.1.1-Gentoo
Jun 17 18:31:50 webserver dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jun 17 18:31:50 webserver dhclient: All rights reserved.
Jun 17 18:31:50 webserver dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jun 17 18:31:50 webserver dhclient:
Jun 17 18:31:51 webserver dhclient: Listening on LPF/eth0/00:50:8b:e9:59:30
Jun 17 18:31:51 webserver dhclient: Sending on LPF/eth0/00:50:8b:e9:59:30
Jun 17 18:31:51 webserver dhclient: Sending on Socket/fallback
Jun 17 18:31:51 webserver dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 17 18:31:59 webserver dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 17 18:32:12 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jun 17 18:32:19 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Jun 17 18:32:26 webserver dhcpcd[13868]: eth0: broadcasting for a lease
Jun 17 18:32:33 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Jun 17 18:32:51 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Jun 17 18:33:30 webserver dhcpcd[13868]: eth0: probing for an IPV4LL address
Jun 17 18:33:30 webserver dhcpcd[13868]: eth0: checking 169.254.10.252 is available on attached networks
Jun 17 18:33:35 webserver dhcpcd[13868]: eth0: using IPv4LL address 0.0.0.0
Attaching the hub, correctly workin...
Jun 17 18:35:34 webserver dhcpcd[13868]: eth0: carrier lost
Jun 17 18:35:39 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Jun 17 18:35:41 webserver ifplugd(eth0)[11123]: client: eth0: sending signal 1 to pid 13868
Jun 17 18:35:41 webserver dhcpcd[13868]: eth0: received SIGHUP, releasing lease
Jun 17 18:35:41 webserver dhcpcd[14280]: eth0: sending signal 1 to pid 13868
Jun 17 18:35:41 webserver ifplugd(eth0)[11123]: client: eth0: waiting for pid 13868 to exit
Jun 17 18:35:41 webserver dhcpcd[14280]: eth0: waiting for pid 13868 to exit
Jun 17 18:35:41 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:35:44 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:35:45 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 17 18:35:47 webserver ifplugd(eth0)[11123]: client: eth0: dhcpcd 4.0.7 starting
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: dhcpcd 4.0.7 starting
Jun 17 18:35:47 webserver ifplugd(eth0)[11123]: client: eth0: broadcasting for a lease
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: broadcasting for a lease
Jun 17 18:35:47 webserver ifplugd(eth0)[11123]: client: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:35:47 webserver ifplugd(eth0)[11123]: client: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:35:52 webserver ifplugd(eth0)[11123]: client: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:35:52 webserver dhcpcd[14742]: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:35:52 webserver ifplugd(eth0)[11123]: client: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:35:52 webserver dhcpcd[14742]: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:35:52 webserver ifplugd(eth0)[11123]: Program executed successfully.
Repeating the hub attachment....
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: broadcasting for a lease
Jun 17 18:35:47 webserver ifplugd(eth0)[11123]: client: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:35:47 webserver dhcpcd[14742]: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:35:47 webserver ifplugd(eth0)[11123]: client: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:35:52 webserver ifplugd(eth0)[11123]: client: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:35:52 webserver dhcpcd[14742]: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:35:52 webserver ifplugd(eth0)[11123]: client: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:35:52 webserver dhcpcd[14742]: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:35:52 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:36:37 webserver ifplugd(eth0)[11123]: Link beat lost.
Jun 17 18:36:38 webserver dhcpcd[14749]: eth0: carrier lost
Jun 17 18:36:41 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:36:42 webserver dhcpcd[14749]: eth0: carrier acquired
Jun 17 18:36:42 webserver dhcpcd[14749]: eth0: rebinding lease of 192.168.1.6
Jun 17 18:36:42 webserver dhcpcd[14749]: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:36:42 webserver dhcpcd[14749]: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:37:32 webserver dhcpcd[15582]: eth0: broadcasting for a lease
Jun 17 18:37:32 webserver ifplugd(eth0)[11123]: client: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:37:32 webserver dhcpcd[15582]: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:37:32 webserver ifplugd(eth0)[11123]: client: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:37:32 webserver dhcpcd[15582]: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:37:38 webserver ifplugd(eth0)[11123]: client: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:37:38 webserver dhcpcd[15582]: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:37:38 webserver ifplugd(eth0)[11123]: client: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:37:38 webserver dhcpcd[15582]: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:37:39 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:37:50 webserver ifplugd(eth0)[11123]: Link beat lost.
Jun 17 18:37:50 webserver dhcpcd[15589]: eth0: carrier lost
Jun 17 18:37:56 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Jun 17 18:37:57 webserver ifplugd(eth0)[11123]: client: eth0: sending signal 1 to pid 15589
Jun 17 18:37:57 webserver dhcpcd[15589]: eth0: received SIGHUP, releasing lease
Jun 17 18:37:57 webserver ifplugd(eth0)[11123]: client: eth0: waiting for pid 15589 to exit
Jun 17 18:37:57 webserver dhcpcd[15957]: eth0: sending signal 1 to pid 15589
Jun 17 18:37:57 webserver dhcpcd[15957]: eth0: waiting for pid 15589 to exit
Jun 17 18:37:57 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:38:00 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:38:02 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 17 18:38:03 webserver ifplugd(eth0)[11123]: client: eth0: dhcpcd 4.0.7 starting
Jun 17 18:38:03 webserver dhcpcd[16418]: eth0: dhcpcd 4.0.7 starting
Jun 17 18:38:03 webserver ifplugd(eth0)[11123]: client: eth0: broadcasting for a lease
Jun 17 18:38:03 webserver dhcpcd[16418]: eth0: broadcasting for a lease
Jun 17 18:38:03 webserver ifplugd(eth0)[11123]: client: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:38:03 webserver dhcpcd[16418]: eth0: offered 192.168.1.6 from 192.168.1.1
Jun 17 18:38:03 webserver ifplugd(eth0)[11123]: client: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:38:03 webserver dhcpcd[16418]: eth0: checking 192.168.1.6 is available on attached networks
Jun 17 18:38:09 webserver dhcpcd[16418]: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:38:09 webserver ifplugd(eth0)[11123]: client: eth0: acknowledged 192.168.1.6 from 192.168.1.1
Jun 17 18:38:09 webserver dhcpcd[16418]: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:38:09 webserver ifplugd(eth0)[11123]: client: eth0: leased 192.168.1.6 for 86400 seconds
Jun 17 18:38:09 webserver ifplugd(eth0)[11123]: Program executed successfully.

_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Wed Jun 17, 2009 1:06 pm    Post subject: Reply with quote

ndse2112 wrote:
Are your interfaces and/or switch ports hardcoded to a speed/duplex or are they set to autoneg?

Try setting the interfaces in your machine to autoneg and see if they will get a link.


can you explain more, i havent set anything...i just bought that switch and decide to replace my hub.Which I basically suspect it to be a little bit slow....

but the upgrade goes as you can see in the thread...my webserver get wrong IP address :evil:

PS
Trying to unmerge any dhcp stuffs...
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
ndse2112
Tux's lil' helper
Tux's lil' helper


Joined: 21 May 2007
Posts: 100

PostPosted: Wed Jun 17, 2009 4:25 pm    Post subject: Reply with quote

Jun 17 18:18:45 webserver ifplugd(eth0)[11123]: Link beat detected.
Jun 17 18:18:47 webserver ifplugd(eth0)[11123]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 17 18:18:48 webserver ifplugd(eth0)[11123]: client: eth0: dhcpcd 4.0.7 starting
Jun 17 18:18:48 webserver dhcpcd[13017]: eth0: dhcpcd 4.0.7 starting
Jun 17 18:18:48 webserver ifplugd(eth0)[11123]: client: eth0: broadcasting for a lease
Jun 17 18:18:48 webserver dhcpcd[13017]: eth0: broadcasting for a lease
Jun 17 18:18:50 webserver ifplugd(eth0)[11123]: client: eth0: carrier lost
Jun 17 18:18:50 webserver dhcpcd[13017]: eth0: carrier lost
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: client: eth0: timed out
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: client:  [ !! ]
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: client:  [ !! ]
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: Program executed successfully.
Jun 17 18:19:08 webserver ifplugd(eth0)[11123]: Link beat lost.


From these few messages, it doesnt look like that nic is staying linked with your switch. The 169.254.x.x is the APIPA range (Automatic Private IP Address). An address out of that space will be assigned to the interface when the interface cannot get a response from the dhcp server.


Do the NIC and the switch link lights stay on when you plug your nic into the switch?

Can you try a different cable?



You can use a tool like mii-tool or ethtool (sys-apps/net-tools and/or sys-apps/ethtool) to look at the link status of the interface:
callisto ~ # mii-tool eth0
eth0: negotiated 1000baseT-FD flow-control, link ok
callisto ~ # ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
callisto ~ #
Back to top
View user's profile Send private message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Wed Jun 17, 2009 6:58 pm    Post subject: Reply with quote

Thanks man....
I will have to look at it tomorrow....enough ambarrasment of this switch for today...
I really didnt expect this, I am also thinking that I might quit for a while on that webserver....to reduce costs and maintance headache...
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Thu Jun 18, 2009 10:14 am    Post subject: Reply with quote

I took that webserver to my living room and make connection directly to the router is OK...using hub also OK...only the via the switch is NO GOOD tried different cables, different tools, net-setup,no luck...mmh

**Running emerge -avuDN world on that webserver, no idea but some weard stuffs happening in there.Not cable nor the switching nor router nor MAC conflicts.May be the upgrade will bring some good :) .

**Integrated webserver into fileserver, and put my website back online for the moment.

P:S
If the switch totally fails, then the server will have to off and used only for maintance issues or backup in the near future when I have time to upgrade its hardware.It does have pretty old stuffs in there pent III :D

May be this is for learning purposes if I run
Quote:
ifconfig eth0 192.168.1.10/25
, it looks from ifconfig that the IP you manually give is submitedd to the machine...but normally I dont get connection as if there is another file that these DHCP software updates.I would guess it would be /etc/resolv.conf....but this file is normally there which is left by the DHCP clients...am I missing something on this manual procedure?
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
alex.blackbit
Advocate
Advocate


Joined: 26 Jul 2005
Posts: 2397

PostPosted: Thu Jun 18, 2009 11:31 am    Post subject: Reply with quote

muhsinzubeir,

as i already wrote before, please find out if the box thinks it has a physical connection or not.
run (as root): "tail -f /var/log/everything/current" or "tail -f /var/log/messages", depending on your syslog daemon and then plug the cable in.
that should bring some light on the situation.
Back to top
View user's profile Send private message
muhsinzubeir
l33t
l33t


Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin

PostPosted: Thu Jun 18, 2009 12:08 pm    Post subject: Reply with quote

alex.blackbit wrote:
muhsinzubeir,

as i already wrote before, please find out if the box thinks it has a physical connection or not.
run (as root): "tail -f /var/log/everything/current" or "tail -f /var/log/messages", depending on your syslog daemon and then plug the cable in.
that should bring some light on the situation.


I think yes, the machine think there is a link but the machine doesnt get correct data using DHCP.
Normally I get all my machines online with DHCP server, but not this time :evil:

connect cables with the switch:
Quote:
tail -f /var/log/messeges

Quote:

Jun 18 17:55:14 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 18 17:55:17 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 18 17:55:20 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jun 18 17:55:28 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jun 18 17:55:36 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
Jun 18 17:55:55 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Jun 18 17:56:08 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jun 18 17:56:15 webserver dhclient: No DHCPOFFERS received.
Jun 18 17:56:15 webserver dhclient: Trying recorded lease 192.168.1.6
Jun 18 17:56:18 webserver netplugd[17946]: eth0: state INNING pid 31507 exited status 0
Jun 18 17:56:37 webserver netplugd[17946]: eth0: state ACTIVE flags 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 -> 0x000 01003 UP,BROADCAST,MULTICAST
Jun 18 17:56:37 webserver netplugd[31929]: /etc/netplug.d/netplug eth0 out -> pid 31929
Jun 18 17:56:39 webserver netplugd[17946]: eth0: state OUTING pid 31929 exited status 0
Jun 18 17:56:41 webserver netplugd[17946]: eth0: state INACTIVE flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BRO ADCAST,RUNNING,MULTICAST,10000
Jun 18 17:56:41 webserver netplugd[32315]: /etc/netplug.d/netplug eth0 in -> pid 32315
Jun 18 17:56:47 webserver dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 18 17:56:53 webserver dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 18 17:57:01 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jun 18 17:57:09 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jun 18 17:57:21 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Jun 18 17:57:35 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
Jun 18 17:57:54 webserver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jun 18 17:58:02 webserver dhclient: No DHCPOFFERS received.
Jun 18 17:58:02 webserver dhclient: Trying recorded lease 192.168.1.6
Jun 18 17:58:05 webserver netplugd[17946]: eth0: state INNING pid 32315 exited status 0


Code:
mii-diag eth0

Quote:
Basic registers of MII PHY #1: 3000 782d 02a8 0154 05e1 45e1 0001 0000.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
End of basic transceiver information.


Code:
ethtool eth0
Quote:

eth0: negotiated 100baseTx-FD flow-control, link ok
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes


Edit:
System hangs when entering runlevel 3 at starting point of eth0 after kernel upgrade.Aaagh I will look at this later on, taking a break on the issue....
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum