Hello to All!
DHCP not enabled; manual config on Dell 10/100 ethernet card.
Does not connect on work lan or web.
I installed SUSE 10.3 on a second partition of a 320GB Dell M1330 laptop.
I boot up at work with the cat5 cable plugged in hot to the laptop.
The Dell 10/100 ethernet card shows along with the Intel 4965 wireless card.
I have configured the ethernet with the proper
IP: 192.168.xx.xx
Subnet: 255.255.252.0
Default Gateway: 192.168.xx.x
Preferred DNS server:192.168.xx.x
My proxy is a “squid/2.5.STABLE6” with no password or username just an address of 192.168.xx.x port: xxxx
DHCP is not enabled, all manual install.
I open administrator with yast and go to network config.
inputting the above information with choosing the ethernet card does not connect me to the network or web.
The proxy config does not test either.
Forgot to mention that I have disabled IPv6 as well for this doesn’t work with the work lan.
I am also on KDE 3.
Everything about the work lan is configured properly except maybe the ‘hostname’.
This remains a little confusing,
I assume it is the machine name, such as “ATECH-xxxxxxxxx”
When I get a chance today I will paste results of:
* lspci
* ifconfig
* route
from the console.
A /22 is uncommon for a home subnet perhaps, but not out of the question at a workplace where the admin may choose any size of subnet to suit the user base. After all class A, B and C are historical limitations now.
OP, what do you really mean by Internet does not work? If you were thinking that the settings in YaST for proxies will control the browser, they don’t, those settings are for repository fetching. You have to configure the browser for the proxy in the browser controls.
Hello Ken, I agree that a /22 isn’t “out of the question”. It is unusual enough, even in a large network, that I think it’s worth asking about just to be sure that’s what he intended. I’ve been a net admin for 12 years and I’ve yet to see supernets used on the end clients of a production network. (Although they’re common as grass in our routing tables… and that’s a good thing)
I don’t want to hijack this thread, but you raise a question that intrigues me… when and why supernet? Seems that once you have more than /24 devices you’d probably want to divvy up the broadcast domains anyway. Interested in your thoughts… and resolving Chetanji’s issues too of course.
Please forgive me for my confusing words.
I did configure Firefox as usual with the proxy settings but it would not find server because of setup “not correct.”
Like you said for the repositories the proxy needs to be setup in Yast.
This is what I am trying to figure out.
From my workstation I can ping the IP and the proxy and replies come back just fine.
I don’t have access to another PC on this “work” network, but have no doubt, it is just a simple
‘ping 192.168.xx.xx -t’
I setup a Fedora 7 workstation with a NetGear wireless card a year ago with the same settings. It took a one foot in the grave Unix Guru to show me how you configure the network on that machine.
I was never able to update the repositories because the proxy required a user name & password at the time, and I was never able to get it to work. The proxy was a bit of a nightmare then.
I tried to install Fedora Core 9 two weeks ago, but it would not recognize the graphics card and several other devices for this Dell M1330 laptop.
So I removed it and happily installed SUSE 10.3 because I heard so many good things about it, for quick config on new laptops.
Why not any size net that suits the user base? The historical class C subnet is not special in any way now, unless the software is badly retarded. It’s just a /24 subnet. A /22 subnet, which is 1022 usable address, isn’t really that large.
In practice I have seen /22, /23, /24 of course, and often /28 subnets.
OP I would use telnet to check that you can actually reach the squid proxy.
telnet squid-server-IP 3128
GET http://mozilla.com/ HTTP/1.0
Ken, do appreciate your comments. I opened a thread here for this particular discussion. Suffice to say I’m already pretty much persuaded that my old ways need some mending.
Hello Ken and all,
Yast shows correctly that this is a Broadcomm card, using different worded name than windows does. This does not appear to be a major difference.
I opened telnet and failed to connect to network.
when I try to ping the proxy server or IP I receive the error message “Network is unreachable.”
I do the proxy test in Yast and here is the error message
Error
An error occurred during the HTTP proxy test.
>About to connect to proxy 192.168.xx.x port 3128 (#0)
>Trying 192.168.xx.x Failed to connect to 192.168.xx.x
Network is unreachable.
>Success
>couldn’t connect to host
>closing connection #0
I also want to mention that on the Windows network this workstation “ABCDEF-1ab23fefe” on the “Workgroup” network.
So in the Hostname tab of Yast config for network card I put “ABCDEF-1ab23fefe” name in Hostname and “Workgroup” in the other box.
everything I type in Yast has been correct for the last year on multiple installations of the OS on this workstation, so this is not the first time.
It is only the first time with SUSE.
My only problem with Fedora Core 7 a year ago was configuring the NetGear Wireless card.
Once Fedora Core 7 recognized the wireless card (which took some doing) the actual config of my network was a snap.
It means you have a network interface configuration issue and your interface isn’t really active. Or on the wrong subnet. Or less likely all traffic is blocked to it the firewall.
Better go back to basics and check that you can ping other machines on your network, ping your gateway, etc. Proxying won’t work until you have a working network interface.
Okay what you say makes sense…
the subnet is correct as the network has been the same for over a year.
I wonder about my windows workstation name and the “Hostname.” Do I understand this correctly?
Also, firewall is “OFF” until all configuring is done ‘correctly!’
Maybe SUSE has recognized the wrong broadcom card and I am looking into this as well.
The only items possibly incorrect are SUSE’s view of the hardware card and the software “hostname.”
All other soft config information is correct.
So many times have I set up this same work network on this workstation and on many laptops.
When I say workstation I am referring to the PC at work and not my laptop which has the SUSE network connect problem.
I disabled the wireless and was able to connect to the work. When I clicked on the folder to open it, a message appeared that said, unable to open ( or some such thing; sorry I forget). It did not even offer the chance to enter username and password for access.
NO Web even with proxy in Mozilla correct.
I am at the point of doors locked before me and must move to major change.
My next move is to wipe openSUSE from hard drive; reinstall with minimal programs, only the basic, and maybe try Gnome this time.
If openSUSE gives me this much trouble with a simple broadcom ethernet card, this tells me to move on to Ubuntu, which promises simplicity in setup.
Unfortunatly, I need to get working in Linux for a important work project as well.
Sorry, but I believe this is a salient point.
Ethernet is decades old and this is not even a gigabit card, just a simple, basic network card by the major manufacturer broadcom.
