can i connect a Suse linux pc to a Windows 7 pc with wireless only and share the connection?

PC 1: windows 7 enterprise 64 bit, 2 network ports, 1 wireless (has access point connection)

PC 2: openSuse linux, older pc, 32b

I dont have any wired internet access. how can the linux pc pipe into the windows 7 pc to get to some kind of access??

has this been written up somewhere? they are connected directly with an ethernet cable, but i have a basic bridge if it needs to have that

iBradleyAllen PC 1: windows 7 enterprise 64 bit, 2 network ports, 1 wireless (has access point connection)

PC 2: openSuse linux, older pc, 32b

I dont have any wired internet access. how can the linux pc pipe into the windows 7 pc to get to some kind of access??

has this been written up somewhere? they are connected directly with an ethernet cable, but i have a basic bridge if it needs to have that

So, normally to connect two PC’s together using wireless would be an ad-hoc connection, kind of like connecting two wired PC’s with a crossover cable (which was needed in the old days). The real work would be required on the Windows 7 PC as you have to convince it to do an ad-hoc connection to another PC, and do a Internet connection sharing out of the ad-hoc Wireless connection. So I missed where you live, but here in Texas I can go to Walmart and buy a wireless router for $50 or even less (if not g rated), set it up as a wireless access point and connected it to the Windows 7 PC as a hub and you would be done already. I am thinking it is not worth the trouble myself, if it can be done at all.

Thank You,

On Thu February 17 2011 05:36 pm, iBradleyAllen wrote:

>
> PC 1: windows 7 enterprise 64 bit, 2 network ports, 1 wireless (has
> access point connection)
>
> PC 2: openSuse linux, older pc, 32b
>
> I dont have any wired internet access. how can the linux pc pipe into
> the windows 7 pc to get to some kind of access??
>
> has this been written up somewhere? they are connected directly with
> an ethernet cable, but i have a basic bridge if it needs to have that
>
>
iBradleyAllen;

As I understand you want to be able to connect to the internet from PC 2 via
PC 1. This HowTo should help you set it up;

http://opensuse.swerdna.org/suseics.html

See also:
http://opensuse.swerdna.org/susenic.html

for setting up your interface on PC 2.


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

hi James

i meant to say the pc that needs the internet is an old P3 with no radio at all, it can only use its ethernet to connect into the main pc’s unused ethernet, which is connected by a built in radio going to a wireless router. Yes, a 2nd wireless access point would work to make the old pc have internet (but I dont have millions of dollars sitting around to buy a $50 wireless box). Yes walmart is a great place to buy stuff, we finally got them out here in So Cal.

But I made it work! the linux pc box simply had to be connected with a static IP to the main pc, and in the main pc’s wireless connection properties just say ICS, internet connection sharing, which apparently gave it a new IP, and the linux pc had to be on the same network IP address range, and it took off

Hey thanks!! this helped to figure it out, it works!

the trick happens on the Win7 side (with the wireless connection) as i had to set the network settings to share the internet connection; then set the linux box with a static IP on the same range. Good thing i did this, because last week when trying to link 2 windows boxes, i had set the win7 to share everything, hoping that would facilitate connecting, then got the chance to connect up wirelessly.

what I didnt like was that in the Suse linux, to open the network settings it takes about 1 minute as it runs a page full of scripts… then eventually opens a basic network control interface. I dont want to see this, just open the thing so i can get to the settings. Is the network control interface something that can be tweaked and recompiled? or is that another thread question?

thanks again

On 02/18/2011 11:06 AM, iBradleyAllen wrote:
> what I didnt like was that in the Suse linux, to open the network
> settings it takes about 1 minute as it runs a page full of scripts…
> then eventually opens a basic network control interface. I dont want to
> see this, just open the thing so i can get to the settings. Is the
> network control interface something that can be tweaked and recompiled?
> or is that another thread question?

How are you controlling that interface? As long as you have a static IP and are
only using a wired connection, you should be using ifup. Once you use YaST to do
that in Network Settings => Network Devices under the “Global” tab, and you set
the configuration on those same pages, all the network connection will take
place during bootup and you won’t see it. No additional “network configuration
interface” will be required.

On Fri February 18 2011 11:06 am, iBradleyAllen wrote:

>
> Hey thanks!! this helped to figure it out, it works!
>
<snip>
>
> thanks again
>
>
iBradleyAllen;

Glad to have helped. Thank Swerdna for his fine tutorials. Enjoy your
connection.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

clicking on the Computer button, then picking the built in network setup icon, I dont know what it is

oh I think I see what you mean now, but I dont want a terminal session to control the network I want something formatted with graphics. ifup is the command, right? not an application? the way things get named in LInux its hard to tell

i got it setup so that it boots and is connected just fine; but in Windows it launches a box with info on it pretty much right away, why does this Suse one take so long to load? it looks like 40 checklist items it does, then gives the dialog box, I dont want to see all that. I want to click on an icon then it launches something that says network control (whatever) and shows the status and has buttons to click to edit the settings.

The screens where you go to set the IP to static/dhcp and enter an IP, thats what Im referring to. it works okay its just a “wish it worked like that” kind of thing

On Sat February 19 2011 06:36 pm, iBradleyAllen wrote:

>
> oh I think I see what you mean now, but I dont want a terminal session
> to control the network I want something formatted with graphics. ifup
> is the command, right? not an application? the way things get named in
> LInux its hard to tell
>
> i got it setup so that it boots and is connected just fine; but in
> Windows it launches a box with info on it pretty much right away, why
> does this Suse one take so long to load? it looks like 40 checklist
> items it does, then gives the dialog box, I dont want to see all that.
> I want to click on an icon then it launches something that says network
> control (whatever) and shows the status and has buttons to click to edit
> the settings.
>
> The screens where you go to set the IP to static/dhcp and enter an IP,
> thats what Im referring to. it works okay its just a “wish it worked
> like that” kind of thing
>
>
iBradleyAllen;

If you configured the card according to Swerdna’s HowTo:

http://opensuse.swerdna.org/susenic.html

it may already be using ifup, he covers that first.

There are two ways to configure a card. Network Manager and Traditional ifup.
Network Manager is designed to give flexibility of connections and useful
for Laptops that need to change networks frequently. ifup is less flexible
and best for situations where the machine will stay on the same network. As
long as everything is working well, don’t lose any sleep.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

That’s why You want to turn off NetworkManager and control your network using ifup. It’s graphical as well when you’re using YAST and You have to set it up once and the settings will be saved and that’s it. There will be no more dialogues and it will start much faster than in Windows :slight_smile: By the way YAST ifup is very much similar to those screens where You go to set static/dhcp and enter an IP in Windows. It looks something like this (sorry for polish) :
SUSE Paste
Read the swerdna’s guide carefully and set up your static IP using YAST ifup.

Best regards,
Greg