SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0004474: PPPoE Interface uses 1.1.1.1 as IP - MantisBT Endian Bugtracker
Endian Issue Tracker





Please see now our new Bugtracker system: JIRA








View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004474Endian FirewallEndian Networkpublic2012-10-26 15:452012-11-09 11:12
Reporterclst 
Assigned To 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusnewResolutionopen 
PlatformOSOS Version
Product Version2.5 
Target VersionFixed in Version 
Summary0004474: PPPoE Interface uses 1.1.1.1 as IP
DescriptionProblem: The transparent proxy of my 4G provider (vodafone) rewrites Images in HTML to its webcache. The cache servers have 1.1.1.1, 1.1.1.2, etc.
Endian uses this IP (I suspect) internally and then does not route 1.1.1.1 to my 4G uplink.
As a result no images show in the browser.
Steps To Reproducecreate PPPoE uplink.
look at
root@efw:~ # ip addr
the ethX device gets 1.1.1.1
Additional InformationWorkaround:
ip addr del 1.1.1.1/24 dev ethX

I did not notice any adverse effects, but after a while (not rebooting) the address somehow gets reassigned and I have to delete it again.
Tagspppoe, uplink
Attached Files

- Relationships

-  Notes
(0008285)
clst (reporter)
2012-11-09 11:12

This got a little annoying lately.
Here is what I did to fix it:

edit /usr/lib/uplinks/generic/pppoe.sh

diff:
83c83
< ifconfig $PPPOEDEV 169.254.112.221 netmask 255.255.0.0 broadcast 169.254.255.255 up 2> /dev/null
---
> ifconfig $PPPOEDEV 1.1.1.1 netmask 255.255.255.0 broadcast 1.1.1.255 up 2> /dev/null

This should be fixed as 1.1.1.1 is no longer BOGON and never was a private address.
I used an auto-configuration IP so you could access the firewall via red if DHCP fails. Maybe a smarter way of assigning an IP is required.

- Issue History
Date Modified Username Field Change
2012-10-26 15:45 clst New Issue
2012-10-26 15:54 clst Tag Attached: pppoe
2012-10-26 15:54 clst Tag Attached: uplink
2012-11-09 11:12 clst Note Added: 0008285

Copyright © 2005-2008 Endian, SRL. All rights reserved.


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker