I have a strange (local) network problem in fc 10 which I never had in
fc9 on the same hardware (with same config files).
This machine serves as a proxy+firewall between about 10 other machines
on the local network (192. addresses - the # of machines varies
depending on where laptops are) and the real world. There have
been no problems up through fc9 (fc2-9 worked fine). No hardware has
changed, and this is a clean install (I can swap boot drives in the
bios so am able to go back to fc9 to check if and compare). While on
fc9 the following work correctly, on fc10 the results are a little
different:
Under fc9:
+ The firewall+proxy machine can see all of the network printers
and ALL of the machines on the 192 network.
+ All Linux, windows, and Solaris machines on the 192 network
can see the firewall+proxy machine.
Under fc10:
+ The firewall+proxy machine can see all of the network printers
but CANNOT see the windows machines on the 192 network.
+ ONLY the non-windows machines on the 192 network can see the
firewall+proxy machine. (The windows machines can still see
each other AND can see everything except the firewall+proxy
box.
The files
/etc/hosts
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/rc.d/rc.local
are identical between the fc9 root and the fc10 install.
None of the other machines (Linux or windows) has had any updates since
BEFORE the install of fc10.
The firewall+proxy machine can see all of the Linux machines on the
network, but none of the windows machines.
A packet sniffer can see the attempts to ping from both sides, but
there is never an answer in either direction.
Finally, I can boot to the fc9 root drive and the problem disappears,
while if I boot to the fc10 drive, it occurs repeatably.
Machine: Athlon 64 X2 6000+ CPU with 6 GB ram, mixed scsi and eide
drives.
Kernel: (fc10: same result with both kernel-2.6.27.7-134.fc10.x86_64
and kernel-2.6.27.5-117.fc10.x86_64). {note: on fc9 it was the
2.6.27.7-53.fc9.x86_64 kernel}.
Glibc: glibc-2.9-3 (x86_64, i686, and i386 installed).
Any pointers as to what I might try to find a solution here would be
greatly appreciated, as I've spent many hours reading and going over
everything I could think of - with no luck.
I suspected a problem with SE linux, so as a test, I took the firewall
+proxy machine off the internet (no connection), disabled selinux, and
rebooted. The results were (as expected) unchanged. (And it's back in
place now, although I thought the disk relabeling would take
forever...).
I really don't think this is a bug - scanning through bugzilla didn't
find any pointers. I suspect cockpit error (mine), but I can't
identify it so far. Please help.
Thanks
--
william w. austin waustin@xxxxxxxxxxxxx
"life is just another phase i'm going through. this time, anyway ..."
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
