Porteus

Posted: **27 Mar 2012, 01:52**

Dear folks,

I am encountering an issue since the 1.1rcX series. Sometimes when starting up porteus with either i486 or x86_64 the dhcpcd prompting of network devices gets an ipv6 address as Hamza has explained in other thread[http://porteus.org/forum/viewtopic.php? ... t=10#p6926], will see how to find it or link it.

Anyhow, if I start porteus within a virtual machine, it gets an ipv4 address and connects automagically to the internet. Is there an easy way to fix this? or another thing to try. My old solution of

Code: Select all

ifconfig eth0 down
dhcpcd eth0

is not working anymore

I don't understand the behavior here, all I know is that machines running Fedora, Slackware, and Windows connect without hiccups. And only porteus tries these ipv6. The network adminstrator does advise me that the network is mainly ipv4 but that it is ipv6 capable, so what could be causing this trouble?

Hamza has explained the differences between ipv4 and ipv6 and to know the difference when doing an

Code: Select all

# ifconfig -a

What I would like to know if there is a magic incantanation in inet* section of network scripts to figure this out?

Thanks,

Antonio

Posted: **27 Mar 2012, 03:39**

hi Tonio,

Try to disable ipv6 support. you can do it in several ways (cheatcode, dhcpcd.conf or even blacklist ipv6 completely) as mentioned on Arch forum:
https://bbs.archlinux.org/viewtopic.php?id=135451

let us know if that helped.

Posted: **27 Mar 2012, 11:51**

@fanthom,

Thanks for the swift response. This undesired behavior has transferred over to a slackware box too

Code: Select all

bash-4.1$ uname -a
Linux emachine 3.2.7 #2 SMP Fri Feb 24 17:41:25 CST 2012 x86_64 AMD Athlon(tm) Processor 2650e AuthenticAMD GNU/Linux
bash-4.1$ cat /etc/slackware-version 
Slackware 13.37.0
su - 
passwd:
root@emachine:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:1d:72:a8:5f:69  
          inet6 addr: fe80::21d:72ff:fea8:5f69/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:218 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:23643 (23.0 KiB)  TX bytes:2716 (2.6 KiB)
          Interrupt:43 Base address:0x6000 

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:210 errors:0 dropped:0 overruns:0 frame:0
          TX packets:210 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:16116 (15.7 KiB)  TX bytes:16116 (15.7 KiB)

root@emachine:~# ifconfig eth0 down
root@emachine:~# dhclient eth0
root@emachine:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:1d:72:a8:5f:69  
          inet addr:10.155.132.127  Bcast:10.155.135.255  Mask:255.255.252.0
          inet6 addr: fe80::21d:72ff:fea8:5f69/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:310 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:39567 (38.6 KiB)  TX bytes:3708 (3.6 KiB)
          Interrupt:43 Base address:0x6000 

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:234 errors:0 dropped:0 overruns:0 frame:0
          TX packets:234 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:18300 (17.8 KiB)  TX bytes:18300 (17.8 KiB)

root@emachine:~#

I will take a look at your reference and see how that goes.

Posted: **24 Apr 2012, 12:42**

Sorry for taking long to post on this. I had not reported back

Using

Code: Select all

ipv6.disable=1

Gets the job done. However, I don't get ip address assigned, I have to run dhcpcd eth0 to get ip address. But this is no problem, since the problem was that somehow I was getting ipv6 addresses

Porteus

dhcpcd, ipv6 vs ipv4

dhcpcd, ipv6 vs ipv4

Re: dhcpcd, ipv6 vs ipv4

Re: dhcpcd, ipv6 vs ipv4

Re: dhcpcd, ipv6 vs ipv4