Salix Forums

Hi,

my old setup was to connect to the router with a fixed IP address. The setup was running since long.

Now I had to change router (cable modem) and was trying to use a dynamic setup.
The new IP of the router is 192.168.0.1.
However, regardless what I try, the machine (salix 14.1 - 64bit) will not connect to the router.

If I connect a windows machine to the same router (same ethernet cable) with an automatic (dynamic) setup, it runs smooth.

Where do I miss the trick?

When using the wicd-tool I configure eth1 (thats the one) and leave DNS entries empty (or with 192.168.0.1) and all the rest to automatic, it does not connect.

Is there somewhere a hidden entry which defaults to a wrong gateway or something like that?

Thanks for any hint.

Post output of

Code: Select all

sudo ifconfig -a

eth1 might have changed when you did the hardware change to something else, ethx.

ok,

here we go, right after a cold start:

Code: Select all

jpg[~]$ sudo ifconfig -a
Passwort: 
eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:10:4b:8a:c0:41  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 22  base 0x4c00  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 512  bytes 37248 (36.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 512  bytes 37248 (36.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Now I am bringing up the interface and try to connect to the router.
However, where is the router adress or gateway? IP is 192.168.0.1 .

Code: Select all

jpg[~]$ sudo ifconfig eth1 up
jpg[~]$ sudo ifconfig eth1 192.168.0.20

jpg[~]$ sudo ifconfig -a
eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.0.20  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 00:10:4b:8a:c0:41  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 22  base 0x4c00  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 709  bytes 51936 (50.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 709  bytes 51936 (50.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So, the interface is configured to have IP 192.168.0.20.

Now try to connect:

Code: Select all

jpg[~]$ sudo dhcpcd
dhcpcd[1378]: version 6.0.5 starting
dhcpcd[1378]: eth1: waiting for carrier
dhcpcd[1378]: timed out
dhcpcd[1378]: allowing 8 seconds for IPv4LL timeout
dhcpcd[1378]: timed out
dhcpcd[1378]: forked to background, child pid 1397

And no connection....

So, why is there no IP assigned (leased) to the NIC?

Moer or less the same happens when using the WICD tool. Salix is trying to obtain the IP address from the router,
but never gets one...

I have no idea...

This should get it running as static:

Code: Select all

/sbin/ifconfig eth1 192.168.0.20
/sbin/ifconfig eth1 mtu 1500
/sbin/route add -net 192.168.0.0 netmask 255.255.255.0 eth1
/sbin/route add default gw 192.168.0.1 metric 1

Could also try lower mtu:

Code: Select all

/sbin/ifconfig eth1 mtu 1360

And don't forget to add nameserver, this example adds google server:

Code: Select all

echo "nameserver 8.8.8.8" > /etc/resolv.conf

ok,

I will try this as well, but I think the problem is different, in mind how persistently the connection is refused.

My guess is, supported by some people having similar issues with that specific provider and cable modem/router, that there
is a problem with IPv4 bridging (or tunneling) to IPv6.
The modem/router will assign an IPv4 address, however the transport is made in IPv6 technique.

Smartphones with actual android or windows OS or Windows 7/8 notebooks do connect flawless by WLAN and the notebook
as well by ethernet cable.

So, how can I manage to convince Salix to accept and work on IPv6 with tunneled IPv4

If Windows and Android do, Linux should do as well or maybe even better...

My last resort would be to connect a router in between, as a bridge, hoping to be able to talk in both ways...

so,

as expected, it did not work:

Code: Select all

sudo ifconfig eth1 192.168.0.09
sudo ifconfig eth1 mtu 1360
sudo route add -net 192.168.0.0 netmask 255.255.255.0 eth1
sudo route add default gw 192.168.0.1 metric 1

No connect!

Trying again the DHCP functionality, the dhcp client is not able to pick up an IP from the router.
To whatever reason the carrier signal gets lost and does not come back.

I am lost as well....

What does your /etc/rc.d/rc.inet1.conf say:

This is mine:

Code: Select all

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""

set USE_DHCP(1)="YES"

Then do
sudo /etc/rc.d/rc.inet1 start
and you should connect.

Hi,

thanks for your hint, however it does not work.

I did this after reading Alien Bob's networking howto.
I tried first with a fixed IP, then with DHCP as you showed.
With DHCP I get more or less the same message as I get when starting DHCP from the command line.
It gets a carrier signal which gets lost in a second.

I am relatively sure, its a problem of the modem/router and the cable.
Unitymedia is the ISP and they use a technicolor TS7200 cable modem.
The use IPv6 addressing, as IPv4 is limited. So they have to tunnel IPv4 in IPv6 or so.
What I understand from the various messages I found in the inet, that the interface
they provide is kind of underscaled/undersized and instead of a full IPv6 connection
the users get something half the way.
Obviously, Salix has a problem with that, whereas Android and Windows dont care about it.

But I would really like to know how to get that slved on my side, as Unitymedia is not really
willing to help, as they have no other technology available, except a business solution,
which delivers an IPv4 interface with static address, but I cannot pay for that.

Thanks so far.

P.S.
I just found following info on the unitymedia website:
(an actual Linux is listed as Working with IPv6) but the general statement is:

das verwendete Betriebssystem muss IPv6 sowie den automatischen Bezug der IPv6-Adresskonfiguration und den automatischen Bezug der IPv6 DNS Server mit DHCPv6 bzw. ND RDNSS beherrschen.

EN:

the used operating system must be able to manage IPv6, automatically obtain an IPv6 address configuration and automatically obtain the IPv6 DNS Server data with DHCPv6 or ND RDNSS

Does that ring a bell to anyone...

Let me get this right... the router forces the use of ipv6 on the local network? That's completely absurd in my opinion. As far as I know the networking tools for connecting to LANs we have (wicd, netconfig) do not support ipv6. I think that maybe NetworkManager does though, so you could try replacing wicd with it. Don't forget to also install the applet. Never tried ipv6 on a LAN myself. There really is no point.

Well, not sure whether the internal LAN has to run IPv6, however the IPv4 tunnel offered by the router seems to be a bit ... buggy or so.

How can I manage to install the Networkmanager?
Simply download the package to USB and then transfer it?

I need to check how that runs...slapt is so nice in use...

Thanks so far.

Salix Forums

[solved] No connection to router via eth1

[solved] No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1

Re: No connection to router via eth1