This is hard to word. Basically I have a wifi connection, and an ethernet connection.
The wifi connection is to provide my internet.
The lan connection is using a crossover cable to connect to my ‘file server’ which also has 2 connections. It’s connections are both lan, one for web, one for sharing files directly via the crossover cable to me.
The problem is instead of the machine I want to use wifi for internet, it uses the internet from the other machine, so for some reason it is being shared by that machine, and this machine prefers the lan over wifi.
How can I either stop the internet sharing on the server, or force this other machine, to only use the net from wifi?
I know it would be easier to use a router, but there is a performance decrease, among other things.
This machine is SUSE 12.1 Gnome 3 64 bit, the other is Mint 9 32 bit. Both have pretty similar connection managers.
This should be done using a correct routing table. The default route should point to the router you goto with the Wifi and not to the other system. Take a look at the output of
/sbin/route -n
When it does not iluminate you, post it here for further advice and specify with it what the different IP addresses represent.
Sorry about the double post, I guess I was having connection issues because I waited, finally refreshed, and posted again as I never saw it go through anywhere.
I guess the part about routing tables indicates this won’t be automatic as I had hoped? It was previously using the wlan connection for net but something obviously changed. Here is the output of that command:
> /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.42.43.1 0.0.0.0 UG 0 0 0 eth0
10.42.43.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
192.168.15.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
the first two are my lan connections to the server, and the wlan0 is the one that should be using the net.
On 01/20/2012 09:16 AM, l300lvl wrote:
>
> hcvv;2432248 Wrote:
>> This should be done using a correct routing table. The default route
>> should point to the router you goto with the Wifi and not to the other
>> system. Take a look at the output of
>>>
> Code:
> --------------------
> > > /sbin/route -n
> --------------------
>>>
>> When it does not iluminate you, post it here for further advice and
>> specify with it what the different IP addresses represent.
>
> Sorry about the double post, I guess I was having connection issues
> because I waited, finally refreshed, and posted again as I never saw it
> go through anywhere.
>
>
> I guess the part about routing tables indicates this won’t be automatic
> as I had hoped? It was previously using the wlan connection for net but
> something obviously changed. Here is the output of that command:
>
>
> Code:
> --------------------
>
> > /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 10.42.43.1 0.0.0.0 UG 0 0 0 eth0
> 10.42.43.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
> 192.168.15.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
> --------------------
>
>
> the first two are my lan connections to the server, and the wlan0 is
> the one that should be using the net.
The networking code will nearly always give preference to wired over wireless.
The problem can be solved. Every simple router does it - most of them even run
Linux. In fact, I recommend that you purchase such a router, which will take
care of this immediately. You claimed a “performance” problem, but did not
specify an basis for this. My experience is that any consumer-grade router can
handle packets faster than my 100 Mbps network. I have never had a Gigabit
network for testing.
Simply put, in real life tests, the performance was based on speeds of actual transfers when connected directly versus connected to a router. I would prefer only using a router as a last resort, and right now it is faster for me to disconnect the Ethernet cable or disable that connection when I’m not transferring.
On 01/20/2012 01:26 PM, l300lvl wrote:
>
> Simply put, in real life tests, the performance was based on speeds of
> actual transfers when connected directly versus connected to a router. I
> would prefer only using a router as a last resort, and right now it is
> faster for me to disconnect the Ethernet cable or disable that
> connection when I’m not transferring.
>
> Are you saying what I asked is not possible?
Then, you needed a better router. As I said, my routers work at full network
speeds, even with 3 of them daisy chained together. Don’t ask.
No, what you want to do is fully possible. You will need to use ifup, not
NetworkManager. For wireless, ifup is much harder. Once the network is up, you
will need to manually add the routing using
Were you comparing the transfer speed across a wire with that through a router
with one leg in the air? If so, you were not being slowed by the router, but the
slowness of that air link, which probably had a upper limit of 27 Mbps compared
with the wire at 100 Mpps.
> I can see a few uses for daisy chaining myself…I can be paranoid…
It is not paranoia, although nothing from the outside can get past #1 except for
subversion packets that go to a file server. I have 3 AP/router boxes always
running so that I can test WPA2, WPA, and WEP without reconfiguring any APs. The
wire for my laptop is connected to #3. To get from here to the Internet, the
path is wire - router3 - wire - router2 - wire - router1 - wire - cable modem -
cable…
It is clear the default route (the first line with the 0.0.0.0 address) points to your router 10.42.43.1 on your wired LAN (via eth0).
Now, my idea was that from understanding your situation (a fixed wired connection and a wired connection also in afixed sutuation) you would use a “traditional with ifup” configuration. When that is the case, you use YaST > Network devices > Network Configuration and the Routing tab. There you will find the default gateway configured as 10.42.42.1. Change it to 192.168.15.n (where n is theof course the number used by your router on the Wifi LAN).
When you do use Network manager, then my first reaction would be:" why didn’t you say so?" In any case then things are different because Network Manager allways prefers cabled before wifi and thus uses that router on th cabled LAN. Can be changed, but needs a NM guru, whith I am not.
@everyone, thanks for the help. I started thinking about what you all said about routes and such and remembered how in NetworkManager you can set Shared/Local link/Auto etc in ipv4 settings tab. On the server I had it set to shared, and after reading about ICS a bit I realized that is the mode that is used to share the net, and since I didn’t want it to there had to be another ‘option’ so… I changed it to Local link only, on the server AND on this device, and it worked. It shares smb shares etc but not net, and now NetworkManager uses the wifi connection for net, and even shows the WiFi as being top priority over eth0 in the panel, e.g the icon shows for wifi instead of lan even though both are connected. So this is solved, and was a lot simpler than I was making it.
About the using the router idea, I realized this just wasn’t going to work as it would defeat the whole purpose, which is. I want to be able to connect to the smb shared over lan, not wifi, but I still want to be able to use WiFi for net, with using the router I’d have to use lan for net, and basically I want the net to stay connected when I disconnect from lan. Sorry I didn’t explain that better, but now we all know how