HDCP Server

hey guys,

i’m new to suse, but I was programming much in windows and I slowly get used to linux, but I loved it from the moment I first opened the terminal.

About my problem:
I’m using SUSE 11.2 as a server in my home network. I about 10 windows-pc’s in my network, which is structured as following:

Very simple router (no dhcp) → Switch → Win1, Win2, …, Suse

I already managed to set up the DHCP server, and it works like a charm, but somehow I’m not able to get in the internet with the Windows PC’s. This is especially strange if you consider the settings:

Suse 11.2 Server:
*****000d88cd4cb4:/home/king # ifconfig br0
br0 Link encap:Ethernet HWaddr 00:0D:88:CD:4C:B4
inet addr:80.109.145.85 Bcast:80.109.145.255 Mask:255.255.255.0
inet6 addr: 2002:506d:9103:a:20d:88ff:fecd:4cb4/64 Scope:Global
inet6 addr: fec0::a:20d:88ff:fecd:4cb4/64 Scope:Site
inet6 addr: 2002:506d:91fb:a:20d:88ff:fecd:4cb4/64 Scope:Global
inet6 addr: fe80::20d:88ff:fecd:4cb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:133250 errors:0 dropped:0 overruns:0 frame:0
TX packets:32193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:64027754 (61.0 Mb) TX bytes:3396690 (3.2 Mb)


Win7 Home PC:
Ethernet-Adapter LAN-Connection:
IPv4: 80.109.145.2
subnet: 255.255.255.0
Gateway: 80.109.145.255

I tried pinging the gateway from both suse11.2 and win but it failed.

Pinging win7 to suse and other way around is possible.

internet works on suse11.2, but it doesn’t works on win.

Win7 Home PC:
Ethernet-Adapter LAN-Connection:
IPv4: 80.109.145.2
subnet: 255.255.255.0
Gateway: 80.109.145.255

Normally a gateway address ends in 1 i.e 80.109.145.1. The one you have there looks like a broadcast address.

You need to post more information on how you are connected to the internet.

It looks like you are setting up the public IP addresses and your scheme is using 255 public IPs. Is that the case?

If Internet is working on the SUSE machine, what is the output of:

route
ifconfig

Also, what is the configuration information for the DHCP. I think you need adjustments on the configuration, especially, the IP range, mask and default gateway there.

There are several weird things about your setup.

Why do you have br0 instead of the normal eth0 for the Linux interface? Did you enable Xen or something?

Why do you have a 256 IP address public subnet? Most home users only get one public IP address.

How are you logging onto the Internet? Is the modem a DSL modem and you are using PPPoE to login? In which case only one machine can have the Internet connection the way you have set it up.

As you can see, you have not provided all the necessary information. I suspect you will not be able to get it to work with the invalid assumptions you are making and any attempts to provide you with help with your current setup are doomed. You have to provide all the relevant information and be prepared to rearchitect your network.

inet addr:80.109.145.85 Bcast:80.109.145.255 Mask:255.255.255.0

this net mask is not suitable for this ip
this ip should get the mask 255.0.0.0
Gateway: 80.109.145.255 this not a broadcast address in this case because you’re using the B class of ip.

and dont forget this is a public IP,it wont work like this
try private ip like 192.168.1.X/24 or 172.16.X.X/16

good luck

thanks for the replies!

-Forget about what i said over the router, I mixed router and modem. My setup is as following:
MODEM > 16PORT_SWITCH > Me (Suse11.2), 10xClientWin

-I’m connected to the internet via a simple noname-modem > DSL

-I don’t know why br0 is my main device instead of eth0, when I ‘ifconfig’ then eth0 is not configured and empty (what’s the difference?)

-It could definetefely be, that I entered a Broadcast IP instead of a Gateway-IP. (Is Broadcast a Switch and Gateway the Router, or am i wrong?)

-About the DHCP-> I’m nearly sure my DHCP server is working fine, all the settings (Gateway, IP and Subnet) are automatically taken from the Win-Clients (IPv4 is automatically assigned from 80.109.145.(2-254)

-Sorry not to know, Bill never told me, what’s a private IP and what’s the difference to a public IP?

-I think it could be a problem if the MODEM is just able to communicate with 1 PC. So in this case I’d need to
-set the Suse PC to Default Gateway
-Enable IP-Forwarding to MODEM

Hope this helps, I’m writing from my Win PC, so I will post the output for
ifconfig
route
tomorrow.

Thanks for your help!


I’m now directly plugged from my win7 pc to the modem, ipconfig as following, ps you were right, gateway has to be x.x.x.1 not x.x.x.255.

*Windows-IP-Konfiguration

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix: telesystem.com
Verbindungslokale IPv6-Adresse . : fe80::6099:a0f:63b5:4435%10
IPv4-Adresse . . . . . . . . . . : 80.109.145.85
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 80.109.145.1

Tunneladapter Teredo Tunneling Pseudo-Interface:

Verbindungsspezifisches DNS-Suffix:
IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:73ba:1063:3a26:af92:6eaa
Verbindungslokale IPv6-Adresse . : fe80::1063:3a26:af92:6eaa%12
Standardgateway . . . . . . . . . :

Tunneladapter Reusable Microsoft 6To4 Adapter:

Verbindungsspezifisches DNS-Suffix: telesystem.com
IPv6-Adresse. . . . . . . . . . . : 2002:506d:9155::506d:9155
Standardgateway . . . . . . . . . : 2002:c058:6301::c058:6301

Tunneladapter 6TO4 Adapter:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:

Tunneladapter isatap.telesystem.com:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix: telesystem.com
*

A private IP address is one in one of the subnets 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16. These addresses are guaranteed to be not used on the public Internet and can be used for intranets. You should not simply take a public subnet for your intranet, you should use a subnet in one of those private regions. You will only hurt yourself when one day you may need to access a server with an address that you have “stolen” and then it cannot be reached because it is duplicated in your intranet.

If you have a dumb DSL modem and your Linux server is doing the DSL login, then you will need to configure it this way:

Modem <-> Linux <-> Switch <-> Intranet (with private IP address subnet)

You will have to configure Linux as a NAT router/gateway. It would also run a DHCP server to give out addresses to your intranet clients.

Thank you, that was a good explanation. I had the same idea, to do it that way, but i wasn’t sure if it was the best idea.