Suse 11 server network configuration

Edward Feustel schrieb:
> On Tue, 15 Sep 2009 13:29:30 +0200, Merlin Morgenstern
> <merlin_x DeleteThis @fastmail.fm> wrote:
>
>> Hi there,
>>
>> I am running suse 11 as a server inside a virtualbox 3.x environment on
>> a laptop. There is no problem as long as I am in the office with WLAN,
>> but once I am disconected from the internet I can not access the server
>> anymore as the network is not configured correctly and I do not know how
>> to fix that.
>>
>> Following set up:
>>
>> 1 suse 11 with 2 network cards: Loopback; WLAN
>> 2 Vista as a host for Virtualbox
>> 3 Intranet with many machines inside the 192.168.0.x range
>>
>> I configured the card as follows:
>> 1. WLAN card: Static IP with alias 192.168.0.109
>> 2. Loopback with 192.168.0.109
>>
>> I know that I should assign 2 different IPs, but I need this server to
>> be accessible under this IP, no matter if I am on a train or connected
>> to the net.
>>
>> I can access the box if I disable one of those two cards and reboot.
>>
>> How can I configure the network to make suse respond to the same IP
>> through WLAN and through Loopback?
>>
>> Thank you for any help!
>>
>> Merlin
>
> Marin,
> Here are some things to check:
>
> You need to look carefully at the Netdevice configuration.
> It is unlikely that it is appropriate for your home use.
>
> I am surprised that you changed the loopback.
> Mostly I have seen the 127.0.0.1 & 2 used for this function
> and that may be required.
>
> Please also check your "gateway" address. By running ipconfig,
> make certain that the gateway address is correct. Your DCHP may
> not be setting it correctly.
>
> Ed

Hello Ed,

thank you for your help.

I know that 127.0.0.1 & 2 are the regular loop backs. I have set it to
192.168.0.109 as I need to reach the server under this adress. My
network knowledge is pretty limited so far. Am I wrong with this setting?

I need to keep the suse server under this IP, as I have used /etc/hosts
on windows to resolve the alias name and therefore windows can not find
the server if the IP is changing. This is also a problem when I log into
the net through another access point. They might have another subnet
and nothting works again.

Can you give me a hint how to solve this?


Regards, Merlin

Merlin Morgenstern wrote:
> I have set it to 192.168.0.109 as I need to reach the server under this adress.

You do know 192.168 is local net only, it NEVER is reachable outside of
it (it is called a private network address)?
--
Eef Hartman, Delft University of Technology, dept. SSC/ICT

Merlin Morgenstern wrote:

> Hi there,
>
> I am running suse 11 as a server inside a virtualbox 3.x environment on
> a laptop. There is no problem as long as I am in the office with WLAN,
> but once I am disconected from the internet I can not access the server
> anymore as the network is not configured correctly and I do not know how
> to fix that.
>
> Following set up:
>
> 1 suse 11 with 2 network cards: Loopback; WLAN
> 2 Vista as a host for Virtualbox
> 3 Intranet with many machines inside the 192.168.0.x range
>
> I configured the card as follows:
> 1. WLAN card: Static IP with alias 192.168.0.109
> 2. Loopback with 192.168.0.109
>
> I know that I should assign 2 different IPs, but I need this server to
> be accessible under this IP, no matter if I am on a train or connected
> to the net.
>
> I can access the box if I disable one of those two cards and reboot.
>
> How can I configure the network to make suse respond to the same IP
> through WLAN and through Loopback?
>
> Thank you for any help!
>
> Merlin

Is the network adapter for the virtual machine configured in bridged mode or
NAT or something else?

kev.

Merlin,
The previous post helped me to realize that your situation is rather
complicated!

Let's start from scratch.

1. You have two WLan cards. How is each configured?
In Suse, using the Yast>Network Devices, what devices do you see
and what are there parameters?
2. You are trying to reach a server. Where is the server physically
located? Is it in the virtual box? From the virtual box, what do you
see if you do ipconfig with a print out of all significant IP
information?
3. When you are on the office network, what is the gateway address?
The DCHP provided address?
4. When you are on external networks, what is the gateway address?
The DCHP provided address?

If you have bridging set up for your virtual box, do you really want
to have a fixed IP and fixed Loopback?

Regards,
Ed

Hello Ed,

I will put m anwers into your text:

Edward Feustel schrieb:
>
> Merlin,
> The previous post helped me to realize that your situation is rather
> complicated!
>
> Let's start from scratch.
>
> 1. You have two WLan cards. How is each configured?

Yes. I have assigned 2 network cards inside virtualbox for the suse 11
server:

eth0:Intel PRO/1000 T Server (Netzwerkbrücke, Microsoft Loopbackadapter)
eth1:Intel PRO/1000 T Server (Netzwerkbrücke, Intel(R) WiFi Link 5300 AGN)


> In Suse, using the Yast>Network Devices, what devices do you see
> and what are there parameters?

I do see eth0 and eth1, just like it should be.
I have configured eth1 as DHCP with an alias that has the fixed ip
192.168.0.109
eth0 is configured with a fixed ip 192.168.0.109

At the moment I fix the problem of the same ip with doing a
ifdown eth0; ifup eth1
and visa versa depending if I do have network or not.

> 2. You are trying to reach a server. Where is the server physically
> located? Is it in the virtual box?

Yes, it is inside a VB container

From the virtual box, what do you
> see if you do ipconfig with a print out of all significant IP
> information?

I will now post the ipconfig info while the server is conected to the
internet with eth1:

ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:A7:90:F2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth1 Link encap:Ethernet HWaddr 08:00:27:84:2F:4C
inet addr:192.168.1.47 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe84:2f4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3701 errors:0 dropped:0 overruns:0 frame:0
TX packets:3145 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:637793 (622.8 Kb) TX bytes:916840 (895.3 Kb)

eth1:snak Link encap:Ethernet HWaddr 08:00:27:84:2F:4C
inet addr:172.16.0.111 Bcast:172.16.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3650 (3.5 Kb) TX bytes:3650 (3.5 Kb)


> 3. When you are on the office network, what is the gateway address?
> The DCHP provided address?

Good question. I do not know. The problem also is, that I am changing
locations. Work at home, at a friends place etc. The all have other
Gateways which becomes a problem. With this setup I always have to
change my host file on windows to resolve the server name with another
ip. This would be great if I could have a fixed IP for the server, but
still be able to connect to the internet from the server!

> 4. When you are on external networks, what is the gateway address?
> The DCHP provided address?

I guess. How could I found this out?

>
> If you have bridging set up for your virtual box, do you really want
> to have a fixed IP and fixed Loopback?

The only 2 things I want is:
1. Have a fixed IP from the server so I do not have to change hosts file
all the time (and in the office I have multiple machines where I would
need to change it!)
2. Have an internet connection on the server if there is one available

>
> Regards,
> Ed


Thank you for any help!

Merlin