Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a rather strange situation on my hands. I have a production web server that was working just fine with two network interfaces, interface A connected to the .0 subnet on the private network, and interface B connected the public network either interface is reachable from any machine on our private and public network. Took it down and updated it with emerge. Brought it back up and now machines on the .0 subnet can only access the machine through interface A, and machines on the public network as well as the .2 subnet ( the .0 and .2 subnets comprise the private network) on the private network can only access the machine through interface B.
There is a second backup web server which is in use now that is setup the same as this machine (different IP's of course) and it has no problem communicating to the .0, .2, and public network segments over both interfaces, just as this server did before the update. We checked with ipconfig and netstat and they are configured the same. Neither are running iptables or any other ip filter/ firewall program. Traceroutes are proper, one hop to correct subnet. The Physical network has not changed and the configuration of the router is the same, checked over everything by eye to make sure. Saw that /etc/conf.d/net has a new syntax. Tried changing it's entries to reflect that and no change. Tried bringing down the aliases, and changing the ip addresses. Tried changing the netmask (the public network is a 255.255.254.0 but the router is configured to allow the netmask of a public machine be either 255.255.254.0 or 255.255.255.0 )
Here is the interesting thing though. If you bring down interface A (the .0 private subnet) then the .0, .2, and the public networks can all reach the machine through interface B no problems. Unfortunately our setup requires an interface on that private subnet.
Does anyone have any ideas as to what is causing this?
ifconfig and netstat output for the server and it's perfectly working backup:
I'm Aaron, the other admin of this machine. To be a little more precise, below is a list of the packages that were emerged on that day. Do you see anything that could be causing our problems? One more possible symptom. I always reboot machines before I start updates. That way I can be sure that a later problem during boot was caused by the update and wasn't a preexisting condition. The machine rebooted fine before the updates. Afterwards, I had to reinstall Grub on the MBR as it wasn't detecting it.
Code:
1137220129: >>> emerge (1 of 129) sys-process/cronbase-0.3.2 to /
1137220143: >>> emerge (2 of 129) sys-devel/binutils-config-1.8-r6 to /
1137220156: >>> emerge (3 of 129) sys-devel/gnuconfig-20051223 to /
1137220170: >>> emerge (4 of 129) sys-devel/binutils-2.16.1 to /
1137220419: >>> emerge (5 of 129) sys-devel/gcc-config-1.3.12-r6 to /
1137220435: >>> emerge (6 of 129) sys-libs/ncurses-5.4-r6 to /
1137220590: >>> emerge (7 of 129) sys-devel/m4-1.4.3 to /
1137220614: >>> emerge (8 of 129) sys-devel/bison-1.875d to /
1137220658: >>> emerge (9 of 129) virtual/libintl-0 to /
1137220664: >>> emerge (10 of 129) sys-apps/sed-4.1.4 to /
1137220701: >>> emerge (11 of 129) sys-apps/texinfo-4.8-r2 to /
1137220754: >>> emerge (12 of 129) sys-libs/zlib-1.2.3 to /
1137220776: >>> emerge (13 of 129) sys-devel/gcc-3.4.4-r1 to /
1137222151: >>> emerge (14 of 129) sys-devel/gcc-3.3.6 to /
1137223117: >>> emerge (15 of 129) sys-kernel/linux-headers-2.4.22-r1 to /
1137223167: >>> emerge (16 of 129) sys-libs/glibc-2.3.5-r2 to /
1137225161: >>> emerge (17 of 129) sys-devel/gettext-0.14.4 to /
1137225369: >>> emerge (18 of 129) sys-apps/man-1.6-r1 to /
1137225393: >>> emerge (19 of 129) sys-apps/man-pages-2.18 to /
1137225441: >>> emerge (20 of 129) sys-apps/grep-2.5.1-r8 to /
1137225473: >>> emerge (21 of 129) sys-devel/flex-2.5.4a-r6 to /
1137225492: >>> emerge (22 of 129) sys-libs/pam-0.78-r3 to /
1137225640: >>> emerge (23 of 129) app-misc/pax-utils-0.1.4 to /
1137225650: >>> emerge (24 of 129) app-shells/bash-3.0-r12 to /
1137225751: >>> emerge (25 of 129) sys-libs/readline-5.0-r2 to /
1137225791: >>> emerge (26 of 129) sys-libs/gdbm-1.8.3-r2 to /
1137225819: >>> emerge (27 of 129) dev-lang/python-2.4.2 to /
1137226003: >>> emerge (28 of 129) sys-apps/debianutils-2.14.1-r1 to /
1137226023: >>> emerge (29 of 129) sys-apps/portage-2.0.53 to /
1137226044: >>> emerge (1 of 100) dev-java/java-config-1.2.11-r1 to /
1137226060: >>> emerge (2 of 100) app-crypt/hashalot-0.3-r1 to /
1137226079: >>> emerge (3 of 100) sys-apps/shadow-4.0.7-r4 to /
1137226158: >>> emerge (4 of 100) sys-apps/pam-login-3.17 to /
1137226198: >>> emerge (5 of 100) sys-libs/com_err-1.38 to /
1137226250: >>> emerge (6 of 100) sys-libs/ss-1.38 to /
1137226282: >>> emerge (7 of 100) sys-fs/e2fsprogs-1.38 to /
1137226363: >>> emerge (8 of 100) sys-apps/util-linux-2.12r-r1 to /
1137226417: >>> emerge (9 of 100) x11-apps/ttmkfdir-3.0.9-r3 to /
1137226445: >>> emerge (10 of 100) media-libs/libpng-1.2.8 to /
1137226476: >>> emerge (11 of 100) x11-base/xorg-x11-6.8.2-r6 to /
1137228225: >>> emerge (12 of 100) sys-apps/file-4.13 to /
1137228262: >>> emerge (13 of 100) app-arch/cpio-2.6-r5 to /
1137228299: >>> emerge (14 of 100) app-arch/rpm2targz-9.0-r3 to /
1137228313: >>> emerge (15 of 100) sys-apps/utempter-0.5.5.6 to /
1137228328: >>> emerge (16 of 100) x11-terms/xterm-204 to /
1137228375: >>> emerge (17 of 100) media-sound/alsa-headers-1.0.10 to /
1137228388: >>> emerge (18 of 100) sys-devel/make-3.80-r2 to /
1137228421: >>> emerge (19 of 100) sys-kernel/gentoo-sources-2.4.31-r1 to /
1137228597: >>> emerge (20 of 100) media-libs/alsa-lib-1.0.10 to /
1137228723: >>> emerge (21 of 100) dev-java/sun-jre-bin-1.5.0.06 to /
1137229299: >>> emerge (1 of 2) app-arch/unzip-5.52 to /
1137229324: >>> emerge (2 of 2) dev-java/sun-jdk-1.4.2.10 to /
1137231245: >>> emerge (1 of 79) dev-java/sun-jre-bin-1.5.0.06 to /
1137231270: >>> emerge (2 of 79) dev-java/sun-jdk-1.4.2.10 to /
1137235032: >>> emerge (1 of 78) dev-java/sun-jdk-1.4.2.10 to /
1137235079: >>> emerge (2 of 78) sys-libs/db-4.2.52_p2-r1 to /
1137235301: >>> emerge (3 of 78) dev-lang/perl-5.8.6-r8 to /
1137235666: >>> emerge (4 of 78) perl-core/Test-Simple-0.62 to /
1137235680: >>> emerge (5 of 78) dev-perl/Locale-gettext-1.05 to /
1137235689: >>> emerge (6 of 78) sys-apps/help2man-1.33.1 to /
1137235704: >>> emerge (7 of 78) sys-devel/automake-1.9.6-r1 to /
1137235726: >>> emerge (8 of 78) sys-devel/libtool-1.5.22 to /
1137235793: >>> emerge (9 of 78) media-libs/jpeg-6b-r5 to /
1137235839: >>> emerge (10 of 78) media-libs/tiff-3.7.3 to /
1137235926: >>> emerge (11 of 78) sys-process/procps-3.2.5-r1 to /
1137235952: >>> emerge (12 of 78) dev-db/mysql-4.1.14 to /
1137237133: >>> emerge (13 of 78) perl-core/Storable-2.15 to /
1137237152: >>> emerge (14 of 78) dev-perl/Net-Daemon-0.38 to /
1137237168: >>> emerge (15 of 78) dev-perl/PlRPC-0.2018 to /
1137237184: >>> emerge (16 of 78) dev-perl/DBI-1.48 to /
1137237208: >>> emerge (17 of 78) dev-perl/DBD-mysql-2.9007 to /
1137237232: >>> emerge (18 of 78) app-misc/mime-types-4 to /
1137237239: >>> emerge (19 of 78) net-www/gentoo-webroot-default-0.2 to /
1137237248: >>> emerge (20 of 78) dev-libs/mm-1.3.0 to /
1137237274: >>> emerge (21 of 78) net-www/apache-1.3.34-r10 to /
1137237343: >>> emerge (22 of 78) net-www/mod_ssl-2.8.25-r10 to /
1137237369: >>> emerge (23 of 78) net-misc/openssh-4.2_p1 to /
1137237465: >>> emerge (24 of 78) app-editors/nano-1.3.7 to /
1137237495: >>> emerge (25 of 78) app-arch/gzip-1.3.5-r8 to /
1137237519: >>> emerge (26 of 78) net-misc/wget-1.10.2 to /
1137237563: >>> emerge (27 of 78) app-crypt/mhash-0.9.2 to /
1137237614: >>> emerge (28 of 78) dev-libs/libxml2-2.6.22 to /
1137237764: >>> emerge (29 of 78) dev-libs/libgcrypt-1.2.2-r1 to /
1137237854: >>> emerge (30 of 78) dev-libs/libxslt-1.1.15 to /
1137237918: >>> emerge (31 of 78) app-text/sablotron-1.0.1 to /
1137238004: >>> emerge (32 of 78) net-mail/mailbase-1 to /
1137238017: >>> emerge (33 of 78) mail-mta/ssmtp-2.61 to /
1137238033: >>> emerge (34 of 78) app-arch/bzip2-1.0.3-r5 to /
1137238055: >>> emerge (35 of 78) net-libs/libwww-5.4.0-r4 to /
1137238292: >>> emerge (36 of 78) sys-libs/db-1.85-r2 to /
1137238314: >>> emerge (37 of 78) net-misc/curl-7.15.1 to /
1137238400: >>> emerge (38 of 78) dev-php/php-4.4.0-r4 to /
1137238620: >>> emerge (39 of 78) dev-util/ctags-5.5.4-r2 to /
1137238646: >>> emerge (40 of 78) sys-fs/reiserfsprogs-3.6.19 to /
1137238685: >>> emerge (41 of 78) sys-apps/busybox-1.00-r4 to /
1137238887: >>> emerge (42 of 78) perl-core/Time-Local-1.11 to /
1137238902: >>> emerge (43 of 78) net-www/awstats-6.5 to /
1137238924: >>> emerge (44 of 78) media-libs/gd-2.0.33 to /
1137238973: >>> emerge (45 of 78) sys-apps/gawk-3.1.4-r4 to /
1137239027: >>> emerge (46 of 78) app-arch/tar-1.15.1 to /
1137239083: >>> emerge (47 of 78) sys-process/vixie-cron-4.1-r8 to /
1137239102: >>> emerge (48 of 78) sys-devel/autoconf-wrapper-3-r1 to /
1137239114: >>> emerge (49 of 78) net-misc/dhcpcd-2.0.0 to /
1137239140: >>> emerge (50 of 78) dev-php/mod_php-4.4.0-r9 to /
1137239437: >>> emerge (51 of 78) sys-apps/hdparm-5.9 to /
1137239451: >>> emerge (52 of 78) net-misc/ntp-4.2.0.20040617-r3 to /
1137239532: >>> emerge (53 of 78) sys-apps/kbd-1.12-r5 to /
1137239556: >>> emerge (54 of 78) www-client/lynx-2.8.5-r2 to /
1137239647: >>> emerge (55 of 78) app-editors/vim-core-6.4 to /
1137239705: >>> emerge (56 of 78) app-editors/vim-6.4 to /
1137239802: >>> emerge (57 of 78) app-vim/gentoo-syntax-20050618 to /
1137239817: >>> emerge (58 of 78) sys-apps/module-init-tools-3.2.1 to /
1137239854: >>> emerge (59 of 78) dev-perl/TermReadKey-2.30 to /
1137239871: >>> emerge (60 of 78) dev-util/dialog-1.0.20050206 to /
1137239900: >>> emerge (61 of 78) app-portage/ufed-0.36 to /
1137239913: >>> emerge (62 of 78) app-admin/logrotate-3.7.1-r1 to /
1137239930: >>> emerge (63 of 78) sys-apps/less-385_p4-r2 to /
1137239958: >>> emerge (64 of 78) sys-apps/diffutils-2.8.7-r1 to /
1137239997: >>> emerge (65 of 78) dev-libs/apr-0.9.7 to /
1137240083: >>> emerge (66 of 78) dev-libs/apr-util-0.9.7 to /
1137240120: >>> emerge (67 of 78) dev-util/subversion-1.2.3-r2 to /
1137240537: >>> emerge (68 of 78) sys-apps/net-tools-1.60-r11 to /
1137240565: >>> emerge (69 of 78) sys-apps/attr-2.4.19-r1 to /
1137240590: >>> emerge (70 of 78) sys-apps/coreutils-5.2.1-r6 to /
1137240769: >>> emerge (71 of 78) sys-apps/sysvinit-2.86 to /
1137240782: >>> emerge (72 of 78) sys-apps/baselayout-1.11.13-r1 to /
1137240802: >>> emerge (73 of 78) sys-boot/grub-0.96-r2 to /
1137240856: >>> emerge (74 of 78) net-misc/rsync-2.6.0-r6 to /
1137240901: >>> emerge (75 of 78) sys-process/psmisc-21.9 to /
1137240925: >>> emerge (76 of 78) sys-apps/findutils-4.1.20-r2 to /
1137240973: >>> emerge (77 of 78) app-portage/gentoolkit-0.2.0-r3 to /
1137240987: >>> emerge (78 of 78) app-admin/apg-2.3.0b-r1 to /
The configuration is not the same
Malfunctioning Server:
# ifconfig -a
eth1 Link encap:Ethernet HWaddr 00:30:48:20:EF:8E
inet addr:206.173.x.x Bcast:206.173.x.255 Mask:255.255. 255 .0
Perfectly Working Server:
eth1 Link encap:Ethernet HWaddr 00:30:48:20:F0:08
inet addr:206.173.x.x Bcast:206.173.x.255 Mask:255.255. 254 .0
I had another good look at the emerge log and noticed that the (1 of 129) ended at 29 others also do not seem to be complete.
Also grub seems to have disappeared; it could be related.
Unfortunately, all of the stops during the update are for valid reasons.
The first stop at 29 of 129, is because the "emerge -u world" updated portage itself. When that happens, it stops and restarts the emerge and the count is reset.
For the next emerge, it stops on 21 of 100 because you have to manually download the java file from Sun and place it in the /usr/portage/distfiles directory because of licensing issues. Since I wouldn't be able to download it for a little while, I went ahead did an emerge -u of the other java package so I could get the URL to go to and download them both at once. That was the 1 of 2 emerge. Then, the emerge that stopped at 2 of 79 was because one of the files I had downloaded was corrupt. I redownloaded it and the following 78 emerges went successfully.
If you do a count, 129 packages were emerged in total. Stops were only made for portage and java.
Grub is listed towards the bottom. The update emerged updated version 0.96-r2. It was update 73 of 78, towards the bottom of the list.
Also, Daniel mentioned in his initial post that our router is configured to accept broadcasts from both netmasks, although we had tried changing the netmask just to be certain.
Here is a recap of the problem:
I have two identically configured production web servers that are working just fine each with two network interfaces. Interface A connected to the 192.168.0 subnet on the private network. Interface B connected the public network, the default gateway, a central router all our networks are connected to, is on the public network. Either interface is reachable from any machine on our private and public network. Took one down and updated it with emerge. Brought it back up and now machines on the 192.168.0 subnet can only access the machine through interface A, and machines on the public network as well as the 192.168.2 subnet, the 192.168.0 and 192.168.2 subnets comprise the private network, on the private network can only access the machine through interface B. If you bring down interface A, the 192.168.0 private subnet, then the 192.168.0, 192.168.2, and the public networks can all reach the machine through interface B no problems.
P.S. Previously we had seen other odd behavior. Sometimes on a restart you couldn't communicate over either of the network interfaces at all, until you change the IP address, just the ip address, then it worked just fine. Reassign the old IP Address and it again becomes inaccessible. Give our other non-updated web server the same IP's and it can communicate just fine. Tried power cycling the switches, still no effect.
Here are the results of our latest tests:
1. Swapped in a new hard drive and did a fresh stage 3 install of gentoo. Configured both interfaces and the same behavior is showing. Nothing besides the base gentoo install is on the system.
2. Wiped the drive and installed Solaris 10 x86. Configured both interfaces and problem solved. Both interfaces are accessible from all networks at the same time.
Questions:
Below is a hardware spec list of this system. Has anyone else with the same chipsets seen this? Has anyone else seen this behavior with gentoo? Were you able to isolate the exact cause? Were you able to resolve the issue?
At the moment it looks to us like it is most likely a driver issue.
Hardware Specs
Motherboard:
SuperMicro X5DLR-8G2
Serverworks™ GC-LE Chipset
Adaptec AIC-7902 Controller
• Dual-Channel Ultra320 SCSI
Dual Broadcom 5704 Gigabit Ethernet
ATI Rage XL SVGA PCI video controller with 8 MB of video memory
Processor: Intel Pentium 4 Xeon
PLEASE LOOK AT PREVIOUS POST FOR DETAILS ON NETWORK CONFIGURATION:
Sorry It won't let me post a link, it is post number 2059109
I'd like to add that the previous networking issues we had began two years ago and have intermittently occured since for a total of(I believe) three times.
There isn't a particular reason to believe the problems are related but we mentioned it in case it is relevent.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.