Very Computer

by **Colombier Pierr** » Sun, 13 Jun 1999 04:00:00

upgrading 5.2 to 6.0 or installing 6.0 put down my network, my computer
became blind.
My 3com 503c work very well with 5.2 but when I upgrade to 6.0 there's
nothing to ping, all is unreacheable ???
a solution ?

thanks for helping me

Pierre ;-)

by **Monte Philli** » Sun, 13 Jun 1999 04:00:00

at boot up and before you login press
SHFT pgUp and scroll back to top, see if you can find a reference
there to 3c509 or some such (should give IRQ and mem address info).
If so then the kernel sees it and the prob lies in your
configuration(s).

do your netconf and make sure eth0 is set up

in the hosts section there should be at least one line
127.0.0.1 localhost localhost.localdomain

in the interface section these two lines
lo 127.0.0.1 none yes active
eth0 <your IP address> none yes active ---your IP is
something like 192.168.0.1 or whatever you decide.

these are the line as they appear in xwindows network configurator

in the command line netconf program you basic host information should
be something along these lines.

Hostname <the name of your computer such as LinuxBox>
x Enabled
config mode (o) Manual
Primary name plus domain <LinuxBox or whatever>
IP address 192.1668.0.1 or whatever
netmask 255.255.255.0
Net device eth0
kernel module 3c509 <your NIC model>

This site has a step by step howto for complete setup of samba. steps
for both linux and the win machine. (and they really work <G>)
http://www.sfu.ca/~yzhang/linux/samba/index.html

g'Luk

if that is properly set you should be able to ping yourself 127.0.0.1

On Sat, 12 Jun 1999 21:24:06 +0200, Colombier Pierre

>upgrading 5.2 to 6.0 or installing 6.0 put down my network, my computer
>became blind.
>My 3com 503c work very well with 5.2 but when I upgrade to 6.0 there's
>nothing to ping, all is unreacheable ???
>a solution ?

>thanks for helping me

>Pierre ;-)

by **Colombier Pierr** » Mon, 14 Jun 1999 04:00:00

ok i will try, but why red hat 6.0 is more hard to configure than 5.2,
the nic card was detect very well and after giving ip address the
network was OK, with 5.2. Now I must try to resolve the problem putting
my eyes in the engine motor, as I'm a newbie, it's hard, don't you think
so?

Thank you any way for the response.

Pierre |:-)

> at boot up and before you login press
> SHFT pgUp and scroll back to top, see if you can find a reference
> there to 3c509 or some such (should give IRQ and mem address info).
> If so then the kernel sees it and the prob lies in your
> configuration(s).

> do your netconf and make sure eth0 is set up

> in the hosts section there should be at least one line
> 127.0.0.1 localhost localhost.localdomain

> in the interface section these two lines
> lo 127.0.0.1 none yes active
> eth0 <your IP address> none yes active ---your IP is
> something like 192.168.0.1 or whatever you decide.

> these are the line as they appear in xwindows network configurator

> in the command line netconf program you basic host information should
> be something along these lines.

> Hostname <the name of your computer such as LinuxBox>
> x Enabled
> config mode (o) Manual
> Primary name plus domain <LinuxBox or whatever>
> IP address 192.1668.0.1 or whatever
> netmask 255.255.255.0
> Net device eth0
> kernel module 3c509 <your NIC model>

> This site has a step by step howto for complete setup of samba. steps
> for both linux and the win machine. (and they really work <G>)
> http://www.sfu.ca/~yzhang/linux/samba/index.html

> g'Luk

> if that is properly set you should be able to ping yourself 127.0.0.1

> On Sat, 12 Jun 1999 21:24:06 +0200, Colombier Pierre

> >upgrading 5.2 to 6.0 or installing 6.0 put down my network, my computer
> >became blind.
> >My 3com 503c work very well with 5.2 but when I upgrade to 6.0 there's
> >nothing to ping, all is unreacheable ???
> >a solution ?

> >thanks for helping me

> >Pierre ;-)

by **Colombier Pierr** » Mon, 14 Jun 1999 04:00:00

OK...

I've tried all you've wrote, and all of my config is good, the adapateur
is active and I can ping myself, but I can't ping other machine, I 'm
blind. I've compared the config with my last config in red hat 5.2 and
it seam to be the same, it's a bug, with 3com ???

thanks

Pierre |;-)

> at boot up and before you login press
> SHFT pgUp and scroll back to top, see if you can find a reference
> there to 3c509 or some such (should give IRQ and mem address info).
> If so then the kernel sees it and the prob lies in your
> configuration(s).

> do your netconf and make sure eth0 is set up

> in the hosts section there should be at least one line
> 127.0.0.1 localhost localhost.localdomain

> in the interface section these two lines
> lo 127.0.0.1 none yes active
> eth0 <your IP address> none yes active ---your IP is
> something like 192.168.0.1 or whatever you decide.

> these are the line as they appear in xwindows network configurator

> in the command line netconf program you basic host information should
> be something along these lines.

> Hostname <the name of your computer such as LinuxBox>
> x Enabled
> config mode (o) Manual
> Primary name plus domain <LinuxBox or whatever>
> IP address 192.1668.0.1 or whatever
> netmask 255.255.255.0
> Net device eth0
> kernel module 3c509 <your NIC model>

