Well,
given my current IP’s, green is left emtpy, and LAN address of the ISP modem is 192.168.78.254.
red’s config:
IP: 192.168.78.253
subnetmask 255.255.255.0
gateway: 192.168.78.254 (which is the ISP modem IP)
ping 192.168.78.253 (red interface) no answer
ping 192.168.78.254 (ISP modem) no answer
Thanks for getting back
jc
Maybe you just mixed up red and green interface?
This i also thought of and swapped both cables. As a result, i couldn’t neither connect from LAN to 192.168.79.254 (green interface) nor to 192.168.78.253 (red interface), so i assume, i have the correct cabling and as far as i can tell, correct setting in nethserver.
btw, would i need to setup a routing from green to red or might red think, there must also be blue or orange?
and should the routing table look like this:
Thanks and best
jc
No, blue and orange are not needed and routing is preconfigured.
The routing table looks good.
Please recheck that IPS and Threat Shield are disabled.
Are there relevant entries in /var/log/firewall.log ?
Could you share your network configuration?
db networks show
Thanks for getting back,
Firewall log has tons of these:
10:52:10 n kernel: Shorewall:loc2fw:REJECT:IN=enp1s0 OUT= MAC=00:22:4d:7b:af:9b:d4:81:d7:a6:03:c8:08:00 SRC=192.168.79.31 DST=192.168.79.254 LEN=152 TOS=0x00 PREC=0x00 TTL=128 ID=8516 PROTO=UDP SPT=65236 DPT=1900 LEN=132
Threat shield was installed, same with IPS, i uninstalled them to make sure.
Last login: Fri Jan 1 05:34:48 2010 from 192.168.79.31
************ Welcome to NethServer ************
This is a NethServer installation.
Before editing configuration files, be aware
of the automatic events and templates system.
http://docs.nethserver.org
***********************************************
[root@n ~]# db networks show
enp1s0=ethernet
bootproto=none
gateway=
ipaddr=192.168.79.254
netmask=255.255.255.0
nslabel=LAN
role=green
enp2s0=ethernet
FwInBandwidth=1000000
FwOutBandwidth=20000
bootproto=none
gateway=192.168.78.254
ipaddr=192.168.78.253
netmask=255.255.255.0
nslabel=Vodafone
role=red
ppp0=xdsl-disabled
AuthType=auto
FwInBandwidth=
FwOutBandwidth=
Password=
name=PPPoE
provider=xDSL provider
role=red
user=
red1=provider
interface=enp2s0
weight=1
Unfortunately …
Best
jc
ps: i assume i misconfigured something in the first place, but, on the other hand, after the installation on my ex clearOS system, it wouldn’t connect either to internet.
It is:
and if i look into the services (firewall details) it looks like this:
Thanks for getting back, i am really stuck …
jc
I know it’s quite windows style issue managament but… did you reboot?
Also: would you please detail us the network card used by your computer? Via console/shell use
lspci |grep Ethernet
this is the output of my test server (single NIC)
1e:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5723 Gigabit Ethernet PCIe (rev 10)
This is an experience I had with other hardware for realtek cards.
Well, i didn’t reboot i have to admit. This are my nics:
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
So no Realtek 
i rebooted but… no connection. I do not need to setup a specific route in this case, correct? Just wanted to make sure.
Thanks and best
jc
This exclude my suggestion.
AFAIK no manual setup for route, never been necessary (according to documentation and my personal experience).
Worth asking…
ISP device (192.168.78.254/24 LAN - WAN unknown)
|
| (direct connection or separated switch)
|
192.168.78.253/24 GW 192.168.78.254
RED
NethServer
GREEN
192.168.79.254/24, no GW
|
| Switch
|
LAN clients (192.168.79.0/24, different IP addresses)
RED and GREEN on NethServer are not sharing a switch, correct?
Did you already tried to change network cable between RED and ISP device?
No switch sharing. The ISP Modem is connected to a wall socket, and the cable runs into a patch panel (around 15 meters long) and from patchpanel directly into RED nic. It is like you pointed out above. I swapped the cable from ISP modem to wall socket and also the connector of the wall socket as well, but no avail. Will give it a try later by changing the cable from patchpanel into RED nic, but i have to crawl behind the 19" rack, which takes a little time to do.
Thanks for help
jc
Take your time, do your tests. If from shell you cannot ping the ISP router seems quite hard to allow internet work… Unless it’s expected the behavior and did not bother ClearOS.
Well,
swapped cable from ISP modem to wall socket
swapped connector in wall socket and therfore changed the patchpanel’s port to reflect the different connector
swapped cable from patchpanel to red nic.
No avail.
It is not the expected behaviour; it did work before, but then after deciding against paying another year for clearos and putting nethserver i won’t have internet in my LAN anymore. So i am a little bit confused. I think, i will try a fresh install tomorrow, to find out, whether this would change something. I really don’t know, what’s happening there…
When connected to wifi of ISP modem, i can ping of course the ISP modem, but i cannot reach the red nic.
having Ethernetcable connected, i can reach green nic, but nothing in the other network. There is something strange happening here… Hmmm…
Thanks for getting back.
Are you using virtualization (Proxmox, VMWare)? Maybe there’s an issue like an enabled firewall or wrong mapping of network interfaces?
Maybe you enabled blocking the web ports?
I think best way is to just install NethServer without any additonal software for testing routing/networking.
now i used a cable directly from the ISP modem to my nethserver, no avail either, so i assume, it is NOT the cabling. No virtualization, bare metal.
You mean Squid Web proxy? That one isn’t enabled.
Yes, I meant squid.
Did you add firewall rules?
db fwrules show
Is ip forwarding enabled?
[root@server ~]# sysctl -a | grep ip_forward
net.ipv4.ip_forward = 1
Does it work if you clear the firewall?
shorewall clear
To enable it again:
signal-event firewall-adjust
Well, i couldn’t hardly wait to figure out, what’s going on. In the meanwhile, after swapping cables and connectors on patch panel and on wall socket, i gave it a shot at hooking up isp modem to a different wall socket, and connecting a different port on the patch panel, to a quite long RJ45 cable to be able to put my firewall pc on the desk, to hook it up to my display.
After reinstalling and forgetting to save the nic prefs, i had to reboot, because it took 192.168.1.1 as a IP address and didn’t want to do this manually in the shell. so i reinstalled one more time.
This time it showed the ip of my firewall within the ISP modem, and it was able, after i setup the correct interface to the iprange of ISP modem / gateway, to display a quite correct time and date, so i could just select my timezone and voila. At the moment it looks like it is working now, and neither the cables nor the patchpanel had problems, but the wall socket with 2 RJ45 jacks.
Will see, it takes some time to install the system, and to test it, shut it down and put it back into the 19" reconnect it to all cables and reboot.
Will keep you posted. Never thought, it could be the wall socket, but everything else. And never heard, that this one went bad before. Hmmm.
Thank you all for helping out and Let’s hope the best. As soon as the nethserver is back in the rack and working (or not, what i hope, will not happen), i’ll get back to you guys.
Best and thanks again.
jc
Cold/imperfect welding
Oxidation.
Barely compliant contact.
Too loose socket
Sometimes having a dumb small switch for testing purposes can pinpoint which side is playing jokes.
Well, never had a bad wall socket. But, i am glad, i figured it out, in the end, but if you guys wouldn’t have helped me, i wouldn’t even got the idea to double check that one, because, if everything fails, the most unlikely possiblity would have to be looked into…
But again, thank you indeed all ery much, haven’t seen such a cool community in ages.
Best
jc