The below route stops my internet connection in its tracks.
ip route show
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.59
192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.2
127.0.0.0/8 dev lo scope link
default via 192.168.1.254 dev eth2 proto static
If I issue the command
ifconfig eth0 down
Followed by
ip route show
192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.2
127.0.0.0/8 dev lo scope link
default via 192.168.1.254 dev eth2 proto static
My question is how to make this permanent ? How do I make this route take precedence over eth0 while keeping eth0 for networking to my lan ?
cabernet wrote:
> AMD64 Suse 11.0
>
> The below route stops my internet connection in its tracks.
> # ip route show
> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.59
> 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.2
These can not exist simultaneously, Either packets for 192.168.1.0/24 go
to eth0 OR they go to eth2, not both.
So something is not as it should be in your situation.
> My question is how to make this permanent ? How do I make this route
> take precedence over eth0 while keeping eth0 for networking to my lan ?
First you must remedy this routing problem, because this will never work.
As stated above you can not have to network connections to the same network at the same time. So only eth0 or eth2 may UP and connected to 192.168.1.0/24.
You could go to YaST > Network Devices > Network card, select one, and Delete it.
Or Edit and go to the General Tab. You will see a chooser Activate Device, make Never (keeping the configuration ready for usage at the shortest nnotice).
Or set Activate device at On Cable Conection and see that only one cable is connnected at any time.
May be there are more
Actually you can have more than one Ethernet interface connected to the same LAN segment in the same subnet. See a recent thread started by swerdna asking this question, among others.
What I suspect the OP did is use the same subnet for two different LANs, his connection the router (albeit a LAN of two machines) and his internal LAN. That wouldn’t work.
It is always what **they **do not tell you and what **we **try to interprete that brings us to different solutions for what may not be the problem! (Legenda: **they **are those who have problems and **we **are those that try to help).
Then your asking for his network layout still holds very much true. So **cabernet, **show us the picture!
Sorry guys, you have been very patient. Since my last post I became quite obsessed with routing and spent a lot of time on it. Probably too much time. My set up --Internet>Router>Suse Box>Bsdbox. A lot of motherboards come with two network connections these days. Attempting to use the two was really hard on Suse. I did not find yast networking very intuitive. Everytime I restarted the network the routing would change, cutting off the internet. Anyway I found this page very helpful. Linux.com :: What can you do with a second Ethernet port?
I went into Yast networking and turned on traditional configuration with ifup and then used the command line as suggested on this web page. Masquerading, port forwarding, pinging and routing are working. I am able to get to the net on the Bsd and Suse box.