> This site has a step by step howto for complete setup of samba. steps
> for both linux and the win machine. (and they really work <G>)
> http://www.sfu.ca/~yzhang/linux/samba/index.html

> g'Luk

> if that is properly set you should be able to ping yourself 127.0.0.1

> On Sat, 12 Jun 1999 21:24:06 +0200, Colombier Pierre

> >upgrading 5.2 to 6.0 or installing 6.0 put down my network, my computer
> >became blind.
> >My 3com 503c work very well with 5.2 but when I upgrade to 6.0 there's
> >nothing to ping, all is unreacheable ???
> >a solution ?

> >thanks for helping me

> >Pierre ;-)

by **Harrington B. Laufma** » Mon, 14 Jun 1999 04:00:00

> upgrading 5.2 to 6.0 or installing 6.0 put down my network, my computer
> became blind.
> My 3com 503c work very well with 5.2 but when I upgrade to 6.0 there's
> nothing to ping, all is unreacheable ???
> a solution ?

> thanks for helping me

> Pierre ;-)

Hello,

Not much information to go on, but I did the same upgrade and lost my ip
forwarding,
thereby breaking my little network. I was using some ipfwadm commands in

rc.local to help secure the network.

The ipfwadm command is gone. So /etc/rc.d/rc.local scripts fail-->no ip
forwarding. ipfwadm has been replaced by ipchains. A Howto tells us:

" Linux ipchains is a rewrite of the Linux IPv4 firewalling code (which
was
mainly stolen from BSD) and a rewrite of ipfwadm, which was a rewrite of
BSD's
ipfw, I believe. It is required to administer the IP packet filters in
Linux
kernel versions 2.1.102 and above.

"The older Linux firewalling code doesn't deal with fragments, has 32-bit
counters (on Intel at least), doesn't allow specification of protocols
other
than TCP, UDP or ICMP, can't make large changes atomically, can't specify
inverse rules, has some quirks, and can be tough to manage (making it
prone to
user error). "

But the life saver is ipfwadm-wrapper, which takes ipfwadm command
arguments and pipes them to ipchains in a correct format. Change all
script
references from /sbin/ipfwadm to /sbin/ipfwadm-wrapper and you are fixed.
Wrestle with the new ipchains command syntax later, get up and running
now.
ipfwadm-wrapper comes with Red Hat 6.0.

Regards,
Harrington

by **Monte Philli** » Mon, 14 Jun 1999 04:00:00

Ok this is a real long shot, but on my machines ( I have a linux
server samba'd to a Win98) I have a 3c509 in the linux box and a
linksys NIC in the Winbox. In order for the network to see each other
I have to bring up the 3com card first or restart the Winbox. Its a
quirk with the 3com card, ( a NIC with a superiority complex or
something <G>)

g'Luk and let me know if you figure it out.... 'cause right now i'm
as stumped as you. :)

On Sun, 13 Jun 1999 08:14:03 +0200, Colombier Pierre

>OK...

>I've tried all you've wrote, and all of my config is good, the adapateur
>is active and I can ping myself, but I can't ping other machine, I 'm
>blind. I've compared the config with my last config in red hat 5.2 and
>it seam to be the same, it's a bug, with 3com ???

>thanks

>Pierre |;-)

by **Mark** » Thu, 01 Jul 1999 04:00:00

FWIW, the version of "pump" that came with RH6.0 had a bug that caused
all kinds of strange network problems. RH6.0 uses "pump" instead of
DHCP or BOOTP. A newer version is available at RedHat's errata page.

> > upgrading 5.2 to 6.0 or installing 6.0 put down my network, my computer
> > became blind.
> > My 3com 503c work very well with 5.2 but when I upgrade to 6.0 there's
> > nothing to ping, all is unreacheable ???
> > a solution ?

> > thanks for helping me

> > Pierre ;-)

> Hello,

> Not much information to go on, but I did the same upgrade and lost my ip
> forwarding,
> thereby breaking my little network. I was using some ipfwadm commands in

> rc.local to help secure the network.

> The ipfwadm command is gone. So /etc/rc.d/rc.local scripts fail-->no ip
> forwarding. ipfwadm has been replaced by ipchains. A Howto tells us:

> " Linux ipchains is a rewrite of the Linux IPv4 firewalling code (which
> was
> mainly stolen from BSD) and a rewrite of ipfwadm, which was a rewrite of
> BSD's
> ipfw, I believe. It is required to administer the IP packet filters in
> Linux
> kernel versions 2.1.102 and above.

> "The older Linux firewalling code doesn't deal with fragments, has 32-bit
> counters (on Intel at least), doesn't allow specification of protocols
> other
> than TCP, UDP or ICMP, can't make large changes atomically, can't specify
> inverse rules, has some quirks, and can be tough to manage (making it
> prone to
> user error). "

> But the life saver is ipfwadm-wrapper, which takes ipfwadm command
> arguments and pipes them to ipchains in a correct format. Change all
> script
> references from /sbin/ipfwadm to /sbin/ipfwadm-wrapper and you are fixed.
> Wrestle with the new ipchains command syntax later, get up and running
> now.
> ipfwadm-wrapper comes with Red Hat 6.0.

> Regards,
> Harrington

--
Mark S. Anthony

Very Computer

problem with rh6

problem with rh6

problem with rh6

problem with rh6

problem with rh6

problem with rh6

problem with rh6

problem with rh6