Not sure if this is possible for a reason I’ll come to as I explain what I’m trying to do
I have a Netgear Rangemax router in one room, but in another room I regularly connect various other computers
Have a spare old Dell machine and thought it would save me a lot of time wasted on installing and uninstalling usb wi-fi adaptors if I set this up as a router
Idea being, connect the Dell to the Rangemax via wi-fi, connect a hub I have lying around to the Dell, and then any machines I need to temporarily add to the network just plug into the hub and let them connect via dhcp
I’ve tried everything that seems obvious and/or logical, there’s only one thing I can see at the moment that may be stopping it working
In Yast’s firewall management screen for masquerading, it’s only picking up the pci ethernet card, the usb wi-fi it’s using for it’s own connection doesn’t appear
Because of that the option to enable masquerading is greyed out stopping me from enabling it
Is there some sort of limitation that means it has to be ethernet cards meaning that I can’t connect the Dell using wi-fi?
Is there a way to add the info for the wi-fi device to a conf file so that it gets recognised for masquerading allowing me to to turn it on?
If I have to run a cable to the Dell machine I wanna use as a router it would defeat the object, if that were the case I could just use the hub
I do have another Rangemax that could do the same job as the hub, less ports but it would add a second wireless point
Shame I couldn’t plug an adaptor into Rangemax2 and connect it to Rangemax1 via wi-fi … that would solve the issue in a flash
Check if the cards are configured in YaST -> Network devices -> Network settings.And then check the zones in Firewall -> Interfaces.they must be assigned to a zone before you can start masquarading
Yes the cards are configured in Yast2 Network Devices
Both are assigned to the external zone
I’m not sure whether the ethernet card should be assigned to external or not, but I’m assuming the wi-fi that handles the machine’s own net connection should be external
I also have dhcp server installed through Yast, another machine on the lan is running a dns server and that works fine
Not sure if I’ve set everything in the dhcp server config as I’ve never installed one before
The ethernet card should not be assigned to the external zone, since it belongs to the internal zone.
Second: you must configure the usb-wifi in Yast, using ifup. Otherwise the wireless connection (i.e. your shared internet connection) will only show up after user tells it to do so, i.e, configures it to automatically connect.
Suse machine running my dns server at ip 192.168.0.3
(There used to be a second Netgear router at 192.168.0.2)
Wi-fi adapter is Suse machine I’m trying to set up as a router is assigned to the external zone with static ip 192.168.0.20
Ethernet card assigned to internal zone and connected to the hub set to use dhcp
I’m using an xp laptop connected to the hub with a cable to test, set it to obtain the addresses via dhcp and it does get assigned the ip 192.168.0.22 with 192.168.0.20 as it’s gateway
The laptop isn’t able to ping any of the other addresses on the lan … much to my disgust as I thought there was some progress when I saw it had obtained the address through dhcp
Interestingly, if I set the ethernet card in the router machine to use a static ip of 192.168.0.21 the wi-fi card loses the internet connection, but the xp laptop is able to ping the lan addresses (obviously no internet connectivity as the wi-fi drops it)
I just had a look at the dhcp server settings in Yast and am getting this message with regards to the ethernet card:
The selected network interface has currently no configuration (no assigned ip address and netmask). Using it in the dhcp server configuration may not work
Seems that the dhcp server needs the ethernet card to have a static address, but if I set it static the machine itself loses the net connection
At the minute i have the wi-fi adaptor set to use static addressing through ifup and wpa authentication, a howto I looked at started off by setting both to dhcp initially
I think I’ve identified one problem, and that’s my own fault, I was trying to put both the external and internal adpaters using addresses in the 192.168.0.0/255.255.255.0 range
Too late in the day to start playing around with it right now though so I’ll have another look at that tomorrow
Bookmarked the swerdna link and I’ll give that a read tomorrow as well
1michael1 are you talking about connecting your suse computer to the internet using your D-Link router?
What is haben my Internet Server Provider is TV Cable they provide me with the modem without router,he told me to get a router.
I have 4-5years old router and the one I use is a 1 3/4 - 2 1/4 years old router use D-LInk model 625 it works really good.
I`m going uninstall SLES and reinstall suse11.1 see yeah later or the next day.
You are connecting your suse computer to the internet THROUGH your d-link router and cable modem
Imagine your suse computer was connected directly to the modem and the suse computer was set up in such a way that other computers could connect to the internet using your suse computer as the router instead of your d-link
In effect the suse computer would be doing the same job as your d-link router, thus allowing you to take the d-link out of the picture completely
Back to my problem …
It looks as if the ip addressing isn’t the only issue
Changed things so that the wi-fi adaptor supplying the suse router box’s internet connection is on 192.168.0.20 and the ethernet card to 192.168.2.1. still no luck
I have followed everything suggested in both the following howtos:
I wondered if perhaps the hub I’m using may be faulty but I’ve tested that using a cable to the netgear router and a laptop also connected via a cable, works perfectly
Is it possible that suse just doesn’t like using wi-fi in this kind of setup?
A look at the relevant sections from some working conf file examples might be handy
Incidentally I’m not using dhcp for the routing at the moment because yast dhcp setup fails to start the server even though I’ve followed everything ss per the two tutorials mentioned above
That shoudn’t matter any as it should work using static addresss but doesn’t
I’ve put so much time and effort into trying to make this work that I’m considering trying a different os to suse but I’m reluctant as that amounts to giving up
Imagine your suse computer was connected directly to the modem and the suse computer was set up in such a way that other computers could connect to the internet using your suse computer as the router instead of your d-link
My computer is connected directly in router and from there into modem so I can go to the internet
Cheers
But it works for me and I use my laptop to with the same router;)
I was trying to point out the difference in what you have to what I’m trying to do
The machine connects to the internet no problem at all, the problem is OTHER computers using it as a router to connect to the net
Still haven’t solved it, don’t seem to be any ideas coming from the threads I’ve started about it on two forums so I’m probably gonna try another linux distro over the weekend
Suse is without doubt my favourite distro but it just isn’t working for me the way I want it to in this particular case, time isn’t something I have much of and I’ve wasted too much of it trying to get this working already
I never try out with suse what you are talking but the easy way use a router.I should try one day with a computer to computer router to connect into net.
